Post-booking outcome
Meeting no-show
A no-show is still an outcome. Cognlay logs it, changes the lead state, and chooses a recovery path instead of pretending the meeting never happened.
What triggers it
Meeting booked, calendar event passed, no attendance or no completed outcome logged.
What Cognlay sees
Intent existed, but commitment failed.
What happens next
Recovery touch drafted, urgency reduced, owner notified.
What we measure
Track rescheduled meeting, ignored recovery, future reactivation, or closed-lost state.
Send a generic reschedule email immediately.
A no-show can mean bad timing, low urgency, internal blocker, or weak qualification. Treating all no-shows the same burns context.
Change the state before writing the message.
Log the no-show, lower the urgency, draft a short recovery path, and track whether the lead re-engages or should be cooled down.
The message is the last step.
Bad outbound treats every signal as a reason to ask for a call. Cognlay treats the signal as a state change first, then decides whether to send, pause, route, suppress, or rewrite.
Template-brain version
You missed our call. Want to reschedule?
After state change
Looks like timing just slipped. No worries. Leaving the link here when it becomes useful again.
The lead is not treated as "hot" anymore. Urgency drops, recovery gets softer, and the outcome is logged.
Not one polite assistant voice.
Cognlay changes tone based on the state. Sometimes it explains. Sometimes it pauses. Sometimes it says nothing should go out.
Operator: Hold this.
Analytical: Pattern changed after touch 2.
Short: Timing's probably wrong.
Direct: This thread looks done.
Low-pressure: Ignore this if irrelevant.
What changes under the hood
Signal
Meeting booked, calendar event passed, no attendance or no completed outcome logged.
State
Intent existed, but commitment failed.
Risk
A no-show can mean bad timing, low urgency, internal blocker, or weak qualification. Treating all no-shows the same burns context.
Move
Log the no-show, lower the urgency, draft a short recovery path, and track whether the lead re-engages or should be cooled down.
Logged outcome
Track rescheduled meeting, ignored recovery, future reactivation, or closed-lost state.
What Cognlay checks
These signals decide whether the next move should be an email, a pause, a handoff, or no action at all.
What we watch for
Cognlay does not stop at sending. Every outcome gets logged, classified, and fed back into future decisions, so the next move is based on what actually happened.
Recommended if the meeting was high-value or owner-specific.
Reschedule rate
Recovery reply
Owner notes
Future reactivation
No-show recurrence