Deals going quiet
Stalled deals and missed SLAs surface on their own. Not a report you remember to run on Friday — a queue that is already waiting when you open it.
04 · Product pillar
Coach Queue
Know who needs you today.
A manager's day is a guessing game: which deal is quietly dying, which rep is quietly stuck, which win nobody noticed. Coach Queue stops guessing. It watches the book and hands you a ranked queue of the people and deals that need you — and it shows your reps exactly what it showed you.
Three things, every day.
Reps who are stuck
At-risk patterns, before they become a quarter. The signal that fired, the rep it fired on, and what specifically changed — so the conversation starts at the problem instead of at "how's it going?"
Wins nobody saw
Recognition moments are in the queue too, ranked alongside the interventions. A good manager already knows the save that deserved a callout. This one just does not let it slide past on a busy day.
The signals
What reaches you, and why.
Four kinds of signal earn a place in the queue. Every row carries the one that put it there, so a queue item is never a mystery you have to go and reconstruct.
Stalled deal Missed SLA Rep signal Recognition
01 Ocklawaha Family Medicine Proposal opened, then silence — next touch proposed. Stalled deal
02 St. Marys Billing Group Next step never scheduled after the last call. Stalled deal
03 Suwannee Orthopedics Follow-up past its window — flagged before the quarter feels it. Missed SLA
04 Territory check-in A rep's pipeline went quiet this week — worth a conversation. Rep signal
05 Alafia Medical Staffing A save worth saying out loud — deal pulled back from stalled. Recognition
every row shows the signal that put it there · your reps see this page too
A manager's queue: three deals going quiet, one rep stuck, one win worth saying out loud. Every row shows the signal that put it there.
Consent-first, by design.
It watches the book
Most tools that watch a sales team watch the rep. Coach Queue watches the book — the deals, the accounts, the signals, the SLAs — and surfaces the person only when the work says someone needs help. That is a real architectural difference, not a policy promise, and it is why the queue can be transparent without being a threat.
Your reps see what you see
So it is transparent. Every rep can see everything their manager sees about them, on a page built for exactly that purpose. There is an opt-out. Nothing about a rep is computed in a room they cannot enter.
This is what we mean by consent governance, and we would rather say it plainly on a product page than bury it in a trust center: a coaching tool that a rep is afraid of is not a coaching tool. It is surveillance with a nicer name, and it will not survive contact with the people it is aimed at.
Every number means something.
There is a game layer: XP, quests, streaks, a leaderboard, team competitions. It is off by default. A rep who wants it turns it on; a rep who does not, never sees it, and loses nothing.
It runs on one rule. Every visible number maps to real earned value. No vanity multipliers. No points for logging in. If a number went up, something real happened in the book — and you can click it and find out what.
That rule is why we call it honest gamification. Most motivation tools are a scoreboard bolted onto a CRM: a second system, with a second set of numbers, drifting out of sync with the first. This one reads the same rows your pipeline reads. There is nothing to sync, because there is nothing separate to sync with.
Coaching that lands
You can hand a rep the work, not a note.
Quests come from four places: the main line, side work, the daily reset — and from you. A coach-issued quest is how a coaching conversation becomes something the rep actually sees in their queue the next morning, tied to the accounts it was about.
Coach-issued to one rep
Work the accounts that went quiet this week — the queue already knows which ones and why.
Issued from a conversation, not a spreadsheet. It lands in their Run tomorrow morning instead of evaporating in a note.
issued by you · visible to the rep · closes on what actually happened
It closes when the pipeline moves, not when someone marks it done. That is the same honest-data rule the rest of the layer runs on — a quest cannot be completed by saying it was.
Where it sits
See it on your own book.
Welaka is pre-GA. There is no self-serve signup yet — access is demo-led. If you manage reps, the fastest way to judge Coach Queue is to watch it rank a week of your own pipeline.