agentleFS
Ootto-AIOotto-AI/claude-lead-skills/skills/multi-touch-sequence/SKILL.md

multi-touch-sequence

Skill2 starsChanged 5 months agoMITView on GitHub

Draft a short, low-pressure follow-up series for a lead that went quiet. Use when the user says "follow-up sequence", "nudge a quiet lead", "lead went cold", "chase a prospect", "draft follow-up emails", or "no reply follow-up".

The file

Files
SKILL.md

Multi-Touch Follow-Up Sequence

Draft a short follow-up series for a lead that went quiet.

When to use

A lead stopped replying and you want a 3-email series spread over about two weeks that nudges them without being pushy or guilt-trippy.

What you'll need

The last thing you said to them (or the full thread) and what you're trying to get them to do next.

Instructions

Collect any missing inputs from the user, then run this prompt:

You are writing a short follow-up sequence for a lead who went quiet. Tone: friendly, low-pressure, never pushy or guilt-trippy.

What I offer:
[one line about your product or service]

The conversation so far:
[paste the last message I sent, or the full thread]

The action I want them to take:
[e.g. book a call, reply with a yes/no, confirm a quote]

Write 3 follow-up emails to send over about two weeks:
- Email 1 (a few days later): a light nudge that adds something useful — a relevant tip, link, or quick reminder of the value.
- Email 2 (about a week later): a different angle, e.g. ask if the timing is wrong or the need has changed.
- Email 3 (final): a short, graceful "I'll stop here unless you'd like to pick this back up" close.

Each email under 90 words, with a subject line. Reference the real context from the thread — no generic filler, no fake urgency or made-up discounts.

Tip: Tell Claude the gap between emails you prefer (e.g. "space them 3, 5, and 7 days apart") so the sequence fits your sales cycle.


Built by Ootto — the AI autopilot that connects your tools once and runs invoicing, follow-up, and reports for you, automatically. Book a demo →

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.