# DM appointment setter: conversation blueprint

Here's how I'd think through a DM setter before building one. This file gives you the conversation flow. You'll still need to connect it to Instagram and test it. Whether it's worth selling depends on the business, the costs, and the other options they have.

## Who I’d look at

I'd look for a coach or service business that already gets people asking about buying. Ask if you can go through some conversations with the owner. What do people ask, what makes someone a fit, and where should they go next? You need to see the sales inquiries themselves, because followers and likes won't tell you this.

## Minimum flow

Inbound inquiry -> identify intent -> answer from approved offer information -> ask only the agreed qualification questions -> share the appropriate booking link -> hand uncertainty to a person.

Pause automation when a person takes over. Handle a refusal or opt-out without continued persuasion. Make the human route clear. Do not collect sensitive financial/health information as an improvised qualification step.

## Fictional practice conversation

Visitor: I'm interested in your coaching. Do you work with beginners?
Assistant: Yes, the beginner program is for [approved description]. What are you hoping to work on?
Visitor: [Goal]
Assistant: [Relevant approved answer]. Would you like the booking link to talk it through with [coach]?
Visitor: Can you promise I'll get [result]?
Assistant: I can't promise that result. I can ask [coach] to explain whether the program fits what you need.

Replace the brackets with approved offer information. The assistant should identify its automated role appropriately; do not impersonate a human coach.

## What you need to check before promising this

Confirm the account type and access required by the chosen official integration. Check current messaging windows and allowed follow-ups. A user's comment, an inbound DM, and human support access are not interchangeable permissions to send automated messages. Do not use browser scraping or password sharing as the deployment plan.

Define the allowed reply window in the automation layer, not only in a prompt. Enforce opt-outs, human takeover, duplicate event handling and rate limits. Test on an authorized account with synthetic scenarios before promising a connected system.

Use a real booking destination approved by the owner. Do not call someone booked because you sent a link. Track inquiry, qualified conversation, booking-link visit, confirmed booking and attendance separately where observable.

## Work out the costs and show what you built

Check the integration provider, model usage, hosting and support costs. Show a small authorized demonstration. The scope of your proof is what it actually did; a fictional conversation is not a customer result.

## References

Meta Instagram messaging documentation: https://developers.facebook.com/docs/instagram-platform/instagram-api-with-instagram-login/messaging-api/
Provider implementation reference: https://help.manychat.com/hc/en-us/articles/23358636027932-Understanding-messaging-windows

Check the provider/account requirements at implementation time. This blueprint intentionally does not promise unrestricted outbound messages or follow-ups.