Meet Dial.

Two students who'd gone silent for weeks, surfaced automatically and reconnected within minutes.

Watch this first. It walks through two real cases from a Friday test. Tre'Vante had sat untouched for a month after saying he'd uploaded his DOT physical — the kind of open loop that stays buried in Quo until the student is gone. Dial scored him an 89 and surfaced him on its own; a call and an email later, he was back on track to enroll. Hassan had been inactive two months, uploaded his license on Friday, and a case opened one minute later with outreach already drafted. The point of both: you don't dig for these students anymore. They come to you while there's still time to act.

Students are split by stage and ranked by a triage score. Work them top to bottom.

Open your stage — theory training, enrollment, yard, or job searching. Each student appears in exactly one stage and carries a triage score from 0 to 100. A higher score means the student both needs attention and is likely to respond to it, so working the queue in order puts your time where it changes outcomes. Click a student to open their case.

• The score combines three things: risk (moving slower than peers, momentum dropping), uplift (likely to respond, blocker we can fix), and cost (coach time the right move takes). It surfaces the students who are at risk and reachable, not the ones you can't help.
• Read the full thread on the right, including calls with playable transcripts.
• Switch between the Human tab (messages sent by an operator on a human number) and the Journey tab (automated comms from the agent's number or inbox).
• Approve the AI draft to send it, or reject it. Rejecting asks why, then drops you into a normal message UI that works like Quo.

Dial picks the channel each student actually answers and drafts the message, so you don't start cold.

Reaching out on the wrong channel wastes the contact. Each student row shows the suggested medium and whether an auto-draft is ready. Dial sets the channel from the student's own inbound history: Jamal picks up calls, so his suggestion is a call; Duane only ever emails, so his is an email you send straight from the queue via success@ or support@emergecareer.com.

Each draft comes with the agent's read of the context — a plain-language summary of the student's profile, why they scored high, and what the outreach should accomplish. Use it to send fast with a clear objective, or as a starting point you edit before sending.

No draft, or one you disagree with? Write your own with the student's full context already in front of you.

You won't always take the AI's suggestion. When you write from scratch, the stage checklist in the sidebar shows exactly where the student stands — Duane has finished 11 of 21 videos, zero practice exams, no permit uploaded — so you ask for the right next step instead of guessing. Don't push him to schedule his CLP when he hasn't finished his videos; re-engage him on the videos.

• Click a checklist snippet to drop the correct link for a missing requirement into your message. No hunting for URLs.
• Open Quick Actions to send a financial-aid or reimbursement link in one click — useful across stages, since these aren't tied to any one checklist.
• Always pair the ask with the link that removes the friction to doing it.

Close a case when the work is done. Snooze it when the work has to wait.

A case is a unit of work. Close it when that unit is finished — a student needed help scheduling a permit exam, and it's now scheduled. Closing removes the student from your queue, auto-captures the time you spent (in the queue, on their profile, and on calls), and asks how it was resolved. Don't close mid-interaction; close when something is actually complete. Over time, that captured time tells us which blockers cost the most coach hours.

Snooze when the work spans days — a student takes their exam Friday, or fails a DOT physical and waits 45 days for the next one. Pick a span, leave yourself a note, and the case reopens on your queue when it's due. Your note feeds the AI's next draft. This is what keeps long-horizon students from falling through the cracks while they wait.

Every text you send carries a live delivery status, so you can tell what reached the student and what didn't.

Quo has had reliability issues, and until now we couldn't see which messages actually made it to students. Each outbound text now shows where it is on its way to the carrier, in real time as you watch it move:

• Sending — a spinner and an iMessage-style bar across the top. The message has left the platform but hasn't reached Quo yet. It will persist and keep trying, so you can move on.
• Orange dot — the message reached Quo but hasn't yet reached the carrier.
• Delivered — the orange dot clears. The message reached the carrier, and if the student's line is active, it's on their phone.

Use it for confidence that a message sent, and for insight into why one didn't. When a follow-up matters, watch it land before you move to the next case.

Search, filters, keyboard shortcuts, and read state — shown here in the job-search stage.

• Search to reach a student who has no open case. Your queue only lists open cases; searching a student lets you message them, which opens a case.
• Filter the view: Triage (default, ranked by priority), Proactive outreach (system-flagged only), Reactive outreach (cases started by an inbound), or an iMessage view sorted by last touch. Stay on Triage — it ranks by impact, which is what the queue is for. Use the iMessage view only when you're trading messages with several students at once.
• Filter by channel to see all comms, or just texts, emails, or calls.
• Use the keyboard: Ctrl + Backspace rejects a draft, Ctrl + Enter approves and sends it.
• A blue dot next to a name means an unread inbound is waiting on you.
• Copy the phone number before opening Quo. The link lands on Quo generally, not the student's thread, so copy first.