Sales coaching advice converges on a comfortable rhythm: meet weekly, review recent calls, set goals, repeat. Most enablement playbooks recommend it. Most managers follow it. And if you ask reps what they want, many will say they prefer a predictable cadence over getting pulled into ad hoc sessions.
There's a real question buried under that consensus: is the weekly cadence actually producing behavior change, or is it just producing a meeting that both sides have learned to tolerate?
When we looked at call data across a range of teams using Tunlai, a pattern kept showing up. Coaching that was timed to a specific recent call — ideally within 48 hours — produced noticeably stronger behavior change on the next observed call versus coaching delivered in a standard weekly 1:1 that reviewed something from three or four days ago. The difference wasn't marginal. The reps who received event-triggered coaching showed roughly 2.4x the improvement rate on the targeted behavior compared to reps coached on a fixed weekly schedule reviewing the same underlying material.
That number matters, but the mechanism behind it matters more. Understanding why event-triggered coaching works better is what lets you actually redesign your cadence rather than just shortening the interval.
The Memory Window Problem
When a rep finishes a call, their subjective memory of what happened — the specific moment they went defensive on price, the question they skipped, the way the prospect's tone shifted — is rich and accessible for about 24 to 48 hours. After that, the specific texture starts to fade. By the time a weekly 1:1 rolls around, the rep is often reconstructing the call from general impression rather than recalling concrete moments.
This is a well-documented feature of episodic memory, not a flaw in your reps. The problem is that coaching works best when the rep can map the feedback directly to the felt experience. "You went defensive when she mentioned Gong" lands differently when the rep still feels the pull of that moment versus when it's reduced to a vague recollection that they probably said something about features.
Coaching within the memory window also reduces defensiveness. A rep who has fully processed a call and moved on to the next three is more likely to feel that old feedback is an indictment of their general competence rather than a specific, correctable moment in a specific conversation.
What "Weekly Coaching" Actually Means in Practice
Weekly coaching isn't one thing. It's a scheduling container that gets filled very differently depending on the manager and the week.
In our experience watching teams use Tunlai, the weekly 1:1 format tends toward three failure modes. The first is retrospective sprawl — the session covers too much ground because there are three or four calls to review, nothing gets the depth it needs, and the rep walks away with three behavioral reminders rather than one clear practice target. The second is agenda drift — if there are pipeline reviews or forecast updates stacked into the same meeting, coaching gets compressed or dropped entirely when time runs short. The third is selective sampling — managers tend to pull up calls that were flagged or that they heard about informally, which creates survivorship bias in what gets coached.
The managers who get the most out of a weekly format are the ones who use the calendar slot as accountability infrastructure but do the actual coaching work much earlier, closer to when the call happened. They've essentially created event-triggered coaching with a weekly check-in layered on top.
Designing a Cadence Around Events, Not Clocks
The practical shift here isn't about meeting frequency — it's about what triggers a coaching conversation. Instead of scheduling backward from a calendar ("we meet Tuesdays at 2pm, so I'll pull calls from this week"), the cadence runs forward from conversations ("a call happened, scoring flagged a pattern, I'm going to send feedback within the day").
This is where automated call scoring changes the economics. Manually listening to every call to identify coaching moments is a real bandwidth constraint — for a manager running a team of six to eight reps, each doing four to six calls a week, listening to even a third of that volume is a 10+ hour commitment on top of everything else. The weekly batch review evolved partly because it was the only way to fit call coaching into a manager's actual schedule.
When a scoring system surfaces the calls worth coaching — flagging specific moments, giving the manager a three-minute review of what to listen for before they play the relevant clip — the event-triggered model becomes feasible. The manager doesn't need to find the coaching moment. They need to respond to it, and that response can be a 10-minute async voice note or a brief text before the rep's next call.
We're not saying weekly 1:1s should disappear. They're the right forum for longer arc conversations — rep development trajectory, skill gaps that span multiple calls, career direction. The mistake is using them as the primary vehicle for tactical call coaching when they're too far from the events to drive tight behavior loops.
One Rep's Pattern: The "Price Pause" Hesitation
One team using Tunlai had an AE who consistently hesitated before quoting price — a 3 to 4 second pause followed by a slight upward inflection on the number, which the scoring rubric flagged as a confidence signal. The rep had been coached on price confidence before in quarterly reviews but had no specific memory of the behavior in context.
When the manager shifted to same-day feedback — a short audio note referencing the timestamp, playing back the specific clip — the rep recognized the pattern immediately because they still felt the hesitation. By the third call after that conversation, the behavior had measurably changed: the pause compressed, the inflection flattened. The rep described it as "finally being able to catch myself in the moment because I knew exactly what I was looking for."
That's what the memory window gives you. Not just a faster feedback loop — a more actionable one, because the rep can still connect the feedback to the felt experience of the call.
The Bandwidth Constraint Is Real — Don't Ignore It
An honest design note: event-triggered coaching requires more from managers in some ways. The weekly batch is administratively tidy. Event-triggered coaching means making a judgment call about which flagged calls actually warrant immediate feedback versus which ones can wait for the 1:1. It also means that coaching moments arrive asynchronously — a call from Tuesday at 3pm gets flagged while you're in a pipeline review Wednesday morning, and you need a system for handling that queue.
The managers who struggle with this model are usually the ones trying to make it synchronous — sending the feedback and then waiting to discuss it live. Async delivery — a voice note, a comment in the call review interface, a tagged timestamp with a two-sentence note — keeps the feedback reaching the rep within the memory window without requiring both parties to be free at the same time.
Teams using async-first coaching delivery tend to see broader coverage across the rep roster, not just the squeaky-wheel calls. The reps who never get formal coaching because they're not visibly struggling are often the ones where early-signal coaching would have the most compounding effect on quota attainment.
Rebuilding the Cadence
The cadence we've seen work well for growing sales teams in the 6-to-15 rep range combines two layers. The first is event-triggered micro-coaching — async, within 48 hours, focused on one specific behavior from one specific call. The second is a weekly or bi-weekly 1:1 that covers development arc, rep confidence, pipeline health, and anything the async coaching surfaced that needs a fuller conversation.
Frequency isn't the right variable to optimize. Proximity to the event and specificity of the feedback are. A manager who coaches once a week but does it three days after the relevant call will see less behavior change than one who coaches three times a week in response to specific moments the day after they happen.
The question "how often should I coach?" has a cleaner answer when you reframe it: coach as soon as there's something specific and actionable to say, while the rep still remembers what it felt like to be in that call.