Call Recovery Features
Objective
This guide provides ready-to-use, word-for-word prompts for GHL Voice AI to implement call recovery strategies, ensuring that: โ AI follows up after dropped or disconnected calls via SMS โ AI detects and responds to silence instead of hanging up abruptly โ AI smoothly re-engages users after reconnection โ AI maximizes the chances of completing the conversation and avoiding lost leads
1. Understanding the Problem: Why Call Recovery Matters
๐น Common Issues Without Call Recovery: Call drops or user hangs up โ AI fails to follow up, leading to lost sales. User remains silent due to distractions or poor connection โ AI hangs up instead of re-engaging. User disconnects unintentionally โ No way to resume the conversation later. ๐น Solution: โ Implement automated follow-up SMS when a call is dropped. โ Use silence detection prompts to prevent AI from disconnecting too soon. โ Ensure AI re-engages smoothly if the user reconnects.
2. Step-by-Step AI Prompt Implementation for Call Recovery ๐น Step 1: Detecting Silence & Attempting to Re-Engage
โ Objective: AI must detect silence and check if the user is still present before disconnecting. ๐ Copy-and-Paste Prompt (Silence Detection): ๐น "I just want to make sure I didnโt lose you. Are you still there?" ๐น "Hello? I want to make sure we stay connected. Can you hear me?" ๐น "It seems like thereโs a pause. If youโre still there, just say anything and weโll continue." โ Real-Life Example: Before (Bad AI Response - No Silence Detection): ๐น User: (Gets distracted and remains silent for 10 seconds.) ๐น AI: (Automatically hangs up.) โ After (Optimized AI Response with Silence
Detection): ๐น User: (Gets distracted and remains silent for 10 seconds.) ๐น AI: "I just want to make sure I didnโt lose you. Are you still there?" โ ๐ Where to Use in GHL: Place this before AI hangs up due to inactivity (after 7-10 seconds of silence).
๐น Step 2: Handling Silence If the User Does Not Respond
โ Objective: If the user does not respond after the initial silence check, AI must provide a soft exit and set up a recovery option. ๐ Copy-and-Paste Prompt (Graceful Call Exit Due to Silence): ๐น "It looks like we got disconnected. If youโre still there, just say something, and we can continue." ๐น "I may have lost you, but no worries! Iโll send you a text with next steps just in case." ๐น "It seems like weโve lost connection. Iโll follow up via text so you donโt miss anything." โ Real-Life Example: Before (Bad AI Response - Abrupt Hang-Up): ๐น User: (Silent for 15 seconds) ๐น AI: (Instantly disconnects.) โ After (Optimized AI Response with Graceful Exit): ๐น User: (Silent for 15 seconds) ๐น AI: "I may have lost you, but no worries! Iโll send you a text with next steps just in case." โ ๐ Where to Use in GHL: Place this before AI hangs up due to extended silence (15+ seconds).
๐น Step 3: Sending an Automated Follow-Up SMS After a Dropped Call
โ Objective: If the user disconnects unexpectedly, AI must send a follow-up SMS to re-engage them. ๐ Copy-and-Paste Prompt (Follow-Up SMS for Dropped Calls): ๐น "Looks like we got disconnected! If youโd like to continue, reply YES and Iโll call you back." ๐น "Oops! It seems like the call dropped. Need to finish our chat? Just reply YES." ๐น "Hey, I think we lost connection! Want me to call you back? Just say YES." โ Real-Life Example: Before (Bad AI Response - No Follow-Up): ๐น User: (Accidentally disconnects.) ๐น AI: (Does nothingโlead is lost forever.) โ After (Optimized AI Response with Follow-Up SMS): ๐น User: (Accidentally disconnects.) ๐น AI (SMS sent immediately): "Oops! It seems like the call dropped. Need to finish our chat? Just reply YES." โ ๐ Where to Use in GHL: Set up an SMS trigger that activates if the call disconnects unexpectedly.
๐น Step 4: Resuming the Conversation When the User Responds to the SMS
โ Objective: If the user replies YES to the follow-up SMS, AI must seamlessly pick up where it left off instead of restarting. ๐ Copy-and-Paste Prompt (Resuming a Call from Follow-Up SMS): ๐น "Great! Letโs continue where we left off. You were asking about [Last Topic]." ๐น "Awesome! Iโm glad we could reconnect. Last time, we were discussing [Last Conversation Point]. Want to pick up from there?" ๐น "Glad to have you back! We were just talking about [Last Topic]. Letโs continue." โ Real-Life Example: User: (Replies โYESโ to follow-up SMS.) AI (Call resumes): ๐น "Awesome! Iโm glad we could reconnect. Last time, we were discussing pricing. Want to pick up from there?"
โ ๐ Where to Use in GHL: Set up a call-back trigger that resumes the last conversation instead of restarting from the beginning.
3. Full Example of an Optimized AI Call Recovery Flow (With Silence Detection & Follow-Up SMS)
๐ Scenario: AI Detects Silence & Re-Engages the User
๐น AI: "Hi, this is Sarah from [Company Name]. How can I assist you today?" ๐น User: (Gets distracted and remains silent for 10 seconds.) ๐น AI: "I just want to make sure I didnโt lose you. Are you still there?" ๐น User: (Remains silent for another 10 seconds.) ๐น AI: "I may have lost you, but no worries! Iโll send you a text with next steps just in case." ๐ Outcome: AI detects silence, attempts to re-engage, and sends a follow-up SMS instead of abruptly disconnecting.
๐ Scenario: AI Handles a Dropped Call & Follows Up via SMS
๐น User: (Call drops unexpectedly.) ๐น AI: (Immediately triggers an SMS.) ๐น SMS: "Oops! It seems like the call dropped. Need to finish our chat? Just reply YES." ๐น User: (Replies YES.) ๐น AI (resumes): "Great! Letโs continue where we left off. You were asking about our pricing optionsโletโs go over those now." ๐ Outcome: AI re- engages the user instead of losing them forever.
4. Implementation Checklist for GHL Voice AI Agents
โ Enable silence detection prompts โ Prevent AI from hanging up too soon. โ Use follow-up SMS triggers for dropped calls โ Give users a way to reconnect. โ Ensure AI resumes conversations instead of restarting โ Saves user time & improves experience. โ Test AI calls to identify where users typically drop off and adjust recovery strategies accordingly.
Last updated
Was this helpful?

