AI outbound call script templates are short, reusable plans for an AI voice agent. Each has an opening line, a few questions and one next step. Write a separate script for each drop-off stage. Someone who never verified an ID needs a different call than someone who never funded.
Match each script to a drop-off stage
Each script starts from a trigger and has one goal. Fire calls from a CRM event, such as a customer dropping off during KYC, and set a delay. The call can go out at once or wait.
| # | Stage | Trigger | Call timing | Goal |
|---|---|---|---|---|
| 1 | Signed up, never activated | No first action | Within hours | Get one first action |
| 2 | Started application, stopped early | Form left unfinished | Next day | Find the block and resume |
| 3 | Stuck at identity or KYC | KYC step failed or idle | Same day | Fix the blocker, resend link |
| 4 | Missing documents | Item still outstanding | 1 to 2 days | Get that item uploaded |
| 5 | Approved or signed, never funded or paid | No payment after approval | 1 to 3 days | Learn what changed, then fund |
| 6 | Long-silent or lapsed | No activity for weeks | Weeks later | Learn why they left |
Scripts 1 to 5 fit lead follow-up campaigns. Script 6 fits win-back.
Scripts 1 to 3: early drop-off
Lending, fintech and investment teams tend to lose people at the same few points: signed up but not active, KYC started but not finished. Each script has the same parts: when to call, opening line, questions, next step and exit line. Replace the bracketed items with your own details.
Script 1: Signed up, never activated
When to call: a few hours after signup, with no first action logged.
Opening line: "Hi [Name], this is an AI assistant calling for [Company]. You signed up today, and I'd like to help you take your first step. This call may be recorded, and if you say 'stop' we won't call again. Do you have two minutes?"
Questions:
- "What did you hope to do with [Product]?"
- "Is anything stopping you from starting?"
Branch: A clear goal gets a link to that first step. Confusion gets a callback or human handover. No interest gets a reason code and a polite close.
Next step: text one link to the first action.
Exit line: "Thanks, [Name]. The link is on its way."
Script 2: Started application, stopped early
When to call: the day after the form was left unfinished.
Opening line: "Hello [Name], I'm an AI assistant calling for [Company]. You began an application yesterday and I'm calling to help you finish it. If you'd rather not get these calls, just say so. Is now a good time?"
Questions:
- "Which part of the form slowed you down?"
- "Was it a question you weren't sure about, or did you run out of time?"
Branch: A confusing question gets a plain explanation and a resume link. A time problem gets a callback slot. A change of mind gets a reason code.
Next step: text a link that reopens the saved application.
Exit line: "Your progress is saved."
Script 3: Stuck at identity or KYC
When to call: the same day the check failed or went idle.
Opening line: "Hi [Name], this is an AI assistant from [Company]. Your identity check didn't finish, and I can help. This call is recorded, and you can opt out at any time. Can I ask a quick question?"
Questions:
- "What happened when you tried: the camera, the ID type, or the app crashing?"
- "Would a fresh link by text help?"
Branch: A camera or app fault gets a new link. An unsupported ID type or a privacy worry goes to a human.
Next step: text a new verification link. Never ask for ID numbers on the call.
Exit line: "The link is on its way."
Log a small win for each step, such as "KYC passed". Then you can tell customer drop-off from product drop-off.
Scripts 4 to 6: late drop-off
These three calls reach people who already gave you effort or trust. Keep each one short, name the exact item, and tag a reason code for every answer.
Script 4: Missing documents
When to call: one to two days after the item was requested and is still outstanding.
Opening line: "Hello [Name], I'm an AI assistant calling for [Company]. Your application is complete except for one item: [exact document]. This call is recorded, and if you say 'stop' we won't call again. Do you have a minute?"
Questions:
- "Do you have [exact document] with you?"
- "What's making the upload hard: finding it, the file size, or the upload page?"
Branch: A document not in hand gets a callback slot and the code "document not held". A technical problem gets another route, such as a text link that opens the phone camera, or email. A question about why you need it goes to a human.
Next step: text the upload link for that one item.
Exit line: "That's the only thing left. The link is on its way."
Script 5: Approved, never funded or paid
When to call: one to three days after approval, with no payment.
Opening line: "Hi [Name], this is an AI assistant calling for [Company]. Good news: your [account or loan] was approved. I'm calling to help you take the last step. You can opt out of calls at any time. Is this a good moment?"
Questions:
- "What's happened since you were approved?"
- "Did something change: the cost, the timing, or how comfortable you feel?"
Branch: A timing issue gets a dated reminder and a callback. A cost worry gets the fee details read out plainly. Any complaint or disputed amount goes to a human. Buyers raise this handover on their own, asking whether it is polite and who follows up. Write the handover line and assign an owner for the queue.
Next step: text the funding or payment link, or book a human callback.
Exit line: "Thanks, [Name]. Your approval is still active."
Script 6: Lapsed, win-back
When to call: weeks after the last activity, inside allowed calling hours. Name the company first, as lapsed customers often don't recognise the caller.
Opening line: "Hello [Name], I'm an AI assistant calling for [Company]. We haven't seen you in a while, and I'd value two minutes of feedback, with no sales pitch. If you'd rather not hear from us, say so and we'll remove you. Is that okay?"
Questions:
- "What made you stop using [Product]?"
- "Is there one thing that would bring you back?"
Branch: A fixable reason gets an offer to send details. "No interest" gets a clean close and the number goes on the do-not-contact list. A complaint goes to a human.
Next step: text a short link, or end with thanks.
Exit line: "Thank you for your honesty. We'll respect your choice."
Use a short fixed list of reason codes: cost, trust, timing, product fit, technical fault, document not held, no interest. Set it inside the campaign so every call ends with one code.
Set the rules before the first call
Say it is an AI in the first sentence of every script. The rule is spreading across regions:
- EU: Article 50 of the AI Act has applied since 2 Aug 2026. Any AI that talks to people, including automated phone systems, must say it is AI from the first interaction.
- US (federal): the FCC's 2024 ruling confirms that the TCPA's "artificial or prerecorded voice" rules cover AI technologies that generate human voices. Calls using them need the called party's prior express consent.
- US (states): Colorado's Chatbot Safety Act takes effect 1 Jan 2027 and requires public-facing conversational AI to disclose it is AI.
Every script also needs a human exit. Gartner found that 87% of customers want access to a human. Keep the handover branch in all six.
Adapt the scripts to your funnel
Change the reason line first. Swap in your product, your exact missing item and your own timing for each stage. Start with the stage that leaks most people, not all six at once.
Insight7 campaign types include lead follow-up and win-back, in beta. Campaigns have consent marking, calling hours, retry rules, a do-not-call list and a scorecard when they end. These details are spec only, so check them in the app. You can test the agent in the browser before launch, with no phone number needed. A dashboard shows calls in progress and lets you read each transcript.
Measure by stage: reached, reason code and completed step. A call where only the AI spoke is not counted as reached.
Related reading: How to Use AI Voice Agents to Recover Customers Who Drop Off During Onboarding, How to Reduce Support Tickets Caused by Incomplete KYC With Automated Outbound Calls and 7 Signs Your Email and SMS Onboarding Sequence Needs a Voice Channel.
Questions people also ask
What should an AI outbound call script include?
It needs five parts: timing, an opening line, two or three questions, one next step and an exit line. The opening line names the AI, the company and the reason. Add a human handover.
How soon should you call after someone abandons a signup?
Match the delay to the stage. Call within hours for a signup that never activated, and the same day for a failed identity check. Wait a day or more for documents or an unpaid approved account.
How many times should you retry an abandoned application call?
We advise three to four attempts. A carrier's temporary refusal should not use up an attempt.
Do you have to tell people an AI is calling?
In the EU, yes, and more regions are following. Disclose in the first sentence everywhere. The transcript then holds proof that you said it.
Is it legal to use AI voice calls for follow-up?
Often yes, with consent. Keep a consent record for each contact and honour opt-outs at once. Rules differ by region and by whether the call is marketing, so check with counsel.
Should you call or send an SMS to someone who abandoned an application?
Call to learn why someone stopped, or when a worry a text can't settle blocks the step. Text when the next step is just a link. Often the best pattern is a call first, then a text with the link.
How long should an abandoned application call be?
Plan for about two minutes. Keep to two or three questions, one branch and one link. Hand anyone who needs more help to a human.
Check the agent before you launch
A call script works when it asks one question and gives one clear next step. Run a test call first. Check that the agent says it is an AI in the first sentence.

