Chapter 5
Follow up without chasing
two-touch follow-up sequence is the practical output of this chapter. Complete it in one focused work session so you can decide the useful reason and timing for each follow-up, without damaging trust with repetitive ‘just checking in’ messages.
What you’ll get
- A completed two-touch follow-up sequence you can use in the next chapter.
- A documented decision about the useful reason and timing for each follow-up.
- A pass or fail signal: every follow-up adds information, proof, a resource, or a decision deadline rather than repeating the first message.
- A concrete first action: Schedule two follow-ups now and attach a distinct reason to each one.
Use a reason, not “just checking in”
Follow up when you can add context:
- Answer a question they raised.
- Share a preview relevant to their use case.
- Correct a misunderstanding.
- State a real deadline or availability constraint.
- Close the loop politely.
Example:
Limit outreach to a small, respectful sequence. Record a clear no and stop contacting the person about that offer.
Apply this chapter to your store
Start with the evidence you already have: the current Tapmy setup, the exact customer path, the messages people see, and the records created after an action. Do not redesign the entire system while you are still trying to locate the constraint.
Implementation move: Schedule two follow-ups now and attach a distinct reason to each one.
Write the decision beside the evidence that supports it. If a teammate cannot reproduce the conclusion from the same evidence, the work is not yet operational. The deliverable should be specific enough to hand to another person without a meeting.
Decision checkpoint
| Check | Pass condition | If it fails |
|---|---|---|
| Evidence | The current state is visible and reproducible | Capture the real route, screen, record, or message before changing it |
| Decision | the useful reason and timing for each follow-up is written in one sentence | Reduce the scope until one owner can choose |
| Execution | Schedule two follow-ups now and attach a distinct reason to each one. | Assign a time and owner, then complete the smallest end-to-end version |
| Verification | every follow-up adds information, proof, a resource, or a decision deadline rather than repeating the first message | Return to the failed boundary and retest only after the cause is changed |
Common failure mode
Following up because the CRM says so, without giving the recipient anything new. This hides the actual constraint and creates false confidence. Use the chapter output as a gate: do not move forward until the decision is explicit and the pass signal is visible.
20-minute implementation sprint
- Open the current Tapmy path and capture the starting state.
- Complete the smallest version of the two-touch follow-up sequence.
- Record the decision, owner, and next review date.
- Test the pass signal once from the customer’s point of view.
- Save the evidence where the person running the next chapter can find it.
