Handoffs, @ Tags & Teamwork
No customer should ever know your shift schedule, your lunch break, or that they're talking to a different advisor than the one who wrote them up. Numa's internal tagging makes that possible — but only if you build the habit. Clean handoffs are the difference between "one team taking care of me" and "I had to start over three times today."
Use Numa @ tags to hand off cleanly between advisors, departments, and shifts — so the customer always feels handled by one organized team.
Why Handoffs Are Where Most Comms Break Down
The customer's experience falls apart at the seams between people. Examples that happen every day:
- Advisor goes to lunch. Covering advisor doesn't know what was promised. Customer calls. Confusion.
- Parts is checking on a backorder. Advisor doesn't know. Customer asks for an update. "Let me check…" silence.
- BDC scheduled an appointment with notes. Advisor never reads them. Customer arrives and is asked to repeat everything.
- Shift change at 5 p.m. Night advisor inherits the RO with no context. Calls back the next day with the wrong info.
Numa @ tags fix every one of those scenarios — when used.
The @ Tag Patterns
1. Lunch / EOD Handoff
Before you walk out — open the Numa thread for any waiting customer and @mention the covering advisor with a one-line summary:
@MikeT — covering for me until 1:30. Mrs. Carter is waiting on a Touch 2 update — Pilot is in shop, ETA 3pm. If James the tech texts you with anything, just reply to her with the update. Thanks man.
Covering advisor now has the full picture. No sticky note to lose. No verbal handoff to forget. Customer experience seamless.
2. Department Handoff (Parts, BDC, Cashier)
Need parts to check stock? Need BDC to follow up on a no-show? Need cashier to apply a goodwill credit? @ tag them in the thread:
@parts — need water pump availability for Mrs. Carter's 2019 Pilot, VIN 4471. Customer waiting, hoping to do it today if possible. Ping me when you know. Thx.
Parts gets the ping with full context. They don't have to come find you. You don't have to leave the customer. Win-win-win.
3. Manager Escalation
For a customer who needs goodwill, an exception, or a tough call — @ tag the service manager BEFORE you bring them into the conversation:
@TracyS — quick goodwill ask. Mr. Reyes (loyalty customer, 4 years) had his Tahoe delay overnight last visit. Today's $620 brake job — could we knock $50 off as a recovery? Will tell him before he leaves if you approve.
Manager can approve / counter-offer in 30 seconds via the app. No physical hunt. No customer waiting in the lounge wondering.
The Walk-Around Dictation Habit
From Lesson 2 — when you're in the drive, use voice-to-text into Numa's internal note field. This becomes especially powerful for handoffs:
"Customer states: front driver tire low last 2 weeks, low-speed squeak from rear, also wants to ask about wiper blade replacement. Mentioned trade-in possibility in 6 months — flag for sales follow-up."
That note is on the customer profile before you walk back inside. If the customer comes back tomorrow and you're off, the next advisor sees everything that was discussed in the drive. No "what did Mike say about the squeak?" mystery.
Push Notification Discipline
From the mobile app side — set notifications to your customers + @mentions ONLY. If you get pinged for every text the whole dealership receives, you'll start ignoring all of them within a week. Then you'll miss the @ mention that mattered.
Set it on day one. Audit it monthly. Three buckets to allow:
- Direct inbound from your customers
- @ mentions of you
- Replies in threads you're actively in
Mute everything else.
The Cross-Department Comms Standard
Same principle that applies to advisor-to-advisor handoffs applies to advisor-to-tech and advisor-to-parts. Every cross-team comm should land in the Numa thread (or its tech/parts equivalent), not in a verbal hallway conversation that disappears.
| Old way (avoid) | Numa way (do) |
|---|---|
| Walk to parts counter, ask Mark | @parts in the thread with VIN + question |
| Yell across the shop to the tech | Tech sees the RO note + Numa internal note |
| Sticky note on covering advisor's keyboard | @advisor tag in the Numa thread |
| "I think I told them 3pm" | It's in writing in the thread, timestamped |
If it matters for the customer, it goes in writing in Numa or the SDL notes. Verbal hallway comms always lose 30% of the detail and 100% of the visibility for the next advisor. Type it. Tag it. Move on.
The Advisor-Tech Loop (Numa + the Tech Side)
Techs don't always work in Numa directly, but the comms loop still has to close. The pattern:
- Tech finishes MPI → pings advisor via the shop comms tool
- Advisor copies the MPI link → texts via Numa to customer
- Customer replies in Numa → advisor sees in Smart Inbox
- Advisor updates the RO note / dispatches the additional work
- Tech sees the approved work and proceeds
Every handoff in that loop is written, visible, and recoverable if the original person isn't there. That's the standard.
The Handoff Checklist
What NOT to Do
Covering advisor gets blindsided. Customer notices.
They have 8 other things going on. Put it in the thread.
You will not remember the squeak when you're 6 ROs deep at 2 p.m. Dictate it then.
Within a week you'll silence the app. Then you'll miss what mattered.
Manager Coaching Tip
Once a week, sample 3 customers who had a shift-change or department handoff mid-RO. Read the Numa thread for each. Is there a clean @ tag at the handoff point? Did the covering advisor pick up the thread without the customer having to repeat anything? If yes, recognize publicly. If no, that's the coaching topic for the week. Handoffs are an invisible-discipline thing — if you don't audit them, they decay.