Writing phone intake
How to write a useful phone intake script
By ByTomorrow · Published
A phone intake script can collect many details and still leave the team unsure what the caller needs. The form was completed, but the request, callback route or responsible person is missing.
Write the script around the next decision. The fillable pattern below uses fictional examples and separates caller statements from assumptions. It is an editorial design aid, not a script that has been tested for your business.
What needs attention
Where the process can go wrong
Every question gets equal priority
Long scripts can ask for optional details before establishing the reason for the call. Order questions by whether the answer changes the next action.
The record says more than the caller did
A summary can turn an uncertain phrase into a firm date or an approved scope. Keep requested, confirmed and unknown values distinct.
Practical worksheet
Use this with your own business details
Opening and role
Fill in: "Thank you for calling [business]. I am the automated assistant. What would you like help with?" Adjust the language to the actual service. This is suggested wording, not a statement that it meets every business requirement.
Required intake fields
For an ordinary callback request collect the stated reason, a usable callback route and any detail needed to choose the responsible role. Ask for a name when useful. Do not require a project budget or full address unless it changes the immediate decision.
Optional branch questions
Add a question only if an answer selects a different route. Example: "Is this about an existing appointment or a new request?" If the caller asks for a human, use the human-request branch rather than continuing unrelated intake.
Read back the action-critical detail
Example: "You would like the scheduling team to discuss changing your appointment. I have not changed it. Is that right?" Read back corrected contact details where needed. Avoid re-reading the entire form.
Define a stopping point
The script ends after an allowed action succeeds or an owned handoff is recorded. Suggested close: "I have recorded your request for the scheduling team." Use that statement only after the record is confirmed. If it failed, state the failure and the approved alternative.
Fillable record format
Use fields: caller-supplied name; reason in the caller's words; request type; confirmed contact route; requested timing; details still unknown; action attempted; action result; follow-up owner. Store guesses as unresolved notes, not confirmed field values.
Put it to work
Check the complete process
Write the receiving team's decision
Ask the team what information it needs to take the next step. Remove questions that serve no defined purpose.
Draft the shortest valid path
Write a complete example for a routine request with only essential questions.
Add exceptions
Create branches for a correction, unclear request, refusal to supply a detail and immediate human request.
Role-play and inspect the record
Use fictional details. Compare the transcript with every saved field. Check that missing information stays missing.
Revise from specific failures
Tie a wording change to an observed misunderstanding. Retest the corrected case and the routine path.
Questions
Straight answers.
Use a summary for context, but define the fields your next action depends on. Check them against what the caller actually said before using them to commit a change.
Do not fill missing details with defaults that imply success. Retell documents cases where custom post-call fields are absent because no conversation occurred.
No. A request may need the caller's own words. Use a limited choice only when the categories genuinely fit, and preserve an unknown or other-request path.
Sources and further reading
- Retell post-call extraction
Retell documents typed extraction from completed conversations and missing custom fields when no conversation occurred.
Checked .
Define the next action
Bring a single request type and the receiving team's required fields. That is enough to draft a script with a clear ending.
Talk through your workflow