How to Use This Document

Each slide card below contains the AI voiceover script (what the learner hears) and screenshot/visual requirements (what the learner sees). Expand a card to see both. Use the status badges to track what’s captured vs. what still needs to be created.

Module Duration: ~33 minutes (self-paced)  |  Tool: Articulate 360 (Rise or Storyline)  |  Track: Track 2 — Specialized Deep-Dive

Voiceover script
Screenshot needed
Already captured (Mar 26)
Needs capture
Design/build in Articulate
0

Welcome & Objectives

2 min · 2 slides
0.1
Title Slide
VODesign
Voiceover Script
Every account has a lifecycle. When a customer needs to close their account — whether by choice or circumstance — how you handle it determines whether they leave as a detractor or a future return customer. In this module, you’ll learn the complete closure process: from routing the request, to executing the checklist, to handling the sensitive scenarios that trip up even experienced agents.
Visual
Title graphic Design in Articulate
Module title: “Account Closure/Shutdown”
Subtitle: “Closing with confidence and care”
PrePass branding / account lifecycle icon
0.2
Learning Objectives
VODesign
Voiceover Script
By the end of this module, you’ll be able to: identify the six reasons accounts get closed or shut down. Route closure requests correctly based on fleet size and CSM status. Execute the closure checklist for PrePass and PrePass Plus/Tolls accounts. Handle sensitive scenarios — including deceased customers, bond accounts, and consolidations. And create proper documentation and refund cases in D365.
Visual
Objectives list graphic Design in Articulate
Numbered list with icons for each objective. Appear sequentially with VO timing. Five objectives total.
1

Why Accounts Close

3 min · 3 slides
1.1
The 6 Closure Types — Overview
VODesign
Voiceover Script
There are six reasons an account gets closed or shut down. Not every closure looks the same, and your role is different depending on the type. Let’s walk through all six. Click on each card to learn what triggers it and what it means for you as an agent.
Visual
6-card interactive graphic Design in Articulate
Six clickable cards or wheel segments, each revealing detail on click:
1. Billing Related — Past Due · 2. Collection Related · 3. Customer Request · 4. Credential Related · 5. Consolidation · 6. Safety Related (ISS Score)
Cards remain dimmed until clicked.
Interaction Design Build as clickable hotspot cards (Storyline) or image-and-text block with tabs (Rise). Learner must visit all 6 before proceeding.
1.2
Card Details — Each Closure Type
VODesign
Voiceover Script
Billing Related — Past Due: the account goes inactive because of non-payment. The customer has to resolve the balance before closure can be processed. Collection Related: the account has been escalated to collections. Special rule here — no credits for returned devices. No exceptions. Customer Request: this is the most common type you’ll handle. The customer voluntarily wants to close. We split these into controllable and uncontrollable reasons — we’ll cover that next. Credential Related: a change of credential triggers inactive status. Consolidation: the customer is moving trucks to another account. This isn’t a lost customer — the truck count stays the same. And Safety Related: a failed ISS safety check triggers closure.
Visual
Card reveal content Design in Articulate
Each card from slide 1.1 reveals a brief description and key callout when clicked. This VO plays as learner explores the cards — or use per-card audio snippets.
1.3
Takeaway — Customer Request Is Your Focus
VODesign
Voiceover Script
Customer Request is the one you’ll handle most often — and it’s the one where your process matters most. The other types are triggered by system events or other departments. But when a customer picks up the phone and says “I want to close my account,” that’s your call to own. Let’s dig into how to route those calls.
Visual
Transition callout Design in Articulate
Callout box highlighting “Customer Request” card. Transition arrow pointing to Section 2.
2

The Routing Decision

