1. Ask satisfaction
How did the experience go?
Collects qualitative feedback by phone and turns it into themes, ratings, and follow-up actions.
How did the experience go?
What should we improve?
Would you like someone to follow up?
How did the experience go?
What should we improve?
Collect customer feedback by phone. Ask for rating, what worked, what did not, and whether follow-up is requested. Save structured feedback with themes and next action.
{
"outcome": "Customer feedback call 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": "rating captured during the call.",
"name": "rating",
"required": true,
"type": "text"
},
{
"description": "positive feedback captured during the call.",
"name": "positive_feedback",
"required": true,
"type": "text"
},
{
"description": "improvement area captured during the call.",
"name": "improvement_area",
"required": true,
"type": "text"
},
{
"description": "follow up requested captured during the call.",
"name": "follow_up_requested",
"required": false,
"type": "text"
},
{
"description": "theme captured during the call.",
"name": "theme",
"required": false,
"type": "text"
}
]
}
AI: Hi, I am an AI call workflow for Customer feedback call. How did the experience go?
Caller: I wanted to give feedback on yesterday's service.
AI: What should we improve?
Caller: The work was good, but the arrival window was unclear.
Make the first screen and opening line match what the caller will actually get. For Customer feedback call, 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, rating, 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 complaint, refund request, safety concern, caller asks for manager 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 post-service follow-up, product research, customer success.
The first question should identify the caller goal and gather enough context to continue naturally. For this template, start with: "How did the experience go?". 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, rating, 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: complaint, refund request, safety concern, caller asks for manager.
The template includes prompt, questions, output fields, sample transcript, handoff rules, and a live call entry point.