At the shop
A customer was told to expect a progress call by 5 p.m. The morning advisor left a note about a possible Friday pickup; the painter has since moved the job back a stage. The evening advisor takes over at 4:55.
Set up the demo
Use the sample records below when entering this fictional repair.
Records to enter in the demo
| Reference | Owner or event | Record entry |
|---|---|---|
| MSG-943A | Advisor to customer · 11:05 | “We’ll call by five with a progress update.” |
| NOTE-943 | Morning advisor · internal | Friday pickup possible if paint passes inspection. |
| STAGE-943 | Painter · 16:42 | Back to prep. Manager reviewing timing. |
| MSG-943B | Evening advisor · 16:57 | “The car is back in prep. I’ll call by 10 tomorrow with the revised timing.” |
Which commitment should the next advisor see?
The 5 p.m. update was made at 16:57. The new commitment is a call by 10 a.m. tomorrow. Friday pickup was an internal possibility. The next advisor should see the customer message, its author and the callback deadline.
Run the handoff
- Find the last customer-facing promise and the current production status. Ask the advisor to explain which information is internal before replying.
- Record a revised callback time and hand the job to a third teammate. Confirm the customer saw only the intended update.
Where AutoHound fits
AutoHound describes a shared texting inbox tied to the repair order, internal messages and individual staff access. This is a useful demo for a shop with rotating front-desk coverage. Read the AutoHound field guide.
What to record
A shared inbox is useful only if staff can distinguish what the customer actually received from what the team discussed internally. Write down the role, screen and document that prove the result.
AutoHound feature reference