Seven Days Later
Follow the bot's 'resolved' conversations for seven days and price what customers did next.
The job
Shows what customers actually did in the seven days after a bot said it resolved their conversation, priced in money. Teams fix the worst topic, claim credit where the contract allows, and choose bots on evidence rather than the vendor's own grading.
The moment
The bot vendor's slide says 81% of conversations were resolved.
Beside it, one real customer's week plays out: marked resolved by the bot at 14:02, calling the hotline at 16:40, then back on WhatsApp the next morning saying "this is the third time I've contacted you".
For that topic, only 49% of "resolved" conversations stayed resolved for seven days, and 38 one-star reviews this week name the bot.
The ledger shows $412,000 billed this quarter for resolutions that did not hold. The CFO asks for a refund claim before the meeting ends.
What it does
- Assign an owner and pre-register a target
- Draft a fix brief
- Open the fix task in Jira or the helpdesk
- Pin a bake-off comparison
- Stamp the Day Seven verdict
- Send a vendor credit claim or renewal argument
- Drill to evidence
What you see
Film reel with '3 hours later…' title cards, a Held bar per intent, a split-screen dashcam for bake-offs and a Day Seven PASS/FAIL stamp
What it moves
The share of bot-resolved conversations where the customer doesn't come back about the same issue within 7 days, compared with what the bot claims, and the money billed each quarter for resolutions that didn't hold.
Built for
- Frontline staff
- CX leaders & VoC
- Product & digital
- Finance
