Close the loop
The conversation ends, but the case keeps going. A good case note lets the next person pick up exactly where you left off.
The note is for the next person
Imagine Dana contacts Northline again next week. A different agent opens her case, and everything they know about the first conversation comes from what you wrote.
If the note says “fixed it,” they’ll have to ask Dana to explain everything again, and that second explanation is often where a frustrated customer becomes a lost one.
Four parts of every case note
Northline’s policy asks for the same four parts every time. Turn each card to see what belongs there.
Compare two notes
Both notes describe Jordan’s conversation with Dana from Lesson 2. Only one would help the next agent.
- Issue: Upset about which charge? Was the account verified? Was the duplicate confirmed?
- Evidence: What records were checked, and what did they show?
- Action: What does “fixed it” mean? There’s no reversal reference.
- Owner/update: Who will follow up, and by when?
The strong note is only a few lines longer. The difference is that it swaps vague words (upset, fixed, will follow up) for details the next person can check: an account, a record, a reference number, a name, and a time.
Your turn: write the note
Write a case note for the conversation below. You’ll then compare it with a model note and review it yourself.
Case: Ana Lima · NL-60318
- Account authenticated through the approved process.
- Ana says she was billed twice in June.
- Order ORD-9112: one monthly plan purchase.
- Transactions: two $24.00 payments on Jun 2, both Settled.
- You reversed the duplicate (ref REV-31877) and told Ana you’ll email her a confirmation by 4:00 PM ET today.
Use your own initials as the owner. At least 40 characters.
Your note
Model note
Keep this beside you
The whole course fits on one page. Download the job aid and keep it next to your support console.
Acknowledge · Verify · Resolve · Record
Pending authorization: explain it, say what you’ll check, and set an update time.
Extra compensation or exception: prepare a supervisor handoff and don’t promise approval.
Prototype download (an HTML file you can print). The production version is planned as an editable Canva design with an accessible PDF export.
Designer’s note · instructional strategy and native build plan
Purpose
Objective 4: write a concise case note that records evidence, action, and next steps. The case note is the course’s most transferable on-the-job behavior and the most practical thing to measure in a pilot, for example by checking how complete real notes are.
Design decisions
- Write it for the next reader. The lesson opens with the agent who reads the note later, which gives learners a concrete reason the note matters beyond compliance.
- Contrasting cases. Weak and strong notes about the same conversation, so the only thing that differs is the quality of the note.
- Honest self-review. Free text isn’t scored automatically for meaning. Learners compare their note with a model and check four criteria themselves. If they leave a box unchecked, they’re prompted to revise.
- Job aid as the takeaway. The four-step structure from the whole course is condensed onto one page for use on the job.
Native Rise 360 build map
| Prototype element | Planned build |
|---|---|
| Four parts | Flashcard grid |
| Weak vs. strong note | Tabs interactive |
| Missing-element check | Knowledge check: multiple choice |
| Write and self-review | Storyline block (text-entry variable, model-note layer, four checkbox self-review). Rise has no long-form text-entry block. |
| Job aid | Attachment block with an accessible PDF exported from Canva |
Still to verify in the native build
The text-entry experience on mobile, how screen readers handle the comparison, and whether the job-aid PDF is accessible.
