Practical operating guide
How to hand a sales inquiry from AI to a person
By ByTomorrow · Published
The AI receptionist passed along the message. The salesperson thought someone else had it. The caller is still waiting.
The missing step is often ownership. Delivering a summary, ringing a phone and having a person accept responsibility are separate events.
Diagnosis
Sent is not the same as accepted
A notification has no accountable recipient
A shared inbox can hold an inquiry without anyone claiming it. Define the owner of the task and the evidence that they accepted it.
A live transfer needs a result
Retell documents cold and warm transfer modes, including private briefing options. Choose a tested mode suited to the business. A transfer attempt alone should not mark the sales task accepted.
A salesperson needs the unresolved request
A long transcript can obscure what the person must decide next. The handoff should name the request, what is already known and the commitment still outstanding.
Working worksheet
A handoff brief with an acceptance record
The brief
Copy this structure: inquiry identifier ___; caller request ___; confirmed facts ___; open question ___; caller's preferred contact method ___; promise already made ___; proposed owner ___. Keep guesses out of the confirmed-facts field.
The acceptance record
Add: receiving person ___; accepted at ___; next action ___; due time chosen by owner ___; source task identifier ___. The person accepting the inquiry confirms that they can see the brief and act on it.
Declined or unavailable
If the proposed owner declines or does not accept within the business's defined window, keep the inquiry open. Route it to the named backup. Record the reason and avoid sending the customer simultaneous follow-ups from multiple people.
Live-call example
Illustrative case: the recipient answers but says they cannot handle this request. The transfer connected, yet the sales handoff was declined. The workflow retains ownership until the backup accepts or an approved callback task is assigned.
Asynchronous example
Illustrative case: the agent creates a task after the call, and an email alert reaches the team. Status remains awaiting acceptance. When a salesperson claims the task and chooses the next action, the record changes to accepted with that person's name.
Use the worksheet
Put it into practice
Choose acceptance evidence
For live calls, define how the recipient confirms they can handle the inquiry. For queued tasks, use an explicit assignment and acknowledgment that the team can inspect.
Test the refusal branch
Have a test recipient decline responsibility. Verify the task reaches the backup without being marked complete or disappearing after the first notification.
Reconcile unaccepted work
At the agreed review time, inspect inquiries still awaiting acceptance. Separate delivery failures from staffing gaps because they require different repairs.
Questions
Straight answers.
No. Intake makes the request understandable. Acceptance establishes who will act on it. A perfectly written brief can still have no owner.
Only when the responsible team has approved and can support that commitment. Record the exact expectation, and update the customer through the approved process if it changes.
Sources and further reading
- Retell transfer-call documentation
Supports cold and warm transfer behavior and private briefing options. Explicit sales-task acceptance is an original operating requirement, not a claimed default vendor behavior.
Checked .
Name the person who accepts the work
A practical handoff discussion needs the primary owner, backup and evidence each uses to claim an inquiry.
Discuss your workflow