Steer a Request to the Right Channel
Practice redirecting a small request to chat instead of a meeting, while keeping the tone collaborative and offering a live conversation only if needed.
Every employee gets a seat — priced per employee in Performance & Learning, quoted with this template ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Built for: Technology · Professional services · Education · Operations
Overview
Steer a Request to the Right Channel is a short AI roleplay practice scenario for deciding whether a teammate’s ask should stay in chat or move to a live conversation. In this template, the learner responds to a remote teammate who wants to book a 30-minute meeting for a small wording change in a project update. The right move is not to block the request, but to redirect it to an async channel, explain why that channel is enough, and keep the door open for a call if the issue turns out to be more complex.
Use this template when the request is time-sensitive but not confidential, emotionally charged, or hard to resolve in writing. It is especially useful for teams that overuse meetings, new managers learning communication norms, and anyone who needs to practice saying “let’s handle this in chat” without sounding abrupt. The scenario is intentionally narrow so the learner can focus on the channel decision, the opening line, and the tone of the redirect.
Do not use this template when the real skill is negotiation, conflict resolution, or handling a sensitive topic that genuinely requires live discussion. It is also not the right fit if the learner needs to practice detailed decision-making, because the scenario is about choosing the lightest effective channel and keeping momentum. A strong attempt should feel efficient, respectful, and collaborative, not evasive.
How to use this template
- Read the situation and note the request size, urgency, and sensitivity before starting the roleplay.
- Begin the conversation with Jordan and respond as you would in a real message thread, not as a scripted speech.
- State whether the request can be handled asynchronously, explain your reasoning clearly, and offer a concrete chat-based alternative.
- Complete the attempt and review the scored rubric to see whether you stayed collaborative while steering the request.
- Retry with a revised opening line if you sounded too blunt, too vague, or too eager to schedule a meeting.
Best practices
- Name the channel decision early so the teammate does not have to guess whether you are agreeing to a meeting.
- Use a specific async alternative, such as asking for the wording in chat or suggesting a short message thread with the relevant context.
- Acknowledge the time sensitivity before redirecting, so the learner does not sound like they are minimizing the request.
- Reserve a live conversation for cases that are complex, confidential, or likely to need back-and-forth clarification.
- Keep the tone collaborative by framing the redirect as the fastest path to a resolution, not as a rejection.
- If the teammate pushes back, restate the reason for async and offer a call only if the scope expands.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this roleplay template help learners practice?
It helps learners practice deciding whether a request belongs in chat, email, or a live meeting. The focus is on politely redirecting a small ask to an async channel without sounding dismissive. Learners also practice explaining the reason for the channel choice and offering a clear next step.
When should I use this template instead of a meeting-skills scenario?
Use it when the main skill is channel selection, not the content of the request itself. This template fits situations where the ask is simple, time-sensitive, and likely resolvable in a short written exchange. If the issue is complex, emotional, confidential, or requires live negotiation, a different scenario is a better fit.
Who should run this practice scenario?
A manager, team lead, enablement partner, or individual learner can run it. It works well in onboarding, communication training, and manager coaching because the learner only needs to handle one short conversation. It is also useful for teams that want to reduce unnecessary meetings.
How often should learners repeat this scenario?
Repeat it until the learner can consistently identify when async is enough and when a live conversation is warranted. Because the scenario is short, it works well as a quick practice drill or a warm-up before a broader communication session. Repeating with different temperaments helps learners avoid sounding rigid.
What is the most common mistake this template surfaces?
The most common mistake is jumping straight to a meeting without checking whether the request can be handled in chat. Another frequent issue is giving a blunt redirect that feels like a refusal. Strong attempts acknowledge the request, explain the channel choice, and still make progress.
Can this template be customized for different teams?
Yes. You can swap in different request types, such as wording edits, status questions, or quick approvals, while keeping the same decision point. You can also adjust the persona’s temperament to make the learner practice with a busier, more skeptical, or more collaborative teammate.
Does this template connect to any integrations or workflows?
It can be paired with the tools your team already uses for chat, task tracking, or meeting scheduling. The scenario is especially useful when your workflow includes Slack, Teams, email, or calendar invites and you want people to choose the lightest effective channel. The roleplay itself stays focused on the communication decision.
How is this better than teaching channel choice informally?
Informal coaching often stays abstract, while this template gives learners a realistic moment to respond in real time. That makes it easier to practice the exact wording they will use with coworkers. It also gives a scored rubric so the learner knows whether they actually redirected the request well.
Related templates
Go deeper on the topic
-
Asynchronous communication is any exchange where the sender and receiver are not in the same moment — written messages, recorded video, shared docs, threaded...
-
Collaboration is the coordinated work of two or more people toward a shared outcome — arguing, deciding, producing, and shipping. It is not the same as...
-
Communication is the movement of information from one person or group to another — announcements, updates, instructions, questions, acknowledgements....
-
Communication at work is the practice of moving information reliably — announcements, decisions, expectations, problems — between the people who have it and...
Ready to use this template?
Every employee gets a seat. Request pricing for Performance & Learning and we quote into a workspace with Steer a Request to the Right Channel ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.