1. Identify caller
Who should I say called?
Acts as a personal phone filter that takes messages, protects time, and routes only important calls.
Who should I say called?
What do you need from them?
When should they respond?
Who should I say called?
What do you need from them?
Filter personal calls. Ask caller identity, relationship, reason, urgency, and desired response. Protect privacy and do not make commitments. Save a concise message brief.
{
"outcome": "Personal assistant call filter 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": "relationship captured during the call.",
"name": "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": "callback window captured during the call.",
"name": "callback_window",
"required": false,
"type": "text"
},
{
"description": "recommended response captured during the call.",
"name": "recommended_response",
"required": false,
"type": "text"
}
]
}
AI: Hi, I am an AI call workflow for Personal assistant call filter. Who should I say called?
Caller: I need to leave a message for James.
AI: What do you need from them?
Caller: Please ask him to call me tomorrow morning about the proposal.
Make the first screen and opening line match what the caller will actually get. For Personal assistant call filter, 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, 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 urgent personal matter, known vip, sensitive legal or financial issue 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 solo operators, creators, consultants.
The first question should identify the caller goal and gather enough context to continue naturally. For this template, start with: "Who should I say called?". 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, 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: urgent personal matter, known vip, sensitive legal or financial issue.
The template includes prompt, questions, output fields, sample transcript, handoff rules, and a live call entry point.