Timing objection
Not-now reply
A not-now reply is not a dead lead. Cognlay records timing, suppresses the wrong follow-up, and schedules the next reasonable touch.
What triggers it
Lead replies with timing language: later, next quarter, not now, circle back, after launch.
What Cognlay sees
Relevant, but timing blocked.
What happens next
Snooze lead with reason and return window.
What we measure
Track reactivation, no response, unsubscribe, or changed intent later.
Push for a call anyway or send another generic follow-up next week.
The prospect gave a state update. Ignoring it teaches them the system is blind and increases unsubscribe risk.
Change the state before writing the message.
Classify the timing window, stop the current sequence, create a snoozed follow-up path, and preserve the reason for the future touch.
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
No worries. Should I follow up next quarter?
After state change
Totally get it. I'll leave this where it is. If timing changes later, I'll pick it back up with the same context instead of restarting the thread from scratch.
The system saves timing and suppresses the current path instead of making the prospect manage your reminder.
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
Lead replies with timing language: later, next quarter, not now, circle back, after launch.
State
Relevant, but timing blocked.
Risk
The prospect gave a state update. Ignoring it teaches them the system is blind and increases unsubscribe risk.
Move
Classify the timing window, stop the current sequence, create a snoozed follow-up path, and preserve the reason for the future touch.
Logged outcome
Track reactivation, no response, unsubscribe, or changed intent later.
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.
Usually not needed unless the reply includes a named stakeholder or active buying signal.
Snooze accuracy
Future reply quality
Reactivation rate
Unsubscribe prevention
Context carryover