Last week I got on a call with a lady who asked about how to change the DBR to handle INBOUND enquiries... Like if someone had a "text INFO to 123" on their website or in their email messaging. So I walked her through what I would do AND I recorded the session I need to do a little bit of touch up on the video but here's what it covers: - How to change the beginning of the "Convo Start" workflow for Inbound enquiries - How to use ChatGPT to do an initial analysis of that first Inbound message - How to update the contact record with new details from the Inbound message - A few other key points about testing Once the video is edited I'll drop it in here for everyone.

[VIDEO NOW INCLUDED!] Last week I finished a small DBR campaign for a MedSpa in the US and wanted to share some learnings in case they help you with your campaigns. I'll also look to create a video for YT where I'll go into more detail about what I built.. But first.... Learning 1) EMOJI RESPONSES!! 🤣😱 I hadn't even thought about this but when going through testing one of the test users sent "Liked" the SMS from the AI.. And that meant in the conversation history in GHL the user sent back the same message the AI sent.. In the format "Liked {{message from AI}}" You can probably guess what happened?! The AI didn't know how to respond and so repeated the same question or message it sent before Here's what I did to resolve it.... - Created a part in a workflow where I'm recording the responses from the user - Using an IF/ELSE step to detect if the user message started with "Liked" or "Loved" - If it did, then I updated the custom field on the contact record with a manual update like "Yes sounds good" rather than the full contents of the message from the user (which was a repeat of the message from the AI) - If the message from the user didn't contain "Liked" or "Loved" the other branch in the IF/ELSE just updated the conversation as normal Learning 2) AI doesn't like the end of conversations Ever had a situation where you've added into the prompt the message for the AI to send at the end of a conversation and then it seems to get into a loop and repeat itself whenever a user responds? Here's what I did to solve it... - I thought about conversations "states" - like a story, a conversation has a start, middle and end - I created a workflow that uses a ChatGPT step to determine the "intent" of the conversation so far - It outputs a single word - "continue", "closing" or "stop" - That then feeds into an IF/ELSE step - if chatgpt thinks the conversation is mid-flow and outputs "continue" the user goes down a path that adds them to a workflow to create the next AI message in the conversation but if it think's the conversation is "closing" it will send a static message like "hope to see you soon" and then not do anything else

Snapshots are a little bit of magic Install them into your agency account and then push them through to a subaccount and you can magically have whole new workflows, forms, web pages and more. But sometimes it can be confusing. There's often a question about whether one snapshot will conflict with another and what will happen. And sadly it is possible if you are getting snapshots from different places. But I wanted to share some details about how I look/think about snapshots when I create them and build my bots. 1. I identify what custom fields and values I need for the bot, like a field for conversation history, or the first message to be sent 2. I create them with a naming structure that reflects the bot like "Reputation Convo History" or "Demo Tool - First Message" 3. I create folders for the custom fields and values 4. I repeat the same process for workflows - separate naming for each bot to minimise conflicts This way, I can have multiple bots installed into the same subaccount for a client without any conflicts. Hope it helps!

Can anyone help me with integration of Google Sheets into GHL? I would like to transcribe conversations into google sheets to share with the client... Thanks!

GHL is enabling outbound calling! BUT.....there are limitations on what you can do and how many calls you can make... So we still might need other providers like Elevenlabs, VAPI, Retell or Synthflow. In this video I go through the simple steps to trigger an outbound call from GHL using Twilio and Elevenlabs. I also show how you can include info from the contact record in GHL so the AI Agent can use those details during the call. Watch the video now on YouTube.