4 min · 4 slides
2.1
Gather Three Things First
VODesign
Voiceover Script
A customer calls and says they want to close their account. Before you touch anything in CRM, you need three pieces of information. Click to reveal each one. First: what’s the cancellation reason? Second: does the account have a Customer Success Manager? And third: how many enrolled vehicles? These three data points determine everything that happens next — who handles the closure, what steps to follow, and where the case goes.
Visual
3-reveal interaction Design in Articulate
Three clickable panels that reveal on click: (1) Cancellation Reason, (2) CSM Status, (3) Fleet Size. Each reveals with a brief explanation. Learner must click all three before proceeding.
2.2
Decision Tree — Route by Fleet Size & CSM
VOScreenshotDesign
Voiceover Script
Here’s the routing decision tree. Follow the path from the top. If the account has a CSM — any fleet size — you assign the case to that CSM. If there’s no CSM, fleet size determines everything. Fleet one to twenty-four: you handle it. That’s your lane. Fleet twenty-five to ninety-nine: convert to a case and assign to Beverly Evans in the Retention group. Fleet one hundred to four ninety-nine: email Jennifer Millard. Fleet five hundred plus: email Brett Jackson. This decision tree is one of the most important things you’ll memorize. Let’s make sure you know it.
Visual
Interactive decision tree flowchart Design in Articulate
Branching flowchart: “Customer wants to close” → “Has CSM?” → YES = assign to CSM / NO → fleet size branches.
Build as interactive click-through flowchart in Storyline or process block in Rise. Learner follows their path.
Key Rule Customer Care does NOT handle Handling Fee closures. If the account is inactive due to billing or collections, the customer must resolve the issue first — payment, transfer, or Collections case — before you can close.
2.3
Controllable vs. Uncontrollable Reasons
VODesign
Voiceover Script
Closure reasons are split into two categories: controllable and uncontrollable. Controllable reasons are things we could potentially address — competitor, billing or invoice issues, customer service dissatisfaction, minimal bypass, and price. Uncontrollable reasons are outside our control — deceased, impacted by Hurricane Helene, medical ailment, out of business, retired, safety, selling business, truck repair, route change, consolidation, moving to company account, and switching companies. Here’s the important nuance: “uncontrollable” does not mean irreversible. A customer who went out of business might come back. A deceased closure could have been initiated by a malicious actor. The closure status matters: accounts in “Initiated” status can be reactivated by agents. “Pending Archive” requires a Team Lead. And “Archived” is permanent — gone for good.
Visual
Two-column tabbed layout Design in Articulate
Tab or accordion: Controllable (5 items) vs. Uncontrollable (12 items).
Below: three-tier status graphic: Initiated (agent) → Pending Archive (TL) → Archived (permanent). Color-coded green → amber → red.
2.4
Quick Check — Routing Scenarios
VODesign
Voiceover Script
Let’s test your routing instincts with two quick scenarios. [Pause for interaction.] Scenario one: a customer with 15 trucks, no CSM, calls to close due to price. What do you do? [Pause.] You handle it — fleet one to twenty-four with no CSM is your lane, regardless of whether the reason is controllable or uncontrollable. Scenario two: a customer with 45 trucks, no CSM, calls to close due to dissatisfaction. [Pause.] Convert to a case and assign to Beverly Evans in the Retention group. Fleet twenty-five to ninety-nine with no CSM goes to Retention — every time.
Visual
2-scenario interaction Design in Articulate
Two scenario cards. Each presents fleet size + CSM status + reason. Learner selects the correct routing. Reveal correct answer with feedback.
3

Closing a PrePass Account

5 min · 4 slides
3.1
Step 1: Initiate Closure in CRM
VOScreenshotCaptured
Voiceover Script
You’ve determined this is a PrePass-only account, fleet one to twenty-four, no CSM. Here’s your checklist. Step one: initiate the closure in CRM. From the main account page, click Status Details. Change the Account Status Indicator to “Initiated.” Select the closure reason in the Account Closure Reason dropdown. Then change Operation Status Reason to “Customer Requests Closure.” Click Save. One important check before you do this — look at the Billing status. If it’s inactive, the customer must pay their balance first. You cannot close an account with an outstanding balance.
Screenshot Requirements
CRM_StatusDetails_View.png Captured Mar 26
Source: CRM status details folder — Status Detail view

CRM_AccountCloseIndicator.png Captured Mar 26
Source: CRM status details folder — Account Close Indicator field

CRM_AccountClosureReason.png Captured Mar 26
Source: CRM status details folder — Account Closure Reason dropdown

CRM_OpStatusReason.png Captured Mar 26
Source: CRM status details folder — Operation Status Reason field

