lead replied 'not right now, try Q3' and the agent logged it as a positive reply and stopped all follow-up
Fixes an SDR agent's reply classification so timing objections like 'not right now, try Q3' route to a nurture or timed re-engagement path instead of being logged as positive or dead. Use when deferral replies are misclassified and follow-up stops entirely. Not for opt-outs, out-of-office replies, or genuine positive replies.
TL;DR
"Not right now" is a timing objection, not a yes and not a no. Add a deferral intent to the classifier, route it to a timed re-engagement (Q3 means Q3, with a reminder set), and stop treating every non-negative reply as a win that ends the sequence.
lead replied 'not right now, try Q3' and the agent logged it as a positive reply and stopped all follow-upSteps
- Find the misclassified reply and confirm the label it got. "Positive" usually came from a sentiment check that saw polite words and no refusal.
Expected: the exact reply-to-label mismatch is documented.
- Add a "deferral / timing" intent to the reply classifier with trigger phrases: not right now, try me in [period], circle back in Q[1-4], reach out next [month/quarter], budget next year, bad timing.
Expected: deferral replies get their own label instead of falling into positive.
- Parse the time reference when present. "Try Q3" becomes a re-engagement date at the start of Q3; "next quarter" becomes 90 days out; vague timing ("sometime later") becomes a default 60-day nurture check.
Expected: each deferral produces a concrete future date, not a dead end.
- Route deferrals to a nurture path: stop the active sales sequence, enroll in a light-touch nurture (quarterly check-in), and set a task for the re-engagement date. Do not mark the lead as won, lost, or unsubscribed.
Expected: the lead stays warm with zero manual tracking.
- Fix the reporting: deferrals should count as "timed out / nurture", never as positive replies. Re-run the last 30 days of "positive" labels through the new classifier and correct the pipeline numbers.
Expected: conversion metrics stop being inflated by polite brush-offs.
Use this when
- Deferral replies ("not now", "try next quarter") are mislabeled
- Follow-up stops completely after a timing objection
- Positive-reply metrics look suspiciously high
Not for this skill when
- The reply is a hard no (that is a closed-lost path, not deferral)
- The reply is an opt-out (suppression path, never nurture)
- The reply is an out-of-office (auto-reply handling)
- There is no time reference and no interest signal at all (treat as a soft no, not a deferral)
Variant phrasings
- "'not right now' logged as positive, follow-up stopped"
- "agent treated a timing objection as a won reply"
- "deferral reply killed the sequence instead of scheduling re-engagement"
Why it happens
Most classifiers collapse replies into positive / negative / neutral. A polite deferral has positive sentiment words ("thanks, sounds interesting") with a negative timing clause, so sentiment wins and the label lands on positive. Positive historically means "AE takes over, sequence stops", so the lead falls into a gap where nobody follows up and nobody nurtures.
Edge cases
- "Not right now" with a named blocker ("no budget until renewal in June") is higher value than a bare deferral. Capture the blocker text for the re-engagement note.
- A second deferral from the same lead ("still not a priority") should age into a long-term nurture, not another 90-day loop. Cap active re-engagement attempts.
- Quarter references are ambiguous across fiscal vs calendar years. When in doubt, ask in the reply or default to calendar quarters and note the assumption.
- Some deferrals are polite permanent nos. If the lead has deferred twice with no engagement in between, treat the third touch as a breakup email, not another deferral.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_67EpUGKNAJPj84tT0Wet9w
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.