Blog

Why sending your booking link in DMs kills your calls

Dropping your Calendly link mid-conversation tanks your booked calls, because the link moves the work onto the prospect. What works instead: offer two times, get their details, and book it yourself.

A working closer once summed it up in one sentence: "people weren't booking calls when I sent links."

That's not a salesperson's hunch. It's what he saw after changing a single variable in the way he closed.

The scene is always the same. The conversation is going well, the prospect says yes to a call, and you send the link. They reply "great, I'll take a look," and then nothing.

Here's why that exact moment breaks the momentum, and what to do instead.

Because it turns an agreement into homework.

When the prospect says yes, they're with you, in the conversation, and they're warm. You send them a link. Now they have to leave the conversation, open a page, figure out the grid, pick a date, pick a time, type their name, type their email, sometimes answer three qualifying questions, then confirm.

Count the steps: there are seven or eight of them, each on a page they've never seen, to get through alone, without you.

Every step loses people. That's not specific to sales, it's true of any flow: the more actions between intent and result, the fewer results. The difference here is that you're losing people after they said yes, which is the worst possible place to lose them.

Then there's the word "later." A booking page rarely gets opened on the spot. The prospect tells themselves they'll check their schedule tonight. Tonight, the conversation feels far away, the urge has faded, and your link is buried under fifteen notifications. Those yeses that never turned into a call pile up for months, quietly, in threads you stopped looking at.

A link isn't a closing tool. It's a form, and a form doesn't close anything.

The answer is to take the effort on yourself, in three moves, one after the other.

Offer two specific times. Instead of "when are you free?", which hands the work back to the prospect and invites vagueness, give two firm options to choose from. A closed question gets answered in three seconds. An open one gets answered later, if at all.

Ask for their first name and email. Once they've picked a time, you need two pieces of information to set up the call. They give them in one line, inside the conversation, without leaving the screen.

Sometimes the person cuts in and asks for the price before any time is set. That's its own question, and we cover how to answer the price question in your DMs without dropping a bare number or dodging it.

Book it yourself. You open your calendar and create the event for them. They get the confirmation and the invite without doing anything more than answering two messages.

The prospect doesn't click a thing: they said yes in the conversation, and the call exists.

It's the complete reversal of the link. Instead of pushing six steps onto someone who owes you nothing, you take six and leave two to someone you actually want to talk to.

The objection comes right away, and it's fair: this takes your time. True, and it's worth putting a number on it honestly instead of brushing it off.

Booking a call by hand takes about thirty seconds. Across ten prospects who said yes in a week, that's five minutes. Compare that with what one lost call costs you because the page never got opened, and the question answers itself.

There's a side effect nobody mentions, and it matters as much as the booking rate. When you book it yourself, you know right away that the call exists. With a link, you know nothing: you wait for a notification that may never come, with no way to tell the person who forgot from the person who changed their mind. So you follow up blind, or not at all.

A second objection, less common but real: time zones and complicated schedules. Here, offering two firm times works less well, because you don't know the constraints on the other side. The method still holds, with a variation: ask first for two windows that suit them, then pick inside one and book it. The booking effort stays with you, which is the whole point.

Time first, or details first?

Both work, and the right order depends on who you're talking to.

The principle behind both is a staircase. Every small yes makes the next one feel natural. Agreeing to a time is a yes. Giving a first name is a yes. Giving an email is another. A string of small yeses lands more often than one big ask, and that's why you break it up.

What's left is choosing which step is easiest for this particular person.

Time first, by default. For someone decisive, saying "Tuesday at 2" costs nothing: it's concrete, it's short, it doesn't involve any personal data. Once the time is set, giving an email becomes a formality, almost rude to refuse.

Details first, for a hesitant lead. For someone who keeps hedging, a time slot feels like a commitment, and that's scary. An email doesn't: it feels like it has no consequence. And someone who just gave you their email commits to a time more easily afterwards, because they've already started saying yes.

