Coach queueFirst release
Who needs coaching today, and why.
The manager home leads with what changed overnight and a short queue of reps to coach, each with the behavior and the evidence behind it.
AnswersWho should I coach today?
How it works
- 01
A pattern surfaces
“Jordan lost control during 4 of 6 price objections this week.” Confidence high, n = 6 objections across 4 calls.
- 02
Each rep comes with a reason
Jordan: objection handling. Alex: call control, monologues over 2 minutes in 5 calls. Mia: discovery depth.
- 03
Act from the card
View the pattern, or assign coaching with the moment already attached.
What you see
Read off the screen above. Every number is sample data from the app’s own prototypes.
- Overnight insight
- One sentence on what changed, with what reps who hold these calls do instead: pause about 1.8s and ask one question first.
- Confidence line
- Every insight states its confidence and sample size under the headline.
- Coach today
- A short list, not a dashboard. Each row has the rep, the behavior and the reason.
- Relationship with outcomes
- Open the pattern to see how the behavior travels with next steps and stage moves.
Who it’s for
Start the day knowing where an hour of coaching will matter most.
Reps do not see the queue. They see their own brief and their own focus.
Where it fits
Bylda is one loop. Coach queue is the patterns step.
- EventsWhat happened on the call
- BehaviorsHow the rep acted
- PatternsWhat repeats, for whom
- OutcomesWhat it travels with
- ChangeOne focus, then measured
What it won’t claim
- The queue suggests who to coach. The manager decides what gets assigned.
- Patterns say “associated with” unless the data supports cause.
Also in Coach
The whole product
What happened on the call, named as behavior.
Whether the behavior changed, with the confidence stated.
Where the system goes after V1. Not in the product yet.
