Use cases

Instagram comment-to-DM for coaches and consultants

A coaching or consulting post doesn't get hundreds of comments, and it doesn't need to. What matters is that the handful who do comment get a real reply, fast, with enough context that the call is worth booking before it even starts.

Last updated

What the flow looks like for you

Someone comments CALL under a specific offer post, gets a public reply, and a DM with a short one-page PDF holding the booking link and a couple of questions worth answering before the call, not a generic keyword firing across your whole account.

Keep this scoped tight: one post, one offer, one keyword. Someone comments, the reply lands under it, and the DM carries a link to a one-page PDF you wrote, the booking link plus two or three questions worth answering before you talk. From there it's a normal conversation: they can reply in the DM thread the way anyone replies to any Instagram message, and you're reading it the same as you would any other DM.

The automation's job ends at that first message. It gets the link and the questions in front of someone the moment they ask, reliably, at 2am if that's when they commented. What happens after is a conversation between two people, which is exactly right for a discovery call.

Keywords that work for this audience

Short, direct words like CALL, CONSULT, or BOOK match reliably; comments that ask without using any of them, "how do I work with you," "interested, what's next", can still be caught by smart matching, which runs only when no keyword matched and stays silent below its confidence threshold.

A keyword match is instant and exact: someone has to type the word. That works for a caption that says "comment CALL to grab a spot," but a consulting post often draws comments that ask the same thing in different words, "what's the process," "can we chat," with no keyword anywhere in them. Smart matching exists for exactly that gap: it only runs after every keyword check comes back empty, and it only fires above a fixed 0.8 confidence threshold, so a comment that's genuinely ambiguous gets left alone rather than guessed at.

Because volume here is naturally low, a false match matters more than it would on a high-traffic post; a stray DM to someone who wasn't actually asking about a call reads as a mistake, not an inconvenience. The fail-closed threshold is the reason that risk stays small rather than the reason to avoid smart matching altogether.

What to offer

A campaign needs one attached file to launch, so the practical offer is a one-page PDF carrying the booking link and the intake questions, rather than an external calendar link typed loose into the DM with nothing backing it up.

The tracked link in the DM always points to whatever file the campaign has attached, not to an arbitrary outside URL, so the booking link itself has to live somewhere: inside that one-page PDF is the cleanest place for it. Keep it to a single page. A name, one line on what the call covers, the booking link, and two or three intake questions ("what are you hoping to get out of this," "what's your timeline") is plenty; anything longer competes with the thing that actually matters, the link.

Those intake questions aren't a form ReplyMagnet captures answers into. They're written prompts on the page, and the honest answer arrives however the person chooses to send it: back in the DM thread, or on the call itself. That's a lighter mechanic than it might sound, and it's the right one, since a real intake conversation belongs with a real person reading it.

Setting it up

Scope the campaign to the specific post announcing the offer rather than the whole account, set one keyword, decide whether the phone gate is worth adding, attach the one-page PDF, and comment your own keyword before publishing the post.

Scope this to the one post making the offer. An account-wide campaign means every comment on every future post carries the same booking prompt, which turns a targeted offer into something closer to a standing pitch, not the read you want on a post about something else entirely.

The phone gate is worth a real look here, and it's a Pro-and-above feature: turning it on asks for a phone number before the PDF releases, which for a call-booking flow gives you a direct way to follow up if the booking itself never happens. Email works the same way on every plan if a number feels like too much to ask before a first conversation. Either way, test the whole thing with a second account before the offer post goes live; a broken PDF link on a post asking people to book time with you is a worse first impression than a comment going unanswered.

What to measure

At low volume the raw comment count matters less than what happens after it, so watch the reply-to-delivery rate and, if the phone gate is on, how many of those comments actually left a number worth calling.

Ten comments a week isn't a small number here, it's the point. What's worth tracking is how many of those ten actually got a reply and a delivered DM (that should be close to all of them, since this isn't a volume problem) and, downstream of the gate you chose, how many left contact info worth following up on. A phone number left on the intake page is a stronger signal of real intent than an email address, since it's a harder thing to hand over casually.

Starter's 30-day lead window is rarely a real limit here; a coach running one or two offers a month isn't losing anything by not seeing comments from three months back. If the list is worth keeping and following up on manually, Basic's CSV export is enough. Pro's live sync into Mailchimp or Kit earns its cost once there's a real follow-up sequence behind it, not before.

Where it goes wrong

The two real mistakes: gating behind both email and phone on a post that already gets few comments, and leaving the campaign scoped to the whole account so a booking prompt fires on posts that were never about booking anything.

Stacking both gates, email and phone, on a campaign that's already low-volume by nature tends to cost more than it gains. Every extra field is a chance for someone to close the tab instead of finishing it, and on a post that might draw fifteen comments total, losing three of them to a second field is a bigger share than it would be on a post drawing a thousand.

The other real mistake is scope, not gating. An account-wide campaign means a comment on an unrelated post, a photo, a client testimonial, whatever, still gets the booking DM, which reads as tone-deaf to someone who wasn't asking about your services at all. Keep the offer campaign tied to the specific post that made the offer.

Common questions

Do I need to gate for a phone number, or is email enough?

Either works; phone capture is a Pro-and-above feature. A phone number gives a more direct way to follow up if someone doesn't book after all, but it's also a bigger ask on a post that already gets few comments, so weigh that against the follow-up value before turning it on.

Can ReplyMagnet actually book the call for me?

No. It delivers the link and the questions the moment someone comments; the booking itself happens on whatever scheduling tool the link points to, and anything past that first message is a normal conversation you're having yourself.

What if someone comments who clearly isn't a real prospect?

Nothing stops the automation from replying, since it can't judge intent from a keyword alone. That's a reasonable trade for a low-volume post: reviewing a handful of replies by hand afterward costs a lot less than adding friction that also turns away real prospects.

Should this campaign cover my whole account or just one post?

Just the one post making the offer, in almost every case. An account-wide scope means the same booking DM fires on comments left under posts that were never about booking a call, which reads as off-topic to the person who left them.

Keep reading