Training Support Teams with Exec

Support teams use Exec to practice the calls that make or break customer trust: escalations, billing disputes, and saying no without losing the customer. Agents talk to an AI customer who arrives frustrated the way actual customers do, and every session ends with a scorecard that grades de-escalation, clarity, and resolution. This guide covers what to build first, which skills to track, and a weekly rhythm built around the tickets in your queue.

Start with One Scenario

When you created your workspace, Exec read your company website and drafted roleplay ideas that fit your business. If you said you were training a support team, those ideas already lean toward customer conversations. Pick the one closest to a call your agents actually take, answer a couple of quick questions, and Scenario Studio builds it in about two minutes. Run it yourself before showing anyone. Talk out loud like it is a live call, end the session with the green End button, and read the scorecard. If the customer gets a detail about your product wrong, edit the scenario and tell the agent what to change in one sentence. New to running sessions? Start with Complete Your First Roleplay.

Scenarios Worth Building

Here are the builds support teams get the most out of. Copy a prompt, fill in the bracketed fields, and paste it into the Scenario Studio chat. The full collection lives in the Prompt Library.

Frustrated Escalation

When to use: Agents freeze or over-apologize when a customer arrives angry.

I am a [JOB TITLE] at [COMPANY], and I want to build a support call scenario where I am speaking with a customer whose [PRODUCT/SERVICE] issue has been open for [TIME PERIOD] and who has already contacted us twice.

My goal is to de-escalate, take ownership, and get the customer to a concrete resolution plan.

For me to succeed, I must acknowledge the frustration in the first 30 seconds, summarize the history accurately without making the customer repeat it, and commit to a specific next step with a time.

This conversation is challenging because the customer interrupts, questions my competence, and threatens to post publicly about the experience.

Billing Dispute

When to use: Refund and billing calls drag on or end in unnecessary credits.

I am a [JOB TITLE] at [COMPANY], and I want to build a scenario where a customer disputes a charge of [AMOUNT] for [PRODUCT/SERVICE] that they believe is wrong.

My goal is to resolve the dispute within policy while keeping the customer.

For me to succeed, I must explain the charge in plain language, state clearly what I can and cannot do, and offer the policy-compliant resolution without letting the customer push me into an exception.

This conversation is challenging because the customer is polite but persistent, cites a competitor's refund policy, and asks for a supervisor when I say no.

Saying No to a Feature Request

When to use: Agents promise roadmap items or leave customers feeling dismissed.

I am a [JOB TITLE] at [COMPANY], and I want to build a scenario where a long-time customer asks for [FEATURE] that we do not offer and have no near-term plan to build.

My goal is to say no clearly while keeping the customer confident in the product.

For me to succeed, I must give a direct answer early, offer the closest working alternative, and log the request in a way the customer believes.

This conversation is challenging because the customer says the missing feature is the reason they might churn.

Your best scenario source is last week’s hardest ticket. Paste the ticket summary into Scenario Studio and ask it to build the call version. When a scenario feels too easy, edit it to make the customer more insistent and the grading stricter.

Skills to Track

Every scenario grades agents against evaluation criteria you control. For support teams, the criteria that move CSAT are:

De-escalation. Lowering the temperature in the first minute without conceding things you cannot deliver.
Ownership language. “Here is what I am going to do” instead of “you will need to.”
Clarity on the resolution. The customer can repeat back what happens next and when.
Holding policy. Saying no cleanly, once, without a lecture and without caving.

Agents see how they scored on each criterion after every session, with lines they actually said and stronger phrasing they could have used. See Interpret Your Results for how to read a scorecard, and Skills for tracking these across the team.

The Weekly Rhythm

The support teams that get the most out of Exec run a simple loop:

Monday. Build or remix one escalation scenario from a ticket that went sideways last week, then assign it with a minimum passing score.
During the week. Agents practice until they pass. Most take two or three attempts.
Friday. The team reviews the toughest transcript of the week together and agrees on the line they will use next time.

Because the scenario comes from a ticket your team just handled, practice never drifts away from what the queue actually looks like.

A Sample Three-Week Onboarding Program

For new-agent onboarding, bundle scenarios into a Program with due dates and completion criteria. Programs come with Starter plans and above.

Week	Focus	Components
1	Product fluency	Announcement with your help-center highlights, common-question roleplay (minimum Silver), intro survey
2	Hard conversations	Frustrated escalation roleplay (minimum Silver, 2+ attempts), billing dispute roleplay
3	Edge cases	Saying-no roleplay (minimum Gold), shadow-ticket action item, final survey

On Professional plans, attach a certification so agents who clear the bar get a record of it before taking live queues.

Score Live Calls Too

If your support team takes phone calls, Call Scoring grades the live ones on the same kind of scorecard your roleplays use, so you can spot which issue types generate the hardest calls and practice those next. Call Scoring works on every plan, including Free, and you pay only for the calls you score. Setup takes about five minutes: Set Up Call Scoring.

Next Steps

Roll Exec out to your team

Invites, seats, groups, and your first assignment, in one walkthrough.

Plans and feature availability

What Free, Starter, Professional, and Enterprise each include.

Getting Help

Need help? Contact us at [email protected] for guidance on building support scenarios or rolling out practice to your team.

Getting Started

Guides

Roleplays

Courses

Skills

Knowledge Hub

Calls

Coaching

Programs

Certifications

Platform Administration

Integrations

Training Support Teams with Exec

Start with One Scenario

Scenarios Worth Building

Frustrated Escalation

Billing Dispute

Saying No to a Feature Request

Skills to Track

The Weekly Rhythm

A Sample Three-Week Onboarding Program

Score Live Calls Too

Next Steps

Roll Exec out to your team

Plans and feature availability

Getting Help

​Start with One Scenario

​Scenarios Worth Building

​Frustrated Escalation

​Billing Dispute

​Saying No to a Feature Request

​Skills to Track

​The Weekly Rhythm

​A Sample Three-Week Onboarding Program

​Score Live Calls Too

​Next Steps

Roll Exec out to your team

Plans and feature availability

​Getting Help

Start with One Scenario

Scenarios Worth Building

Frustrated Escalation

Billing Dispute

Saying No to a Feature Request

Skills to Track

The Weekly Rhythm

A Sample Three-Week Onboarding Program

Score Live Calls Too

Next Steps

Getting Help