Workflow Template

Review request call call app template

Calls or answers customers after service, captures satisfaction, and routes happy customers toward a review request.

View output schema

Best fit

  • Home services
  • Clinics
  • Local businesses

Do not use it for

  • Fake reviews
  • Review gating that hides negative feedback

Call flow

1. Ask experience

How did the service go?

2. Capture concerns

Is there anything we should fix first?

3. Invite honest review if appropriate

Would you be comfortable leaving an honest review?

4. Offer follow-up

How did the service go?

5. Save outcome

Is there anything we should fix first?

Prompt template

Ask for post-service feedback by phone and invite an honest review only when appropriate. Do not pressure the caller or suppress negative feedback. Save review readiness and follow-up notes.

Questions asked

  • How did the service go?
  • Is there anything we should fix first?
  • Would you be comfortable leaving an honest review?

Human handoff

  • Complaint before review
  • Refund or rework request
  • Caller feels pressured

Structured output schema

{
  "outcome": "Review request 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": "satisfaction captured during the call.",
      "name": "satisfaction",
      "required": true,
      "type": "text"
    },
    {
      "description": "concerns captured during the call.",
      "name": "concerns",
      "required": true,
      "type": "text"
    },
    {
      "description": "review interest captured during the call.",
      "name": "review_interest",
      "required": true,
      "type": "text"
    },
    {
      "description": "follow up needed captured during the call.",
      "name": "follow_up_needed",
      "required": false,
      "type": "text"
    },
    {
      "description": "review platform captured during the call.",
      "name": "review_platform",
      "required": false,
      "type": "text"
    }
  ]
}

Transcript example

AI: Hi, I am an AI call workflow for Review request call. How did the service go?

Caller: The job was finished today and I got a follow-up call.

AI: Is there anything we should fix first?

Caller: I am happy to leave a review after I receive the link.

Recommended integrations

Google SheetsSlackHubSpot

Launch review

Caller promise

Make the first screen and opening line match what the caller will actually get. For Review request 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.

Required outcome

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, satisfaction, 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.

Human review

Write down the cases that should not be automated. Use human review for complaint before review, refund or rework request, caller feels pressured 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.

FAQ

When should I use a review request call Call App?

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 home services, clinics, local businesses.

What should the AI ask first?

The first question should identify the caller goal and gather enough context to continue naturally. For this template, start with: "How did the service go?". Keep follow-ups short so the caller does not feel like they are reading a form over the phone.

What output fields should be saved?

Save a structured result with caller name, phone number from caller id, satisfaction, 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.

What should trigger human handoff?

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 before review, refund or rework request, caller feels pressured.

Clone this template

The template includes prompt, questions, output fields, sample transcript, handoff rules, and a live call entry point.