Leave with a three-message outline with a purpose and stopping rules.
Start with a real buying situation
For the worked example, the audience is the owner of a 60-person business. Their problem is that support requests arrive through personal messages and urgent issues lack a clear owner. The desired practical outcome is a documented escalation path and visible ticket ownership.
The example is deliberately bounded: business-critical systems cannot be changed during working hours. That condition should influence the promise, scope and next step rather than disappear from the marketing copy.
| Illustrative offer | a support and device-management service |
|---|---|
| Buyer question | Which incident last interrupted work, and how was responsibility assigned? |
| Possible evidence | an example ticket lifecycle with triage, handover and closure evidence |
| Useful asset | an incident escalation checklist |
How to complete your lead nurture sequence
- Define why the person asked to hear from you.
- Identify the next decision or uncertainty.
- Choose useful evidence for each message.
- Use a clear, proportionate next action.
- Stop or change the sequence when the person responds, declines or asks to unsubscribe.
Worked example
These entries are illustrative planning material, not research findings or customer results. Keep the structure and replace the content with verified details.
| Reason for the relationship | The person requested information about a support and device-management service. Record the actual source and their communication preferences. |
|---|---|
| First unresolved question | Message 1: clarify their question. “Which incident last interrupted work, and how was responsibility assigned?” Include an incident escalation checklist if it helps. |
| Evidence to share next | Message 2: explain an example ticket lifecycle with triage, handover and closure evidence. Connect it to a documented escalation path and visible ticket ownership, with limitations. |
| Decision invitation | Message 3: ask whether it would be useful to review a limited device group and agree escalation responsibilities. Offer a clear way to pause or decline. |
| Stop and handover rules | Stop automated follow-up when the recipient responds, declines or opts out. Route substantive replies to a named owner. |
Review before using it
A useful operational measure in this example is ticket age by priority, with priority definitions agreed first. That does not automatically make it a marketing attribution metric. Define the source, period and owner before drawing conclusions.
- Would each message still be useful if the recipient did not buy immediately?
- Check the delivery assumptions: Define supported devices, service hours, exclusions and escalation contacts.
- Use evidence rather than promises. Response time is not resolution time; do not imply they are interchangeable.
- Discuss the draft with someone who understands the buying situation. Start with: “Which incident last interrupted work, and how was responsibility assigned?”
- If the next step is a trial, define its purpose. One possible starting point is to review a limited device group and agree escalation responsibilities.
Common mistakes and a better review
Do not fill a missing fact with an impressive-sounding number. Mark it as an assumption, explain how you will check it and give that check an owner. A short, honest document is easier to use than an elaborate plan built on unknowns.
| Watch for | A sequence that ignores replies behaves like a broadcast rather than a conversation. |
|---|---|
| A real buyer concern | Our existing IT person already handles everything. |
| Useful response direction | We can map the workload with them and identify gaps in cover; the conversation need not start with replacing anyone. |
| Evidence to collect | The buyer’s own account, an example ticket lifecycle with triage, handover and closure evidence, and records relevant to ticket age by priority, with priority definitions agreed first. |
Your working sheet
Write your own version below. Notes are saved on this browser when local storage is available. Use Download to keep a separate copy; avoid adding confidential information on a shared device.
Example: The person requested information about a support and device-management service. Record the actual source and their communication preferences.
Example: Message 1: clarify their question. “Which incident last interrupted work, and how was responsibility assigned?” Include an incident escalation checklist if it helps.
Example: Message 2: explain an example ticket lifecycle with triage, handover and closure evidence. Connect it to a documented escalation path and visible ticket ownership, with limitations.
Example: Message 3: ask whether it would be useful to review a limited device group and agree escalation responsibilities. Offer a clear way to pause or decline.
Example: Stop automated follow-up when the recipient responds, declines or opts out. Route substantive replies to a named owner.
Review your work
Tick only what you can support with your answer or practice. This is a reflection checklist, not an automated assessment.
Questions about this resource
How do I adapt this for my managed it services business?
Replace the audience, offer and evidence with your actual information. Begin with a recent buyer conversation about why support requests arrive through personal messages and urgent issues lack a clear owner, then check which assumptions match your business.
Is the filled example ready to publish?
No. It is a working example. Verify claims, permissions, prices, current capabilities and any customer information before using it externally. Response time is not resolution time; do not imply they are interchangeable.
What should I do after completing the worksheet?
Use it to make one decision or have one focused conversation. The intended output is a three-message outline with a purpose and stopping rules. Set a review date and update it when the evidence changes.
Illustrative business worksheet. No customer results, market rates, traffic volumes or performance benchmarks are implied. About these resources.