1. Ask caller identity
Who is calling?
Screens unknown callers, captures why they are calling, filters spam, and forwards legitimate messages.
Who is calling?
What is the reason for your call?
What action do you want from the owner?
Who is calling?
What is the reason for your call?
Screen calls for a busy person. Ask who is calling, why, urgency, requested action, and whether a callback is needed. Do not share private information. Save a screened message.
{
"outcome": "Call screening outcome",
"fields": [
{
"description": "caller name captured during the call.",
"name": "caller_name",
"required": true,
"type": "text"
},
{
"description": "phone number from caller id captured during the call.",
"name": "phone_number_from_caller_id",
"required": true,
"type": "text"
},
{
"description": "company or relationship captured during the call.",
"name": "company_or_relationship",
"required": true,
"type": "text"
},
{
"description": "reason captured during the call.",
"name": "reason",
"required": true,
"type": "text"
},
{
"description": "urgency captured during the call.",
"name": "urgency",
"required": true,
"type": "text"
},
{
"description": "requested action captured during the call.",
"name": "requested_action",
"required": false,
"type": "text"
},
{
"description": "spam flag captured during the call.",
"name": "spam_flag",
"required": false,
"type": "text"
},
{
"description": "message summary captured during the call.",
"name": "message_summary",
"required": false,
"type": "text"
}
]
}
AI: Hi, I am an AI call workflow for Call screening. Who is calling?
Caller: I am calling from a vendor and need a callback.
AI: What is the reason for your call?
Caller: It is not urgent, but I need approval by Friday.
Make the first screen and opening line match what the caller will actually get. For Call screening, the promise should be narrow enough that a caller understands the purpose before sharing details or scanning a QR code. Avoid broad claims like "we can help with anything"; a specific promise produces cleaner calls and clearer follow-up.
Decide which fields are required before the call can be considered complete. A practical first version should capture caller name, phone number from caller id, company or relationship, then send a summary that the workflow owner can act on without replaying the call. If a field is not used for routing, qualification, scheduling, or review, remove it from the first launch.
Write down the cases that should not be automated. Use human review for known important contact, urgent family or safety issue, legal or media request so the workflow stays useful without pretending to handle every edge case. Review the first real calls before connecting higher-risk actions or expanding the workflow.
Use it when the call is repeatable, the team already knows the information they need, and the caller benefits from speaking instead of filling out a form. It works best for founders, creators, busy professionals.
The first question should identify the caller goal and gather enough context to continue naturally. For this template, start with: "Who is calling?". Keep follow-ups short so the caller does not feel like they are reading a form over the phone.
Save a structured result with caller name, phone number from caller id, company or relationship, plus a summary, completion status, and handoff reason when needed. The owner should be able to act on the result without interpreting raw transcript text.
Human handoff should trigger when the caller needs judgment, asks for a person, gives conflicting answers, or matches one of the workflow-specific rules: known important contact, urgent family or safety issue, legal or media request.
The template includes prompt, questions, output fields, sample transcript, handoff rules, and a live call entry point.