Show as a step-through: numbered annotations 1 → 2 → 3 → 4 over each screenshot.
Billing Check If Billing status is inactive (Non Payment/Balance Due), the customer must resolve the balance before closure. This should appear as a persistent warning callout.
3.2
Steps 2–4: Delete Trucks, Explain Billing, Send Return Instructions
VOScreenshotCaptured
Voiceover Script
Step two: delete all trucks from the account. Step three: explain billing. Tell the customer we bill one month behind — they’ll receive a final bill after the account is closed. Make sure they understand this so they’re not surprised. Step four: send device return instructions. For PrePass-only accounts, use email template CCC 13.2. Devices must be returned within 30 days.
Screenshot Requirement
D365_EmailTemplate_CCC132.png Captured Mar 26
Source: D365 email folder — CCC 13.2 template selection UI

Show the template selection screen with CCC 13.2 highlighted.
Template Reminder PrePass-only = CCC 13.2. PrePass Plus/Tolls = CCC 13.1. The numbers are close — double-check before sending.
3.3
Steps 5–6: Collections Rule & Call Documentation
VOScreenshotCaptured
Voiceover Script
Step five: check for collections. If the account is or was in collections and the customer is returning a Mark IV, Fusion MD, ElitePass MD or NY, or SelectPass — no credits for returned devices. No exception. This is a hard rule, so don’t let a customer talk you into making an exception. Step six: create your phone call activity in D365. Five9 Agent Assist auto-generates the call summary — it appears in the phone call Timeline tab. You review and verify it, then copy it and paste it into the Description field on the Phone Call tab.
Screenshot Requirements
D365_PhoneCall_Timeline.png Captured Mar 26
Source: D365 call documentation folder, screenshots 11–13 — AA summary in Timeline tab

D365_PhoneCall_Description.png Captured Mar 26
Source: D365 call documentation folder — Description field where summary is pasted

Show as step-through: (1) AA generates summary in Timeline, (2) Agent copies, (3) Pastes into Description.
Collections — No Exception NO credits for returned devices on collections accounts. Mark IV, Fusion MD, ElitePass MD/NY, SelectPass. This is absolute.
3.4
Step 7: Close with Care
VODesign
Voiceover Script
Step seven: close with care. End the call professionally: “It was a pleasure doing business with you. If you decide to return, we will be happy to help you.” That last impression matters. You also have optional steps depending on the situation: report devices as lost or stolen if needed. Create a refund case if there’s a balance to refund. Create a trailer plate removal case if applicable. We’ll cover refund cases in detail in Section 6.
Visual
Script callout card + checklist summary Design in Articulate
Display the closing script in a styled callout box. Below: a recap checklist of all 7 steps with checkmarks, plus the 3 optional/conditional steps indicated with a different icon.
4

Closing a PrePass Plus / Tolls Account

5 min · 5 slides
4.1
What’s Different About Plus/Tolls?
VODesign
Voiceover Script
PrePass Plus and Tolls accounts follow the same basic flow as PrePass-only closures, but with additional steps. The key differences are sticker deactivation, the trailer plate report, and a critical toll service warning. Let’s walk through the full checklist. Pay attention to the steps marked with a star — those are unique to Plus and Tolls accounts.
Visual
Side-by-side comparison Design in Articulate
Two-column layout: PrePass (7 steps) vs. PrePass Plus/Tolls (12 steps). Differences highlighted with star icons. Consider an animated reveal where matching steps are grey and unique steps glow.
4.2
Steps 1–3: Initiate, Inform, Delete Trucks
VOScreenshotCaptured
Voiceover Script
Steps one through three are the same as PrePass. Initiate the closure in CRM — Status Details, set to Initiated, select closure reason, operation status to Customer Requests Closure, save. Step two: inform the customer. Use this language: “I initiated your account closure. The account will not be fully closed until we receive the device or devices and you pay the final bill.” This sets expectations early. Step three: delete the trucks on the account.
Screenshot Requirement
CRM_StatusDetails_View.png Captured Mar 26
Source: Same CRM status details screenshots from Section 3. Reuse with brief reference.
4.3
Steps 4–5: Deactivate Stickers & Trailer Plate Report
VOScreenshotCaptured
Voiceover Script
Here’s where Plus and Tolls diverge. Step four: deactivate any stickers on the account. This is a Plus/Tolls-only step — PrePass accounts don’t have stickers. Step five: check the Trailer Plate Report and create a case. Assign the case to the Utah Supervisor group, owner Leidy Canas, category Trailer Plate Update. In the notes, write: “Please delete any trailer plates associated to account number” and include the account number and note that the customer closed the account. Leidy handles all trailer plate add, edit, and remove cases.
Screenshot Requirements
TrailerPlateReport_FullHistory.png Captured Mar 26
Source: Trailer plate subfolder — Full Trailer Plate History report

