Chapter 3
Start conversations that earn a reply
reply-earning conversation scripts is the practical output of this chapter. Complete it in one focused work session so you can decide which context, observation, and low-friction question to use for warm, community, referral, and cold routes, without sending a miniature sales page that gives the recipient no reason to respond.
What you’ll get
- A completed reply-earning conversation scripts ready for the next chapter.
- A documented decision about which context, observation, and low-friction question to use for warm, community, referral, and cold routes.
- A pass or fail signal: messages earn useful replies that reveal fit, timing, or a clear no.
- A first implementation move: Write the first line from real context, name the relevant problem, and ask one answerable question before presenting the product.
Lead with context, not a miniature sales page
A useful first message has four parts:
- Context: why you are contacting this person.
- Observation: the problem or moment you noticed.
- Small question: something answerable without a call.
- No-pressure boundary: permission to ignore or decline.
Warm-contact script
Community reply
Referral request
Never disguise a sales pitch as “research.” If your product is ready and you may offer it, say so.
Apply this chapter to your store
Start with the live customer path, not a hypothetical version. Open the relevant content, profile, Tapmy page, email, or operational record and capture what a buyer sees now. Keep the scope to one campaign and one decision so the result can be measured.
Implementation move: Write the first line from real context, name the relevant problem, and ask one answerable question before presenting the product.
Connect the decision to evidence: customer language, transition counts, questions, observed behavior, or a completed end-to-end test. If another person cannot understand why you chose the action, add the missing evidence rather than more strategy language.
Decision checkpoint
| Check | Pass condition | If it fails |
|---|---|---|
| Scope | One buyer, one campaign, and one next action are named | Narrow the work before creating more assets |
| Evidence | The current state is visible in a live route or record | Capture the source, destination, and decision point |
| Decision | which context, observation, and low-friction question to use for warm, community, referral, and cold routes is written clearly | Remove competing goals and choose one priority |
| Verification | messages earn useful replies that reveal fit, timing, or a clear no | Rework the weakest boundary, then retest it |
Common failure mode
Leading with features, price, and a checkout link before understanding the person. It creates activity without reliable learning. Use the chapter deliverable as a gate: the work is complete only when the decision is written, applied to the live path, and verified with the stated signal.
20-minute implementation sprint
- Open the live route or record and capture the starting state.
- Complete the smallest useful version of the reply-earning conversation scripts.
- Apply the decision to one campaign or Tapmy path.
- Test the pass signal from the buyer’s point of view.
- Save the evidence and the next review date.
