Workflow Template

Sales roleplay call app template

Acts as a buyer, raises objections, and scores how a rep handles discovery, value, and close.

View output schema

Best fit

  • Sales training
  • Objection handling
  • New rep onboarding

Do not use it for

  • Recording without consent
  • Replacing manager coaching entirely

Call flow

1. Set scenario

What buyer persona should I play?

2. Play buyer role

How would you open the call?

3. Raise objections

How do you handle a price objection?

4. Score response

What buyer persona should I play?

5. Save coaching notes

How would you open the call?

Prompt template

Run a sales roleplay by phone. Act as the selected buyer persona, raise realistic objections, evaluate discovery and response quality, then save coaching notes.

Questions asked

  • What buyer persona should I play?
  • How would you open the call?
  • How do you handle a price objection?

Human handoff

  • Sensitive customer data
  • Manager review requested

Structured output schema

{
  "outcome": "Sales roleplay outcome",
  "fields": [
    {
      "description": "rep name captured during the call.",
      "name": "rep_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": "scenario captured during the call.",
      "name": "scenario",
      "required": true,
      "type": "text"
    },
    {
      "description": "objections handled captured during the call.",
      "name": "objections_handled",
      "required": true,
      "type": "text"
    },
    {
      "description": "score captured during the call.",
      "name": "score",
      "required": true,
      "type": "number"
    },
    {
      "description": "strengths captured during the call.",
      "name": "strengths",
      "required": false,
      "type": "text"
    },
    {
      "description": "coaching notes captured during the call.",
      "name": "coaching_notes",
      "required": false,
      "type": "text"
    }
  ]
}

Transcript example

AI: Hi, I am an AI call workflow for Sales roleplay. What buyer persona should I play?

Caller: I want to practice handling price objections.

AI: How would you open the call?

Caller: I struggled to connect the objection back to business value.

Recommended integrations

NotionGoogle SheetsSlack

Launch review

Caller promise

Make the first screen and opening line match what the caller will actually get. For Sales roleplay, 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 rep name, phone number from caller id, scenario, 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 sensitive customer data, manager review requested 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 sales roleplay 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 sales training, objection handling, new rep onboarding.

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: "What buyer persona should I play?". 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 rep name, phone number from caller id, scenario, 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: sensitive customer data, manager review requested.

Clone this template

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