TrailerPlateReport_URL.png Captured Mar 26
Source: Trailer plate subfolder — SQL Server Reporting Services URL

Show the report and the case creation fields with sample notes template.
Case Template Group: Utah Supervisor · Owner: Leidy Canas · Category: Trailer Plate Update · Notes: “PLEASE DELETE ANY TRAILER PLATES ASSOCIATED TO ACCT # _____. CUSTOMER CLOSED THE ACCOUNT.”
4.4
Steps 6–8: Billing, Toll Warning & Device Return
VOScreenshotCaptured
Voiceover Script
Step six: explain the billing cycle — same as PrePass, we bill one month behind. Step seven is critical and unique to Plus and Tolls. You must warn the customer: toll service is still active. The customer is responsible for any toll charges until the device is deactivated. If they want tolls to stop immediately, the device must be reported “not returned” the same day. They can return the device later for a partial fee credit — but only for ElitePass and Fusion MD. This is the step that catches new agents off guard. Don’t skip it. Step eight: send device return instructions using template CCC 13.1 — note that’s a different template than PrePass-only.
Screenshot Requirement
D365_EmailTemplate_CCC131.png Captured Mar 26
Source: D365 email folder — CCC 13.1 template (includes toll fees and deposit refund timeline).
Toll Warning — Do Not Skip Toll service is STILL ACTIVE after closure is initiated. Customer is responsible for charges. Devices must be reported “Not Returned” same day to stop tolls. This must be a persistent, prominent callout.
4.5
Steps 9–12: Collections, Refund, Expectations & Close
VODesign
Voiceover Script
Step nine: the collections rule applies here too — no credits for returned devices on collections accounts. No exception. Step ten: create a refund case. We’ll cover the full refund case process in Section 6, but know that PrePass Plus and Tolls accounts always need a refund case at closure. Step eleven: set refund expectations. Use this language: “Once your device is returned, and your final bill is paid, the refund process will begin, which can take up to 45 to 60 days to credit to your payment method.” Step twelve: thank the customer and close the call professionally.
Visual
Full checklist recap Design in Articulate
Complete 12-step checklist with checkmarks. Star-marked steps (4, 5, 7) highlighted as Plus/Tolls-only. Include the refund expectation script as a callout card.
5

Special Scenarios

