Turn new GoHighLevel bookings into rep-ready pre-call briefs

When someone books a call, we research them, pull up what your team already told them, and hand the rep a brief in Slack and on their calendar.

Agentic Task
GoHighLevelGoogle CalendarSlack BotInternet SearchSalesMeeting WorkflowsLead EnrichmentResearch & Monitoring
PromptCreate

Watch my GoHighLevel calendars and run this every time a new appointment is booked. Hang the workflow off the GoHighLevel new appointment trigger so it fires from the booking itself and receives that appointment, rather than scanning a calendar on a schedule.

Start from the appointment the trigger hands you. Use Calendars Get Appointment to load the full booking, including the start and end time, the calendar it landed on, the assigned user, the title, and any notes. Then use Contacts Get Contact to load the attendee, including their name, email, phone, company, tags, source, and custom fields.

Next, look back over everything that has already been said to this person. Use Conversations Search Conversations to find their conversations, then Get messages by conversation id to read the real message history on each one. I care about what they originally enquired about, the questions they asked, any pricing or promises my team already gave them, and anything they asked that nobody ever answered.

Then research the person and their company on the web with Internet Search. Look for what the company actually does, its size and location, recent news, and the person's role there. Ignore anything you cannot stand behind, and do not pad the brief with guesses or filler.

Write a short pre-call brief, roughly 300 words at most, covering four things: who this person and their company are, what they asked for, what my team has already told them, and three specific questions the rep should ask on the call. The questions must follow from the actual conversation history and the research, not generic discovery questions. If a question of theirs went unanswered, make chasing it one of the three.

Mirror the booking onto the rep's own calendar using Google Calendar Create Event at the same start and end time as the appointment. Title it with the contact name and what the call is about, and put the full brief in the event description so it is sitting there when the calendar reminder appears.

Send the same brief to the rep in Slack with Send a Message, defaulting to the user the appointment is assigned to, so it reaches them where they actually read things.

Finally, reply to the contact through GoHighLevel using Conversations Send a new message. Keep it short and warm, confirm the day and time, and reference what they actually enquired about in their own words. It must not read like a generic booking template.

One thing to keep in mind: the point of this workflow is the research and the recall of prior conversations, not the reminder. GoHighLevel already sends its own appointment reminders, so do not build reminder or follow up sequences here. If there is no prior conversation history, or the web turns up nothing useful, say so plainly in the brief instead of inventing detail.

Example output

Pre-call brief: Dana Whitfield, Whitfield Dental Group Tuesday 19 Aug, 2:30pm, 30 minutes, booked on the New Patient Consults calendar. Who they are: Practice manager at a three location dental group in Leeds, roughly 25 staff. Their site has been promoting a new implant clinic since June. What they asked for: Came in through the pricing page form asking whether you can run recall campaigns for patients who have not been in for 18 months. Mentioned they are on Dentally. What they have already been told: Sam replied on 6 Aug quoting the 950 a month retainer and said recall campaigns are included. Dana then asked whether that covers SMS costs and nobody answered her. Three questions to ask: 1. Sam quoted 950 including recall campaigns, but your question about SMS costs never got answered. Shall we start there? 2. How many dormant patients are sitting in Dentally right now? 3. The implant clinic launched in June. Is filling that the real priority, or is this about general recall?

What does this prompt do?

  • Runs the moment a new appointment lands on one of your GoHighLevel calendars, so the prep happens without anyone remembering to do it.
  • Pulls up the booking and the contact, then reads back through the messages your team has already exchanged with that person.
  • Researches the person and their company on the web, then writes a short brief covering who they are, what they asked for, what they have already been told, and three questions worth asking.
  • Puts the brief on the rep's own calendar at the booking time and sends it to them in Slack, then replies to the customer with a friendly confirmation that references their actual enquiry.

What do I need to use this?

  • A GoHighLevel account containing the calendar your bookings land on, with access to contacts and conversation history.
  • A Google Calendar account for the rep whose calendar should mirror the booking.
  • A Slack workspace where the brief can be delivered to the rep.
  • No research subscription is needed, the web research is built in.

How can I customize it?

  • Choose which calendars count, so you get briefs for sales consults but not for admin or support bookings.
  • Change where the brief lands, either as a direct message to the assigned rep or into a shared team channel where everyone preps together.
  • Reshape the brief itself, asking for more or fewer questions, a deeper company section, or a set house style for the customer confirmation.

FAQs

Does this replace GoHighLevel's appointment reminders?
No, and it does not try to. GoHighLevel already sends reminder texts and emails on its own, and this leaves all of that alone. The value here is the preparation, meaning the research and the recall of what the customer has already been told.
What happens if the contact has never messaged us before?
The brief says so plainly. A brand new lead simply gets the booking details plus whatever the web research turns up, rather than invented history. The same applies when the research finds nothing useful about a person or company.
Does it matter how the appointment was booked?
No. It runs off the booking itself, so it works whether the slot came from a funnel, a booking widget, a form, or someone on your team entering it by hand.
Who receives the brief in Slack?
By default it goes to the rep the appointment is assigned to. If your team preps together you can send it to a shared channel instead, or do both.
Will the customer confirmation sound automated?
It is written fresh for each booking and quotes what the person actually enquired about, so it reads like a colleague replying rather than a template. You can set the tone and length to match how your team normally writes.

Related templates

Alert your team when GoHighLevel messages go unanswered

Every 30 minutes during business hours, find the customer messages nobody has replied to yet and post one quiet Slack nudge.

GoHighLevel
Slack Bot
Google Sheets
Deterministic Code
Triage new GoHighLevel conversations and draft the reply

Every new inbound message gets sorted by intent, urgency and mood, with a ready-to-send reply waiting in Slack before anyone opens the inbox.

GoHighLevel
Slack Bot
Agentic Task
Re-engage dormant GoHighLevel contacts with personal messages

Every Monday, find the leads who have gone quiet, read what they originally asked about, and send each one a short personal nudge.

GoHighLevel
Google Sheets
Agentic Task
Auto-fix your calendar when a flight slips, and flag what's at risk

When your flight moves, your calendar times get corrected automatically and you get a Slack note naming the meetings you're about to miss.

Google Calendar
AviationStack
Slack
Agentic Task
Build a credential rotation checklist when someone leaves

When someone leaves, we check which shared passwords they used in their final months and post a ranked rotation list to your security channel.

1Password
Rippling
Slack Bot
+1
Agentic Task
Weekly Amazon S3 bucket security audit posted to Slack

Every Monday, check every S3 bucket for public exposure, missing encryption and weak backup settings, then get the risks ranked in Slack.

Amazon S3
Slack Bot
Google Sheets
Agentic Task

Stop walking into calls cold.

Every new booking arrives with the research already done and the history recalled, so your rep opens the call knowing exactly what this person asked for.