agentleFS
manypicommanypicom/sales-skills/skills/meeting-booking-cta/SKILL.md

meeting-booking-cta

Skill1 starsChanged 2 months agoMITView on GitHub

Write calls to action that convert interest into a booked meeting, and fix the handoff between a positive reply and a calendar invite. Use whenever the user mentions CTAs, calls to action, booking meetings, calendar links, demo requests, show rates, no-shows, or asks what to ask for at the end of a cold email. Also use when emails get positive replies that never turn into meetings.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Don't attach anything: No deck, no case study, no one-pager.

    line 58
  2. Distinctive:

    Not everyone wants a call, and insisting on one loses people who'd have converted another way.

    line 82

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

The Ask, and Getting to a Meeting

Two failures live here and they need different fixes. Emails that get no replies because the ask is too big, and positive replies that never become meetings because the handoff is slow or awkward.

The first is a copywriting problem. The second is an operations problem, and it's where more pipeline is lost.

Size the ask to the relationship

You are a stranger. The ask should be proportionate to that.

AskFrictionWhen
"Worth a look?"LowestFirst email, cold
"Is this something you own?"Very lowFirst email, unsure of the role
"Want the 3-line version?"Very lowFirst email
"Worth 10 minutes?"LowFirst or second email
"Here's my calendar"MediumAfter a positive reply
"Book a 30-minute demo"HighRarely appropriate cold
"Here's a link to a 14-step onboarding"Very highNever

"Is this something you own, or should I be talking to someone else?" is unusually effective as a first-email ask. It's easy to answer, it's genuinely useful to you either way, and it doesn't ask them to buy anything. The reply is either a conversation or a referral, and referrals are the highest-converting lead type there is.

One ask per email

Two questions get zero answers. "Are you the right person, and would you be free Thursday, and should I send the case study?" is three decisions for someone who owes you none.

Pick the single most useful thing they could tell you and ask only that.

Don't put a calendar link in a cold email

It asks a stranger to commit half an hour before they know what you do, and it makes the email look like a funnel rather than a message. It also adds a link, which costs deliverability. See spam-filter-triggers.

The calendar link belongs in the reply to a positive response, when they've already indicated interest.

The exception: warm inbound, an existing relationship, or an explicit "send me your calendar".

The handoff, where meetings are lost

Someone replies "sounds interesting, tell me more". What happens next decides whether it becomes a meeting.

Reply within an hour if possible, same day at worst. Interest decays fast and they emailed your competitors too.

Give both a link and specific times. Some people won't click a scheduler, and some won't propose times. Offer both.

Here's my calendar: [link]

Or if easier — Tuesday 2pm or Wednesday 10am, CET. Happy to work around you.

Anything specific you want me to have ready?

Three things make this work: both options, the timezone stated explicitly, and the closing question, which gets them thinking about their own situation before the call and gives the meeting a purpose.

Don't attach anything. No deck, no case study, no one-pager. It shifts the next step from a conversation to homework, and homework doesn't get done.

Make the meeting small

"30-minute demo" is a bigger commitment than most cold prospects will make, and it also frames the meeting as you presenting rather than as a conversation.

  • 15 minutes converts better than 30, and the meeting usually runs longer anyway once it's useful.
  • Call it a conversation, not a demo. "15 minutes to see if this is relevant" sets a lower bar than "a demo of our platform".
  • Give the meeting a stated purpose — the question you'll answer, not the product you'll show.
  • Make it obvious it's not a hard sell. "If it's not a fit I'll say so" is credible and it removes the main reason people decline.

Reducing no-shows

Booked meetings that don't happen are the quiet leak. Roughly a fifth to a third of cold-booked meetings no-show without intervention.

  • Send a confirmation immediately, with the purpose restated in one line.
  • Remind the day before, briefly. A reply-able email, not an automated calendar nag.
  • Ask a question in the confirmation. Any reply between booking and the meeting raises the show rate substantially, because it re-establishes that a person is on the other end.
  • Keep the gap short. A meeting booked ten days out no-shows far more than one booked in three days.
  • Make rescheduling easy and say so. People no-show partly because cancelling feels awkward. "If something comes up, just reply and we'll move it" converts a no-show into a reschedule.
  • Include the agenda and the joining link in the invite itself.

Alternatives to a meeting

Not everyone wants a call, and insisting on one loses people who'd have converted another way.

  • "Want me to send the 3-line version?" — a low-friction step that starts a thread.
  • "Should I send you the numbers instead?" — for people who prefer to evaluate alone.
  • Async video, brief and specific to them, for a warm-but-busy prospect.
  • "Reply with your setup and I'll tell you whether it's a fit" — a qualifying exchange that costs them one email.

Each of these keeps the conversation alive and creates a second, better-informed chance to ask for the meeting.

Diagnosing "positive replies, no meetings"

Work through in this order:

  1. How fast is the response? Over a day is usually the whole answer.
  2. Is a calendar link the only option offered?
  3. Is the meeting length too long?
  4. Does the reply pitch instead of booking? A positive reply answered with three paragraphs of product kills momentum.
  5. Is the purpose of the meeting clear?
  6. Is someone actually owning the replies? A shared inbox nobody owns is where this fails most often.
  7. Was the email over-promising? Meetings booked on a misleading premise cancel or no-show.

The first and last are the most common. Speed of response and honesty of the original email account for most of the gap.

Don't do these

  • Don't put a calendar link in a cold first email.
  • Don't ask for 30 minutes cold.
  • Don't send a deck before the meeting.
  • Don't ask two questions.
  • Don't use fake urgency. "I have two slots left this month" from a stranger is transparent.
  • Don't let a positive reply sit overnight.
  • Don't book meetings you know aren't qualified to hit a meetings number. It corrupts every downstream metric and wastes two people's time.

Related skills

cold-email-copywriting, reply-handling, email-sequence-design, outbound-metrics-benchmarks, subject-line-optimization

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.