5 min · 4 slides
5.0
Special Scenarios Overview — 3 Tabs
VODesign
Voiceover Script
Not every closure is routine. Some require extra care, different rules, or a completely different approach. We’re going to cover three special scenarios: deceased customer closures, bond account closures, and account consolidations. Click on each tab to learn the scenario.
Visual
3-tab interaction Design in Articulate
Three tabs: Deceased Customer | Bond Account | Consolidation
Tabs remain dimmed until clicked. Learner must visit all three before proceeding.
Interaction Design Build as tabbed interaction (Rise: tabs block; Storyline: tab interaction). Each tab opens to a mini-scenario with key steps and callouts.
5.1
Tab 1: Deceased Customer
VODesign
Voiceover Script
A caller says they’re calling about their father’s account. He passed away last week. First, lead with empathy: “I’m so sorry to hear about your loss. Please accept our condolences.” Then follow the process. Set the CRM Closure Reason to “Deceased.” Communicate billing gently: “You may receive a final invoice, but if settling it isn’t possible, you can disregard it. We won’t take any further action.” Do not create a device adjustment to write off the device. Remove Autopay to prevent automatic charges. For toll accounts, inform the caller that pending charges will be deducted from the toll deposit. Then close the account using standard notes. The key principle: we do not pursue payment from deceased customers. No collections. No further billing. Mark as Deceased and let billing processors handle the rest.
Visual
Empathy-styled scenario card Design in Articulate
Different visual treatment for this tab — softer color palette, empathy icon.
Step list with compassion tips alongside each step.
Prominent callout: “Do NOT create device adjustment. Do NOT pursue collections.”
Common Mistake Do NOT create a device adjustment to write off. Do NOT pursue payment or send to collections. These are the two most common errors on deceased closures.
5.2
Tab 2: Bond Account Closure
VODesign
Voiceover Script
A customer wants to close their account. You check CRM and see they have a Surety Bond. This changes things. First, check the Surety Program field in CRM. If it’s a bond account, do not create a Billing Refund case. There is nothing to refund — the customer never paid a deposit to PrePass. The bond replaced it. Advise the customer: once their devices are returned and the final bill is paid, they need to contact their bond agency to cancel the bond. That’s their responsibility, not ours. Once they cancel, we receive a notice and mark the bond inactive. The biggest mistake agents make here is telling a bond customer to call back for a deposit refund. They didn’t pay us a deposit. There’s nothing for us to refund.
Visual
Bond scenario card + trigger table Design in Articulate
Step list with prominent “NO Billing Refund case” callout.
Include trigger reference table: Balance past due (>39/>18 days), 90% Surety reached (2 biz days), AutoPay removed/declined (5 biz days).
Key Rule Bond = NO refund case. The customer never paid a deposit to PrePass. Redirect them to their bond agency.
5.3
Tab 3: Consolidation
VODesign
Voiceover Script
A customer is switching companies but will still drive with PrePass under the new company’s account. This is a consolidation — not a lost customer. The truck count stays the same. Here are the steps: verify service on both accounts and check device compatibility. If transferring between different services — say, Plus to PrePass — both accounts must be active. Initiate closure with the reason set to “Consolidation of the Account.” Transfer the trucks to the new account. If going from PrePass Plus to PrePass, check for stickers and deactivate them. Explain the billing cycle, provide device return instructions if they’re not transferring devices, and remember — the collections rule still applies. One important handoff: if the customer wants PrePass and PrePass Plus under the same DOT, transfer them to the Account Team.
Visual
Consolidation flow diagram Design in Articulate
Step-through process with decision point: “Same DOT, both services?” → YES = transfer to Account Team / NO = proceed with consolidation steps.
Include sticker deactivation reminder for Plus → PrePass transitions.
Handoff Reminder PrePass + PrePass Plus under the same DOT → transfer to Account Team. Don’t try to handle this yourself.
6

Refund Case Process & Handoffs

5 min · 6 slides
6.1
When Is a Refund Case Needed?
VODesign
Voiceover Script
This is where new agents make the most mistakes — getting the refund case right is critical. So let’s start with the decision: does this closure need a refund case? PrePass Plus and Tolls accounts: yes, always create a refund case at closure. PrePass-only accounts: only if there’s a balance to refund. Bond accounts: no. There’s nothing to refund — redirect the customer to their bond agency. One more thing: if a customer calls asking about a refund and a case already exists, place your phone call activity in the same existing case. Don’t create a duplicate.
Visual
3-path decision graphic Design in Articulate
Three paths: Plus/Tolls → Always · PrePass-only → If balance to refund · Bond → Never.
Build as an interactive decision: learner selects account type and sees the correct answer.
6.2
Create the Case from the Phone Call (D365)
VOScreenshotCaptured
Voiceover Script
The refund case starts life as a standard phone call conversion in D365. Here’s the step-by-step. First, fill the Regarding field at the bottom of the phone call screen with the account info. This field is sometimes blank — it must be filled before you save. Save the phone call. Then click the dropdown “Convert To” and select “To Case.” A popup appears: “This will close this phone call and convert it to a case.” Click OK. Your new case is now created with the phone call visible in the Timeline.
Screenshot Requirements
D365_PhoneCall_RegardingField.png Captured Mar 26
Source: D365 call documentation folder, screenshot 14 — Regarding field

D365_ConvertTo_Dropdown.png Captured Mar 26
Source: D365 call documentation folder, screenshot 15–16 — Convert To → To Case

D365_ConvertToCase_Popup.png Captured Mar 26
Source: D365 call documentation folder, screenshot 17 — confirmation popup

D365_NewCase_Created.png Captured Mar 26
Source: D365 call documentation folder, screenshot 18 — new case with timeline

Show as numbered step-through: 1 → 2 → 3 → 4 → 5.
6.3
Configure the Case for Billing Refunds
VOScreenshotCaptured
Voiceover Script
Now you need to configure the case for the Billing Refunds team. Edit the title to match the naming convention: “Refund” followed by the method — CC for credit card, CK for check — then a dash, then “CSLR” and the date. For example: Refund CC dash CSLR 03/26/26. Change the Assigned Group to Billing Refunds. Set the Owner to Unassigned. Then add a task: click the plus sign at the top right of the Timeline and select Task. In the description, use the template: the account name, “Would like Requested program amount refund sent to,” the payment method and number, “Account closed” and the closure date. Select a Category from the dropdown — this is required before you can save. Click Save and Close on the task.
Screenshot Requirements
D365_RefundCase_Title.png Captured Mar 26
Source: D365 refund request folder — case title convention

