Blog Guide
Live transfer vs callback vs application link: setup
In short
Pick the handoff by who is free to take the call. Use a live transfer when a rep is free, a booked callback when nobody picks up or the merchant wants a later time, and your application link when they would rather apply on their own. On a build-it-yourself platform you configure each step yourself.
Short answer: pick the handoff by who is free to take the call
If a rep is free and the merchant is ready, transfer live. If nobody picks up, or the merchant wants to talk later, book a callback. If the merchant would rather type than talk, send your application link.
To set up a live transfer on a build-it-yourself voice platform, you add a transfer tool, enter your rep’s destination, choose a transfer mode and tell the agent in its prompt when to use it. Both Vapi and Retell document those steps. The rest of this guide covers the modes, the setup work, and what to do when the rep is busy.
Transfer modes in the Vapi and Retell docs
This table comes from each company’s public docs as of 2026-10-21. Check the linked pages for changes before you build.
| Platform | Mode | What the docs say |
|---|---|---|
| Retell | Cold transfer | The call goes straight to the destination and the agent drops off right away. |
| Retell | Warm transfer | The agent stays on the line after dialing. It can wait for a person to speak, play a private message only the destination hears, or do a three-way introduction before connecting the caller. |
| Retell | Agentic warm transfer | A second AI agent talks to the destination while the caller waits on hold. It then connects the caller or cancels. |
| Vapi | Blind transfer | Connects the customer without speaking to the destination. This is the default mode. |
| Vapi | Warm transfer with message, summary or TwiML | The destination hears a fixed message, a generated summary or TwiML instructions before the caller connects. These modes are Twilio only. |
| Vapi | Warm transfer, wait for operator first | Waits for the destination to speak, then delivers a message or summary. |
| Vapi | Warm transfer, assistant-based (experimental) | The caller waits on hold while a transfer assistant talks to the destination, then connects or cancels. |
Two limits from the docs matter for planning. Retell says Transfer Call works on phone calls only. Vapi says its five traditional warm modes run on Twilio calls and a message can be at most 1,000 characters.
What you set up yourself on a build-it-yourself platform
On these platforms, each of the following is a choice you make and test. From the docs:
- A destination. Vapi’s transfer tool routes a call to a phone number or SIP URI. Retell’s Transfer Call tool takes a destination too. If you have several reps or desks, give each destination a clear description so the agent routes to the right one.
- A trigger. You write in the prompt when the agent should transfer. Check the call log to confirm the tool fired. Both Vapi and Retell describe the tool setup.
- A mode. Cold, warm or agentic warm on Retell. Blind or one of the warm modes on Vapi.
- What the rep hears. A fixed message, a generated summary, or a private message. Vapi and Retell both offer a version of this. You write or configure it.
- How long to wait for the rep. Vapi’s wait-for-operator mode waits for the destination to speak before it delivers the message.
- What happens on failure. Vapi’s call ended reasons list transfer failure and operator-busy outcomes. You decide what the merchant gets in each case.
- A check that your phone provider supports the mode. Vapi’s message and summary modes work only on Twilio, so confirm this before you pick a mode.
What happens when the rep is busy
Plan for this case first. Vapi’s call ended reasons include transfer failure and operator-busy outcomes, so your setup needs an answer for both.
Use this to decide the route:
| Situation | Route | Why |
|---|---|---|
| Merchant is ready now and a rep is free | Live transfer | The merchant talks to your rep while still on the call. |
| Merchant is ready now, nobody picks up | Booked callback | Offer a time instead of making them wait. |
| Merchant wants to talk later | Booked callback | The merchant picks the time. |
| Merchant prefers to type, or your floor is closed | Application link | They start on their own, through your link. |
| Merchant needs capital later | Check back on their date | They stay in your future pipeline. |
Callback
Use it when the merchant wants to talk later, or when the live transfer rang out.
- Let them pick the time. Record the time they give.
- Call on time. Make sure someone owns each booked callback.
- Treat “call me back soon” as a real request. Put it on the schedule with a time.
Application link
Use it when the merchant would rather start on their own: busy owners, calls after your floor has gone home, people who prefer to type.
- Use your own link. The merchant applies through your application.
- Send it where they will see it. Text or email, their choice.
- Follow up. Track whether an application comes in after you send the link.
Check back later
Some merchants don’t need capital now but expect to soon. Put them on the date they gave and call back then.
Checklist before you turn on live transfer
- Rep availability. Know who is on the desk and when.
- The brief. The rep should hear who the merchant is and what they said before the call connects. Keep it short.
- Ring time. Decide how long the destination rings before the attempt counts as unanswered. Tell the merchant to expect a short hold.
- Fallback. Decide what happens on busy, no answer and failure. Callback first, application link second.
- Call record. Keep the recording, the transcript and one clear outcome for every call, so you can see which handoffs worked.
Then mark deal status on every handoff: not worked yet, application in, funded, or lost. Give it time. Your own numbers will show which route works for your floor.
How LeadRefinery hands off
LeadRefinery is an AI voice agent that works the aged leads already sitting in your CRM. When a merchant wants to talk, the agent hands them back by live transfer to your rep, a booked callback, or your application link.
- Live transfer. Your rep gets a short brief before the merchant connects. If nobody picks up, the agent offers the merchant a callback.
- Callback. It goes to your rep at the time the merchant chose. Check-back requests come back on the right date and build your future pipeline.
- Application link. Merchants get your own application link by text or email. We never collect bank logins.
- Call record. Every call keeps a recording, a transcript and one clear outcome.
- Phone setup. It is fully managed. We provision and register the phone numbers and check their health every day. See how it works.
Who each route fits
- A build-it-yourself platform fits you if you have a developer and want to choose every transfer setting yourself. Vapi and Retell both document their options in detail, linked above.
- A managed service fits you if you want aged files worked and handed back to your reps without building the transfer setup yourself. That is what we do.
- Any live transfer route needs reps who answer. If your desk is thin, lean on callbacks and your application link.
For a wider look at the options, read the best AI SDR tools for business lending and what to check before you buy an AI voice agent. For the basics, read what an AI sales rep does for an MCA broker and how to work aged MCA leads without hiring more reps.
Book an intro call
To talk about LeadRefinery for your aged files, book an intro call.
Questions
- How do I set up a live transfer from an AI voice agent to my reps?
- On a build-it-yourself platform you add a transfer tool, enter your rep's destination, choose a transfer mode and tell the agent in its prompt when to transfer. Then plan a fallback and test it. Steps are in https://docs.vapi.ai/call-forwarding and https://docs.retellai.com/build/single-multi-prompt/transfer-call.
- What is the difference between a cold and a warm transfer?
- Per Retell's docs, a cold transfer sends the call straight to the destination and the agent drops off. A warm transfer keeps the agent on the line to wait for a person, brief them, or introduce the caller before connecting. See https://docs.retellai.com/build/single-multi-prompt/transfer-call.
- What happens if nobody picks up the live transfer?
- That depends on how the handoff is set up. With LeadRefinery, the agent offers the merchant a callback, and the callback goes to your rep at the time the merchant chose.
- Do platform transfer tools work on web calls?
- Retell's docs say its Transfer Call tool works on phone calls only (https://docs.retellai.com/build/single-multi-prompt/transfer-call). Vapi's docs describe its transfer call tool as routing a phone call to a phone number or SIP URI (https://docs.vapi.ai/call-forwarding).
- Which handoff converts best?
- We don't publish conversion numbers yet. Track deal status on every handoff in your own shop and let your data decide.
- Should the application link be ours or the vendor's?
- Yours. LeadRefinery sends your own application link by text or email and never collects bank logins.
- Does LeadRefinery set up the phone side for me?
- Yes. It is fully managed. We provision and register the phone numbers and check their health every day.