You choose based on how the conversation feels, not at random. If the person asks precise questions and replies fast, go with the time. If they stall, if they reply in one line every six hours, go with the details.

The four-message sequence

Here's the full flow, from yes to confirmation. Adapt it to your own voice: the structure matters more than the words.

1. Offering times. Three versions depending on your tone:

Perfect. How about Monday at noon or Tuesday at 2pm, which works better for you?

Nice. I've got two openings this week: Thursday at 11 or Friday at 4. Which one do you want?

Love it. Tuesday at 2pm? If that's bad timing I also have Wednesday late afternoon.

Two options rather than three: a third one restarts the thinking, while two force a choice.

2. Asking for details.

Locking it in. Can you send me your first name and email so I can send the invite?

3. You book it. Nothing to write. You open your calendar and create the event.

4. The confirmation.

You're all set for Tuesday at 2pm, the invite is in your inbox. We'll take 30 minutes, you tell me where you're at and I'll tell you what I'd do. If something comes up, just let me know here and we'll move it, no problem.

The fourth message does more than inform. It says what's going to happen, which takes the edge off, and it gives a clean way out, which cuts no-shows: someone who knows they can reschedule lets you know instead of disappearing.

Honesty matters here, or nothing else in this piece is worth much: the booking link isn't the problem. Where you put it is.

The link is excellent anywhere the prospect comes to you on their own:

At the bottom of a sales page. The person has read, they're convinced, they're looking for the button. Asking them to send a message instead would be a step backwards.

In your bio, your email signature, your signup flow. It works while you sleep, with people you've never had a conversation with. No manual method replaces that.

With an existing client. Someone who already knows you and needs to go over something doesn't need hand-holding. The link saves them time, and you too.

The rule fits in one line: the link helps when the prospect is looking for you, and hurts when you're the one holding them.

In a private conversation, in the middle of a warm exchange, you're the one holding them, and that's exactly the moment not to let go.

One clarification is needed here, because there's a lot of loose talk on this topic.

A link on its own isn't a penalty trigger. No platform publishes a rule saying a booking link puts an account at risk, and what actually gets an Instagram account restricted comes down to a handful of behaviors, none of which is about links.

What is documented is repetition. Meta's spam policy describes repetitive content and high-volume, automated-looking sharing as the kind of behavior it acts on.

And a link pasted into a DM rarely travels alone. It usually comes inside a template message sent as-is to dozens of people. The link isn't the problem. The copy-paste around it is.

You'll notice the method above solves this without even trying. A time offered to one person, with their name and the context of your exchange, isn't identical to any other message. You can't repeat word for word a sentence that contains a time picked for one specific person.

That's not a security argument, just a consequence: writing to people one at a time looks like writing to people one at a time.

I won't give you any threshold number, because no platform publishes one, and every figure floating around online is made up.

FAQ

What is Ficiel?

Ficiel is an AI inbox for coaches and setters: it surfaces old Instagram, WhatsApp and LinkedIn conversations worth following up, drafts the message, and nothing is sent without your approval. The call then gets booked inside the conversation, right where the prospect said yes.

Should I stop using Calendly?

No. Keep it at the bottom of your pages, in your bio, in your signature, and for existing clients: anywhere the person comes to you on their own. Just don't send it in the middle of a private conversation, at the moment someone has just agreed to a call.

How do I suggest a time without sounding pushy?

Offer two specific options instead of an open question, and leave a way out. "Monday at noon or Tuesday at 2?" gets answered in three seconds and doesn't box anyone in, while "when are you free?" hands the work back to the prospect and usually ends with no answer.

What if the prospect goes quiet after saying yes?

It's the most common case, and you can work with it. A message that was opened and never answered is the best follow-up signal you have: what to do when a lead leaves you on seen covers exactly this situation.

Does this work on WhatsApp and LinkedIn too?

Yes. The mechanics don't depend on the app: a link asks the prospect to leave the conversation and finish alone, while offering two times keeps them where they already are. On LinkedIn, where people check messages less often, offering times that are a few days out works better than "tomorrow."