D365_RefundCase_AssignedGroup.png Captured Mar 26
Source: D365 refund request folder — Billing Refunds group assignment

D365_RefundCase_Task.png Captured Mar 26
Source: D365 refund request folder — task creation with template

Show as step-through with title convention prominently displayed.
Title Convention Refund [Method] – CSLR [MM/DD/YY]    Example: Refund CC – CSLR 03/26/26
6.4
Do NOT Resolve the Refund Case
VODesign
Voiceover Script
This is the number one rookie mistake on account closures, and we’re going to make sure you don’t make it. After adding the task, leave the case open. Do not resolve it. New agents frequently resolve the refund case out of habit because that’s what you do with standard cases — add task, mark complete, resolve, save and close. But the refund case is the exception. If the case is resolved, the Billing Refunds team will not work it. The case must stay open and active for the refund to be processed. Let me say it one more time: do not resolve the refund case.
Visual
Warning callout + comparison Design in Articulate
Large, prominent warning graphic: “DO NOT RESOLVE THE REFUND CASE”
Below: two-column comparison — Standard Case flow (add task → mark complete → resolve → save) vs. Refund Case flow (add task → save & close task → STOP — leave case open).
This is a key wrong-answer path in the knowledge check.
Rookie Mistake Alert If the refund case is resolved, Billing Refunds will NOT work it. The refund will not be processed. Leave the case OPEN. This is the #1 error on closures.
6.5
Refund Timeline & Customer Expectations
VODesign
Voiceover Script
The refund timeline is the number one source of customer callbacks, so teach it clearly. The 45 to 60 day clock does not start when the account is closed. It starts after the final bill is generated. And the final bill is generated the month following device return or deactivation. Here’s what that looks like. If an account is closed in May and devices are returned in June, the final invoice comes July first. The 45 to 60 day window starts July first. That means the earliest refund is mid-August. After the 60-day window, there’s additional processing time. Credit card and checking account refunds take 7 to 10 business days. Check refunds take 6 to 8 weeks. Reissued checks take 4 weeks. Two more rules: the refund goes to the most recently billed payment method. You cannot add a new card or account. If the billed method is invalid, the Billing Refunds Team issues a check to the account name. And do not request an expedited case unless it’s a billing error or it has exceeded the 60-day timeframe.
Visual
Timeline animation + processing table Design in Articulate
Animated or interactive timeline: Account Closed (May) → Devices Returned (June) → Final Invoice (July 1) → 45–60 Day Window → Refund Processed.
Below: processing time table (CC: 7–10 biz days, Checking: 7–10 biz days, Check: 6–8 weeks, Reissued: 4 weeks).
6.6
Handoffs — CSM, Retention & Escalation
VODesign
Voiceover Script
When handing off to a CSM or Retention, convert the phone call to a case in D365 and include detailed notes: customer name, account number, phone number, the person they spoke with, and the reason for wanting to close. For escalations — if a customer calls back saying their case hasn’t been processed — email the supervisor who owns your Team Lead. Adriana Rodriguez is the supervisor over TLs Brian Cooley and Stefani Torres. Eddy Encinas is the supervisor over TLs Galya Goodrich and Marangelie Boyer. CC the Enrollment Support Supervisor, Shawna Velasquez, or the CSM Manager — Jennifer Millard or Brett Jackson. Include the account name, account number, case number, assigned CSM, and escalation details.
Visual
Handoff reference card Design in Articulate
Two-panel layout: Left = Case handoff template (5 required fields). Right = Escalation path with supervisor names and TL assignments.
Build as a reference card the learner can revisit.
7

Knowledge Check

3 min · 5 slides
7.1
Q1: Routing — Fleet 45, No CSM
VODesign
Voiceover Script
Question one. A customer with 45 trucks, no CSM, calls to close their account due to price. What do you do?
Visual
Multiple choice interaction Design in Articulate
A) Close the account yourself — it’s a controllable reason
B) Convert to case, assign to “Retention” group and Beverly Evans ✓
C) Email Jennifer Millard
D) Transfer the call to Customer Success

