Check before you promise
What the customer tells you is where you start. It isn't your evidence yet. Follow one agent through a duplicate-charge complaint, then try it yourself.
Why the pause matters
When a customer is upset, a promise can look like the fastest way to calm them down: “I’ll refund that right now.”
A promise made before you check the record is a guess. If the guess is wrong, you now have two problems: the original complaint, plus a commitment you can’t keep or weren’t authorized to make.
You’ll follow a worked example, read an annotated billing record, and answer two knowledge checks. Each activity unlocks the next section.
Worked example: Dana’s duplicate charge
Follow Jordan Okafor, a Northline support agent, through a single complaint. Use the buttons to move through each step.
A customer opens chat
Dana is frustrated and is making a specific claim. Jordan has to take the claim seriously without assuming it’s true.
Acknowledge the impact
Why it works: Jordan names the cost to Dana (her time) and moves straight toward the evidence. Nothing has been promised yet.
Verify the account
Before discussing anything account-specific, Jordan confirms Dana’s identity through Northline’s approved authenticated support process.
Inspect the record
Jordan opens the order record and the masked transaction list.
| Date | Item | Amount | Status |
|---|---|---|---|
| Mar 3 | Monthly plan | $24.00 | Settled |
| Mar 3 | Monthly plan | $24.00 | Settled |
The order record shows one March subscription purchase. The transaction list shows two settled payments for it.
Apply the policy condition
Both conditions are met: one purchase, two settled payments. The reversal is within Jordan’s authority, so it doesn’t need to be escalated.
Resolve and commit
The commitment is specific and something Jordan can deliver. He says nothing about bank timing, which he doesn’t control.
What Jordan didn’t do
- Promise a refund before checking the record
- Ask for a password or full card number
- Offer an extra credit he isn’t authorized to give
- Escalate a case that was within his authority
Read the record like Jordan
This is the console view Jordan used. Select each numbered marker to see what he checked and why. View all four to continue.
| Order record | ||
|---|---|---|
| ORD-7730 | Monthly plan · March | Qty 1 |
| Date | Amount | Card | Status |
|---|---|---|---|
| Mar 3 | $24.00 | •••• 4417 | Settled |
| Mar 3 | $24.00 | •••• 4417 | Settled |
1. Verified first
The authenticated support process is complete before any account details are discussed. Until you see this, keep the conversation general.
2. One purchase
The order record shows a single March subscription. If Dana had two subscriptions, two charges could be correct.
3. Both settled
Settled means the payment completed. Only two settled payments make a verified duplicate. A pending authorization doesn’t count.
4. Masked card
The console shows only the last four digits. That’s all you need, so never ask the customer for the full number.
0 of 4 viewed
Keep the policy close
You don’t need to memorize this policy. You need to know where it is and what each condition means. Open any item to review it.
Key takeaways
In Lesson 3 you’ll handle three cases yourself, with less guidance each time.
Designer’s note · instructional strategy and native build plan
Purpose
This lesson addresses Objectives 1–3: identify the concern and the facts still needing verification, respond in a way that acknowledges impact, and select a remedy within the agent’s authority. It is the fully guided stage before the Storyline practice, where guidance fades.
Design decisions
- Worked example before practice. New agents watch the full sequence modeled once, with the reasoning visible, before they have to make the decisions themselves.
- The record is the teacher. The labeled graphic shows learners which details in the console prove a duplicate, so the policy rule is tied to something they will actually see on the job.
- Feedback names the error. Each distractor is a plausible workplace mistake (a premature promise, an invented timeline, an unnecessary escalation). Its feedback explains why it fails and cites the policy. A second wrong attempt reveals the best response.
- Gated continues. Each interaction unlocks the next section, so learners can’t scroll past the evidence.
Native Rise 360 build map
| Prototype element | Planned Rise block |
|---|---|
| Opening statement | Statement block |
| Worked example | Process interactive |
| Annotated console | Labeled graphic over an original record image (Illustrator) |
| Policy reference | Accordion |
| Two checks | Knowledge check: multiple choice. Per-choice feedback depends on the Rise version; if it isn’t available, use a Storyline block. |
| Section gates | Continue divider set to “Complete block above” |
| Takeaways | Flashcard grid |
Still to verify in the native build
Keyboard and screen-reader behavior, contrast, mobile layout, and the actual completion behavior of each Rise block. This prototype doesn’t claim WCAG conformance.
