agentleFS
prosyo-aiprosyo-ai/gtm-skill/skills/no-show-recovery/SKILL.md

no-show-recovery

Skill13 starsChanged 25 days agoMITView on GitHub

Use this skill when a prospect misses a booked meeting or keeps rescheduling: \"they didn't show up\", \"no-show follow-up email\", \"how to rebook a no-show\", \"reduce no-shows\". Writes the same-day no-show sequence (gracious message, rebooking options, value touch, close the loop), sets the timing across email, phone and LinkedIn, and diagnoses why no-shows happen so the booking process can be fixed.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this when a meeting is missed.

    line 16
  2. Distinctive:

    If no answer, send something useful tied to the meeting topic (the checklist, the short customer story), plus the link.

    line 33
  3. Distinctive:

    After two missed meetings, do not offer a third slot directly.

    line 41
  4. Distinctive:

    MUST keep the tone gracious, every time.

    line 59
  5. Distinctive:

    MUST stop after the close-the-loop message unless they reply.

    line 60
  6. Distinctive:

    NEVER charge, threaten or shame a no-show.

    line 61
  7. Distinctive:

    NEVER escalate to their manager because they missed a sales meeting.

    line 62

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Use this when a meeting is missed. Most no-shows are not rejections: calendars collide, days get away. A gracious, fast follow-up rebooks a large share of them.

Inputs

  • Meeting details: who, when, purpose, how it was booked.
  • The thread before the meeting.
  • How many times they have rescheduled already.

The play

1. Wait five to ten minutes, then reach out once

At five minutes past: a short email ("I'm on the line; no worries if today got away from you"). If the person's phone number is known and calling is appropriate, one call.

2. Same day: rebook without guilt

Hi Maya, no problem at all about today. I know how quarter-end weeks go. Would Thursday 10:00 or Friday 14:00 work instead? Or pick any time here: <link>

3. Day 2-3: add value

If no answer, send something useful tied to the meeting topic (the checklist, the short customer story), plus the link.

4. Day 6-7: close the loop

Hi Maya, I'll take this off my list for now. If month-end close gets back on the agenda, reply "close" and I'll send times.

Optionally, one LinkedIn message between steps 3 and 4 if connected.

5. Second no-show

After two missed meetings, do not offer a third slot directly. Ask whether the topic is still a priority; if yes, ask them to pick a time.

6. Diagnose patterns

PatternLikely causeFix
No-shows on meetings booked 2+ weeks outInterest fadesBook within 7 days; add a value touch in between
No-shows after links with no agendaUnclear valueAgenda in invite; confirmation with a prep question
High no-shows from one campaignWeak qualification or a pushy askFix the ask; qualify before booking
No-shows at certain timesTime zone errors, Monday mornings, Friday afternoonsConfirm zones; avoid those slots

What good looks like

  • First message within 15 minutes of the missed start time.
  • Rebook rate of 30-50% on first-time no-shows.
  • The common mistake is the passive-aggressive "Sorry we missed you, I waited 15 minutes", which makes rebooking awkward.

Rules

  • MUST keep the tone gracious, every time.
  • MUST stop after the close-the-loop message unless they reply.
  • NEVER charge, threaten or shame a no-show.
  • NEVER escalate to their manager because they missed a sales meeting.

Example prompts

  • "My 2pm with the VP of Ops didn't show. Write the follow-up sequence."
  • "This prospect has rescheduled twice. What now?"
  • "Our no-show rate is 35%. Diagnose and fix our booking process."

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.