Feedback: Fleet size 25–99 with no CSM goes to Beverly Evans in the Retention group, regardless of the closure reason.
7.2
Q2: Deceased Customer — What NOT to Do
VODesign
Voiceover Script
Question two. A family member calls about a deceased customer’s account. Which of these should you not do?
Visual
Multiple choice interaction Design in Articulate
A) Remove Autopay
B) Create a device adjustment to write off the device ✓
C) Set CRM Closure Reason to “Deceased”
D) Inform them a final invoice may arrive but they can disregard it

Feedback: Never create a device adjustment for deceased accounts. Simply mark as Deceased, remove Autopay, and let billing processors handle the rest.
7.3
Q3: Bond Account — Refund Request
VODesign
Voiceover Script
Question three. A customer with a closed bond account calls asking for their toll deposit refund. What’s the correct response?
Visual
Multiple choice interaction Design in Articulate
A) Create a Billing Refund case
B) Transfer to Financial Department
C) Advise them to contact their bond agency to cancel the bond ✓
D) Process the refund using their credit card on file

Feedback: Bond customers never paid a deposit to PrePass — the bond replaced it. There’s nothing for us to refund. They need to cancel through their bond agency.
7.4
Q4: PrePass Plus Closure — Step Ordering
VODesign
Voiceover Script
Question four. Put these PrePass Plus closure steps in the correct order.
Visual
Ordering/drag-drop interaction Design in Articulate
Drag-drop or ordering interaction. Correct order:
1. Initiate closure in CRM → 2. Inform customer → 3. Delete trucks → 4. Deactivate stickers → 5. Check Trailer Plate Report → 6. Explain billing cycle → 7. Warn toll service still active → 8. Email device return instructions (CCC 13.1) → 9. Create Refund Case

Feedback: The order matters — sticker deactivation and trailer plate check happen before billing and toll discussions.
7.5
Q5: Billing Inactive — What Comes First?
VODesign
Voiceover Script
Question five. A customer calls to close their fleet-12, no-CSM, PrePass-only account. Their billing status shows Inactive due to Non Payment. What must happen first?
Visual
Multiple choice interaction Design in Articulate
A) Proceed with closure — billing status doesn’t matter
B) Customer must resolve the balance (payment, transfer, or Collections case) before closure ✓
C) Transfer to Collections department
D) Email the supervisor for approval

Feedback: If the account is inactive due to billing or collections, the customer must resolve the issue before closure can be processed.

Passing score: 80% (4 of 5)
8

Summary & Resources

1 min · 1 slide
8.1
Key Takeaways & Resource Links
VODesign
Voiceover Script
Let’s recap. Always gather three things first: the closure reason, CSM status, and fleet size. Route by fleet size — you handle one to twenty-four with no CSM. PrePass Plus and Tolls have extra steps: stickers, trailer plates, and the toll warning. For deceased accounts: empathy first, no device adjustments, no collections. Bond accounts: nothing to refund — redirect to the bond agency. Document everything — use Agent Assist and the note template. And remember: the refund clock starts after the final bill, not when the account is closed. You now have the tools to handle any closure scenario with confidence and care. The way you close an account is the last impression a customer has of PrePass. Make it count.
Visual
Recap graphic + resource links Design in Articulate
7 key takeaways as a visual summary (icons + brief text).
Resource links section:
• Process for Closing an Account (KB)
• Account Status Indicators (KB)
• Deceased Customer Process (KB)
• Bond Request Handling Guidelines (KB)
• Refund Requests (KB)
• Device Return Instructions — CCC 13.1 (Plus/Tolls) / CCC 13.2 (PrePass)

Screenshot Inventory — Sections 0–8

#FilenameSectionSourceStatus
1CRM_StatusDetails_View.png 📂3.1CRM status details folderCaptured
2CRM_AccountCloseIndicator.png 📂3.1CRM status details folderCaptured
3CRM_AccountClosureReason.png 📂3.1CRM status details folderCaptured
4CRM_OpStatusReason.png 📂3.1CRM status details folderCaptured
5CRM_BillingStatus.png 📂3.1CRM status details folderCaptured
6CRM_OpStatus.png 📂3.1CRM status details folderCaptured
7D365_EmailTemplate_CCC132.png 📂3.2D365 email folderCaptured
8D365_PhoneCall_Timeline.png 📂3.3D365 call documentation folder (SS 11–13)Captured
9D365_PhoneCall_Description.png 📂3.3D365 call documentation folderCaptured
10D365_EmailTemplate_CCC131.png 📂4.4D365 email folderCaptured
11TrailerPlateReport_FullHistory.png 📂4.3Trailer plate subfolderCaptured
12TrailerPlateReport_URL.png 📂4.3Trailer plate subfolderCaptured
13D365_PhoneCall_RegardingField.png 📂6.2D365 call documentation folder (SS 14)Captured
14D365_ConvertTo_Dropdown.png 📂6.2D365 call documentation folder (SS 15–16)Captured
15D365_ConvertToCase_Popup.png 📂6.2D365 call documentation folder (SS 17)Captured
16D365_NewCase_Created.png 📂6.2D365 call documentation folder (SS 18)Captured
17D365_RefundCase_Title.png 📂6.3D365 refund request folderCaptured
18D365_RefundCase_AssignedGroup.png 📂6.3D365 refund request folderCaptured
19D365_RefundCase_Task.png 📂6.3D365 refund request folderCaptured
20Five9_AgentAssist_Panel.png3.3Nice-to-have — Content Needs #7Nice-to-Have
21D365_StandardCase_Resolve.png 📂6.4D365 call documentation folder (SS 19–25)Captured
22QC_ClosureCallTranscript.txtScenarioNice-to-have — Content Needs #5Nice-to-Have
19 of 22 assets already captured or confirmed (March 26). 2 are nice-to-haves (Five9 AA panel screenshot, QC call transcript). 1 standard case resolve flow is captured for comparison. Remaining slides use designed graphics built directly in Articulate.

Voiceover Summary — Sections 0–8

SlideTitleApprox WordsEst. Duration
0.1Title Slide~5520s
0.2Learning Objectives~6025s
1.16 Closure Types — Overview~4515s
1.2Card Details~13550s
1.3Takeaway — Customer Request~5520s
2.1Gather Three Things~7530s
2.2Decision Tree~11040s
2.3Controllable vs. Uncontrollable~14055s
2.4Quick Check — Routing~10040s
3.1Initiate Closure in CRM~10540s
3.2Delete, Billing, Return Instructions~7025s
3.3Collections & Call Documentation~10040s
3.4Close with Care~8030s
4.1What’s Different About Plus/Tolls~5520s
4.2Steps 1–3~8030s
4.3Stickers & Trailer Plates~10040s
4.4Billing, Toll Warning, Device Return~12045s
4.5Collections, Refund, Close~9035s
5.0Special Scenarios Overview~4015s
5.1Deceased Customer~15560s
5.2Bond Account~13050s
5.3Consolidation~12550s
6.1Refund Decision~8530s
6.2Create Case from Phone Call~9035s
6.3Configure for Billing Refunds~12045s
6.4Do NOT Resolve~10040s
6.5Refund Timeline~16060s
6.6Handoffs & Escalation~10540s
7.1Q1: Routing~2510s
7.2Q2: Deceased~2010s
7.3Q3: Bond~2510s
7.4Q4: Step Order~158s
7.5Q5: Billing Inactive~3012s
8.1Summary & Resources~12045s
34 voiceover scripts across sections 0–8. Total estimated voiceover: ~16 minutes 30 seconds. All scripts written and ready for AI voice generation.

Content Needs Status

#ItemStatusNotes
1Call documentation steps with Five9 AAConfirmedScreenshots 11–13 show full workflow
2D365 refund case process (screen-by-screen)ConfirmedScreenshots 14–25 + refund request folder
3CRM Status Details screenshotsDelivered6 screenshots covering all fields
4Device return email templates (CCC 13.1 & 13.2)DeliveredMarkdown text + 2 UI screenshots
5Real closure call transcript from QCNice-to-HaveWould strengthen scenario scripts
6Common rookie mistakesConfirmed#1: resolving refund case
7Five9 Agent Assist screenshot/demoNice-to-HaveGuidance Cards + Checklist appearance
8Trailer Plate Report screenshots + URLDelivered2 screenshots + SSRS URL
All 4 must-haves confirmed. Nice-to-haves #5 (QC call transcript) and #7 (Five9 AA panel) would strengthen the module but are not blocking the build.