---
title: "How to Set Up an AI Setter (Step by Step)"
slug: how-to-set-up-an-ai-setter
author: "Leonardo Maldonado"
category: "AI Setter Operations"
articleType: how-to-guide
tags: ["set up an AI appointment setter","AI setter setup guide"]
publishedAt: 2026-09-28T09:00:00.000Z
updatedAt: 2026-10-27T12:00:00.000Z
canonical: https://setluca.com/blog/how-to-set-up-an-ai-setter
---# How to Set Up an AI Setter (Step by Step)

> To set up an AI setter, connect your DM channels, link your calendar (Calendly, Cal.com, Google Calendar, or a manual link on SetLuca) and pass leads to your CRM through webhooks or the API. Train it on your writing style and offer, set your qualifying questions and escalation rules. On SetLuca, Instagram, Telegram and Messenger are live, and WhatsApp is coming soon. Auto-send is on by default on every channel, and you can switch any channel to review.

## Key takeaways

- Setup is six steps: connect channels, connect calendar and CRM, set booking rules, train writing style, set qualifying questions, then choose auto-send or review per channel and write escalation rules.
- The calendar step is the one people skip, and double-booking is the failure that follows. Two-way sync plus a live availability check at the moment of offer prevents it.
- Each channel has its own gate. WhatsApp needs an approved display name and only allows free-form replies inside a 24-hour customer service window, per Meta's developer documentation.
- With SetLuca, auto-send is on by default on every channel, and you can switch any channel to review.
- Speed is the point. A lead contacted in five minutes is far likelier to qualify than one reached at thirty, so the setter earns its keep the moment it goes live.

---

Learning how to set up an AI setter takes about an hour, and most of it goes into teaching it to match the way you write and wiring it to your calendar so it never offers a slot you don't have. Six moves: connect your channels, connect your calendar and CRM, set your booking rules, train the writing style, write your qualifying questions, then choose auto-send or review for each channel. For the mechanism behind each part, we cover [how AI appointment setters work](/blog/how-ai-appointment-setters-work) separately.

## How to set up an AI setter: the 6-step map

![Setup path for an AI setter: connect a channel, teach it the way you write, pick a sales framework, connect your calendar, choose auto-send or review](https://cms-media-emdash.setluca.com/01M55HHAG7TRH1KRRH22K9QKPB.png)

*The setup path at a glance. Auto-send is on by default, and you can switch any channel to review.*

You set up an AI setter in six steps: connect channels, connect calendar and CRM, set availability, train writing style, pick qualifying questions, then choose auto-send or review and write escalation rules.

| Step | What you do | Done when |
| --- | --- | --- |
| 1 | Connect DM channels | Live channels show in the inbox |
| 2 | Connect calendar and CRM | Booking link works; leads reach your CRM via webhook or API if you use one |
| 3 | Set availability | Slots respect lead timezone and your capacity |
| 4 | Train writing style and offer | 20 real replies loaded; prices current |
| 5 | Qualifying questions | 2 to 4 questions before the calendar link |
| 6 | Auto-send or review, plus escalation | Each channel set to auto-send or review; handoff rules written |

How to set up an AI setter breaks into six moves: channels, calendar and CRM, booking rules, writing style, qualifying questions, and review settings. Channel status on SetLuca: Telegram, Instagram and Messenger are live; WhatsApp is coming soon. Auto-send is on by default, and you can switch any channel to review.

## What do you need before you start?

Gather four things first and the rest of this takes an hour instead of an afternoon.

- 20 to 50 recent DM threads, including a few price conversations.
- Your offer in plain terms: who it's for, what it costs, what a good fit looks like.
- The three or four things you ask before offering a call. See [lead qualification questions for coaches](/blog/lead-qualification-questions-for-coaches).
- Admin access to each channel, the Meta Business portfolio that owns your Page, your calendar, your CRM login, and your real working hours.

## Step 1: Connect your DM channels

Start with the channels where your leads already message you, and expect each to gate access differently. Meta's documentation sets the requirements: Instagram needs a professional account, WhatsApp an unused business number and an approved display name, Messenger a Page you administer.

**Instagram.** Business or creator account, not personal. The path then forks. Instagram Login needs no linked Facebook Page and uses `instagram_business_manage_messages`; Facebook Login requires a linked Page plus `instagram_manage_messages` and `pages_show_list` ([Meta, Instagram Platform](https://developers.facebook.com/docs/instagram-platform/overview)). Either way, turn on third-party message access in the app's settings, or the connection looks fine while nothing arrives.

**WhatsApp.** The longest one. You need a Meta app tied to a business portfolio, a WhatsApp Business Account, a number not already on a personal WhatsApp, a display name, a webhook, and a permanent token from a system user ([Meta, WhatsApp Cloud API](https://developers.facebook.com/documentation/business-messaging/whatsapp/get-started)). One rule shapes everything else. A customer service window opens for **24 hours** each time someone messages you, and outside it only approved templates send ([Meta, WhatsApp messaging docs](https://developers.facebook.com/documentation/business-messaging/whatsapp/messages/send-messages)). Templates are reviewed on submission, usually within 24 hours ([Meta, template fundamentals](https://developers.facebook.com/documentation/business-messaging/whatsapp/templates/overview)). Submit yours on day one; see the [WhatsApp 24-hour window](/blog/whatsapp-24-hour-window) guide.

**Messenger and Telegram.** Messenger runs off a Page you administer, with a 24-hour standard window and a Human Agent tag that lets a person reply up to **7 days** later ([Meta, Messenger Platform policy](https://developers.facebook.com/docs/messenger-platform/policy/policy-overview)). Telegram is just a bot token.

| Channel | Needs before you connect | Reply window | Connect first if |
| --- | --- | --- | --- |
| Instagram | Professional account, permission, toggle | Rolling | DMs start from Reels or comments |
| WhatsApp | Portfolio, unused number, display name | 24h, then templates | Leads are abroad or already text |
| Messenger | A Page you administer | 24h, 7 days with tag | You run Facebook ads or a group |
| Telegram | A bot token | None fixed | You sell to crypto or devs |

Connect the channels where your leads already message you. On SetLuca that means Instagram, Telegram and Messenger today; WhatsApp is coming soon. If you're not sure which channel carries your volume, start with [your primary DM channel](/blog/best-dm-channel-for-coaches) and add the others once it's running.

WhatsApp passed **3 billion monthly users** in 2025, Telegram **1 billion**, Instagram near **2 billion** ([TechCrunch, 2025](https://techcrunch.com/2025/05/01/whatsapp-now-has-more-than-3-billion-users/); [Telegram, 2025](https://x.com/durov/status/1902454590747902091); [DataReportal, 2025](https://datareportal.com/social-media-users)).

## Step 2: Connect your calendar and pass leads to your CRM

Link the calendar before the setter offers a single time. Booking is where a DM turns into money, and it's also where the admin lives. On SetLuca, booking connects to Calendly, Cal.com, Google Calendar, or a manual link, so check that your scheduler reads every calendar you use.

Ask for two-way sync. One-way sync writes bookings in but never reads what's already there, so the dentist appointment you added on your phone stays invisible and the setter books over it. Two-way sync reads busy blocks from every calendar you list, so list all of them.

Then check how the tool looks up your free time. A setter that grabs your open slots each morning will offer a 4pm that got taken at 2pm. You want a live check when times are offered, and another before the event is created. Google's Calendar API can push a notice to an app the moment something changes, instead of the app asking every few minutes, though the docs warn those channels expire and notices go missing ([Google, Calendar API push notifications](https://developers.google.com/workspace/calendar/api/guides/push)). Good integrations still check on a timer as a backstop.

CRM mapping is the other half. Unmapped fields mean the lead lands as a nameless row and your follow-up never fires. Map these:

| Captured in the DM | Where it belongs | Why it matters |
| --- | --- | --- |
| Handle or phone number | Contact identifier | Deduplicates a lead across channels |
| Goal, in their words | Notes or custom field | You read it before the call |
| Timeline and budget signal | Lead status or score | Decides who gets chased |
| Channel and first-contact time | Source fields | Shows which channel earns calls |
| Booked time with zone | Meeting record | Stops reminders at the wrong hour |

SetLuca isn't a CRM, and it doesn't sync to one natively yet: HubSpot, GoHighLevel and iClosed integrations are in progress. Today you pass leads and booked-call events to whatever CRM you use through webhooks or the API. Send one test lead through the path, then open the record and check every field landed.

## Step 3: Set your availability, capacity, and time zone rules

Booking rules stop a working setter from wrecking your week. Set six: working hours per weekday, maximum calls per day, buffer either side, minimum notice, booking horizon, and the zone each call is quoted in. Calendar APIs store event times with an explicit offset, so a call created without the lead's zone gets quoted in yours.

Fifteen minutes of buffer after a call gives you time to write notes while it's fresh, and fifteen before stops a call landing the second you finish a client session. Set minimum notice to two hours, or you'll get a booking for eleven minutes from now.

Capacity is a limit, not a preference. Decide the honest maximum of calls you can run in a day without the last one being bad, then set it one below.

Time zones need three settings. Store the lead's zone, quote every slot in _their_ zone, and confirm with both written out. Block slots landing between 10pm and 7am local to the lead. Daylight saving matters too, since the US and Europe change on different dates. Confirmations done right are the cheapest way to [cut no-shows](/blog/how-to-reduce-no-shows-on-sales-calls).

## Step 4: Train it on your writing style and offer

Teach the setter how you talk and what you sell. This is the step that decides whether a lead feels answered by you or by a company, and it's worth the extra twenty minutes.

Feed it your real past DMs. It learns your openers, your emoji habits, how you handle "how much is it," and how you close. Give it threads, not a polished script. For the deeper method, see [how to train AI to reply the way you write](/blog/how-to-train-ai-to-reply-in-your-voice).

Then write a short offer brief. Most tools take one free-text block. Copy this:

```abap
WHO I AM
I'm [name], a [niche] coach. I help [audience] get [outcome] in [timeframe].

WHAT I SELL
[Program], [length], [format], [price]. Payment plans: [terms].

GOOD FIT / NOT A FIT
[Budget range and readiness signals. Then who I turn away, politely.]

BEFORE OFFERING A CALL, LEARN
1. What they're changing right now. 2. Timeline. 3. Coached before?

HOW I TALK
Lowercase, short lines, no exclamation points. One question per message.
I never pitch before they've told me their goal.

PRICE QUESTIONS
Give the real number: [price]. Never dodge it. Then ask what's making
them consider coaching now.

NEVER DO THIS
1. Promise a specific weight, income, or medical result.
2. Invent a discount, deadline, or bonus I haven't listed.
3. Answer a refund or billing question. Flag it for me instead.
4. Reply to anyone who didn't message me first.
```

The good-fit and not-a-fit block is the one people leave out, and the one that keeps you out of trouble. The writing style isn't fixed at setup. Add more real threads whenever your offer or the way you write changes.

## Step 5: Set your qualifying questions

Decide what the setter must learn before offering a call. Three or four is enough: goal, timeline, budget range, and whether they've worked with a coach before. Any more and the thread starts to feel like an intake form.

Order them the way a person would. Goal first, because it's easy to answer and earns the next question. Timeline second. Money last. Ask about budget in message two and it reads like a form.

Write a disqualify rule too. If someone's browsing, or wants the outcome in a timeframe you can't deliver, let the setter say so warmly and offer a resource instead of a call. We break down [how AI qualifies leads in DMs](/blog/how-ai-qualifies-leads-in-dms) separately.

## Step 6: Choose auto-send or review, and set escalation rules

Here you decide how much control to keep. With SetLuca, auto-send is on by default on every channel, so replies go out the way you write as leads message. You can switch any channel to review, and on that channel each reply waits for your tap to approve, edit, or reject before it sends.

Set the disclosure rule here too. If a lead asks whether they're talking to a person, the reply discloses plainly that it's AI-assisted and that a coach is reachable, Meta requires disclosure where the law does, and California's SB 1001 is one of those laws. Never write a script that denies it.

Define your escalation triggers explicitly, so a handoff isn't a judgment call at 2am. A thread stops and waits for you when any of these appear:

- Refund, chargeback, or billing language.
- A price objection that survives one honest answer.
- Any mention of injury, illness, pregnancy, or mental health.
- Anger, a complaint, or a threat to post about you.
- A question the offer brief doesn't cover.
- A message from an existing or former client.

The ladder is short. The reply is held, and the thread is flagged to the top. If you haven't opened it within your own response promise, the setter sends one pre-approved holding line: "let me check on that and come back to you today." Then you take the thread.

Escalation triggers work the same whichever mode a channel is on: the threads above come to you instead of getting an automatic answer. If one channel carries most of your money or health conversations, switching just that channel to review is a reasonable choice, while the others stay on auto-send.

Speed is why the setup pays off. Leads contacted within five minutes stay warmer than leads left for half an hour, and that gap is hard to close later.

## A hypothetical example: booking rules for a nutrition coach

To make the booking rules concrete, picture a hypothetical nutrition coach in Lisbon who sells a 12-week program and gets most of her leads on Instagram. She might allow three calls a day with 15-minute buffers, two hours' minimum notice, and no calls after 7pm Lisbon time. Many of her referrals live in Brazil, so every slot is quoted in the lead's own zone and the confirmation shows both times.

Her offer brief would list the program price and payment plan, her three qualifying questions, and the escalation triggers for refunds and health questions. Nothing about her setup depends on a special feature; it's the six steps above, filled in with her own details.

## What should you track weekly after launch?

Check five numbers every Friday for a month, then monthly. None of them is a vanity number, and each one tells you which step of the setup to go back to.

| Metric | Healthy sign | When it misfires | What to do |
| --- | --- | --- | --- |
| Median first-reply time | Minutes, not hours | Replies sit overnight | Check which channels are on review, or set a reminder for that queue |
| Reply edit rate (channels on review) | Falling weekly | Still editing most replies after a month | Feed 20 more threads, tighten the "how i talk" block |
| Qualified-conversation rate | Stable or rising | Lots of chat, few qualified | Move goal to message one |
| Calls booked per 100 chats | Rising as writing style settles | Flat while replies read fine | Add a question before the call offer |
| No-show rate | Low and steady | Spikes after a new channel | Check the zone on confirmations and the reminder hour |

Read five full threads a week too. Numbers say something changed; threads say what.

## What breaks during setup, and how do you fix it?

Most setup failures are permissions, calendar mismatches, or review rules left too loose. Use this table to match the symptom to the fix.

| Symptom | Likely cause | Fix |
| --- | --- | --- |
| Connected, but no messages arrive | Message-access toggle off, or the webhook didn't save | Re-check the toggle, resubscribe the webhook, send a test DM |
| Two leads in the same slot | One-way sync, or availability cached not checked live | Two-way sync, add every calendar, re-check before booking |
| WhatsApp replies fail after a day | The 24-hour customer service window closed | Send an approved template; submit templates early, review takes 24 hours |
| Replies sound generic | Trained on a sales page instead of real threads | Replace the training set with 20 to 50 real conversations |
| Bookings land at the wrong hour | Lead's zone unstored, or daylight saving moved blocks | Quote in the lead's zone, confirm in both, re-check after each DST change |
| Setter answers a refund question | No escalation trigger for billing language | Add refund, chargeback, and billing to your escalation list |

## Which setup mistakes should you avoid?

Most setup mistakes come from moving too fast. The costliest is letting the setter answer leads before it has your real threads and offer brief, because one off-style reply can cost you the lead. In Zendesk's 2025 CX Trends report, **63% of consumers said they'd switch to a competitor after one bad experience**, up 9% year over year ([Zendesk, 2025](https://www.zendesk.com/newsroom/articles/2025-cx-trends-report/)).

**Thin training.** Feed it 20 to 50 real threads, not a sales page, and read a sample of replies every week.

- **Skipping the calendar step.** A setter that can't see your real week offers slots you don't have, and the apology costs more than the booking.
- **Leaving WhatsApp templates until you need them.** Review takes time, and the window closes at 24 hours either way.

## Which edge cases does your setup have to handle?

**The 2am replier abroad.** Answering at 2am is the advantage. Booking at 2am isn't. Let the setter reply immediately, offering slots only inside working hours in the lead's zone.

**The lead who resurfaces after four months.** On WhatsApp the customer service window closed long ago, so the only opener available is an approved template. On Instagram and Messenger the thread reopens when they message you. Decide now which template covers a cold return.

**The person who asks whether they're talking to a bot.** The setter says yes, plainly, and offers to bring you in. Meta requires disclosure where the law does, California's SB 1001 among them, and recommends it everywhere else.

**The double-booking that happens anyway.** It will, once. Have the recovery ready: you message first, you name the mistake, you offer two new times and a make-good. Then find whether it was the sync, the cache, or a missing calendar.

## What is the one honest limit of an AI setter setup?

Setup can't skip the human part. Some replies won't sound quite like you, especially on odd questions or emotional objections. That's why the training threads, the offer brief and your escalation rules matter, and why you can switch any channel to review. Coaches who skip the training step take a real risk. They're the ones who send a robotic reply to a hot lead and regret it.

There's a second limit worth naming. A setter is only as accurate as the systems behind it. If your calendar is wrong, it will confidently book the wrong time. If your offer brief is vague about payment plans, it will be vague with a lead who's ready to pay. It doesn't know what it wasn't told, and it won't flag the gap, so your escalation rules and weekly thread reads are how you find those holes. For the full category picture, see [what a DM setter is](/blog/what-is-an-ai-dm-setter), then shortlist tools in [best AI DM setter](/blog/best-ai-dm-setter).

That is how to set up an AI setter without guessing. Six steps, auto-send or review chosen per channel, then measure. Once it is live, run the numbers with [AI appointment setter ROI](/blog/ai-appointment-setter-roi).


## FAQ

### How do I set up an AI setter, step by step?

Connect your DM channels, then link your calendar and pass leads to your CRM. Train the setter on your real past messages and your offer, list your qualifying questions, and set escalation rules. On SetLuca, auto-send is on by default on every channel, and you can switch any channel to review if you want to approve replies first.

### How long does it take to set up an AI setter?

Usually about an hour of active setup, most of it spent feeding the setter your past DMs so it learns your writing style. Connecting a channel takes minutes. WhatsApp setups take longer, since Meta reviews message templates on submission and that review can take up to 24 hours. On SetLuca, WhatsApp is coming soon.

### Do I need a Facebook Page to connect Instagram?

It depends on the route your tool uses. Meta's Instagram API with Instagram Login works without a linked Page and uses the instagram_business_manage_messages permission. The Facebook Login route requires a linked Page plus instagram_manage_messages and pages_show_list. Either way, your Instagram account has to be a professional account, business or creator.

### How do I stop an AI setter from double-booking me?

Use two-way calendar sync, list every calendar you actually use including personal ones, and confirm the tool checks availability live when it offers times rather than from a morning cache. Google's Calendar API supports push notifications for changes, but the documentation warns that some notifications can be lost, so a reconciliation check matters too.

### Will the AI send DMs before I approve them?

Yes, by default. SetLuca's auto-send is on for every channel, so replies go out the way you write without waiting for you. Switch any channel to review and each reply waits for your tap to send, edit, or reject. Escalation rules hold sensitive threads for you either way.

### What should trigger a handoff to me?

Define the triggers before launch: refund or billing language, a price objection that survives one honest answer, any mention of injury or illness, anger or complaints, messages from existing clients, and anything the offer brief doesn't cover. Messenger's Human Agent tag allows a manual reply up to 7 days later, per Meta's messaging policy.

### Is it safe to turn on an AI setter on a new Instagram account?

Answering real inbound DMs is the low-risk part. Bans tend to come from sudden, high-volume, cold activity, not from replying to people who messaged you first. Use a tool that connects through Meta's official API, keep it to inbound conversations, and set escalation rules so sensitive threads come to you.

### What should I track in the first month after going live?

Five numbers weekly: median first-reply time, reply edit rate, qualified-conversation rate, calls booked per 100 conversations, and no-show rate. Read five full threads a week too. The numbers tell you something changed; the threads tell you what, and which setup step to go back and fix.


## Sources

1. [Meta : WhatsApp Cloud API get started (business portfolio, phone number, display name, webhooks, tokens)](https://developers.facebook.com/documentation/business-messaging/whatsapp/get-started)
2. [Meta : WhatsApp send messages and the 24-hour customer service window](https://developers.facebook.com/documentation/business-messaging/whatsapp/messages/send-messages)
3. [Meta : WhatsApp template fundamentals (review, status values, categories)](https://developers.facebook.com/documentation/business-messaging/whatsapp/templates/overview)
4. [Meta : Messenger Platform messaging policy (24-hour standard window, Human Agent tag)](https://developers.facebook.com/docs/messenger-platform/policy/policy-overview)
5. [Meta : Instagram Platform overview (professional accounts, Page linkage, messaging permissions)](https://developers.facebook.com/docs/instagram-platform/overview)
6. [Google : Calendar API push notifications (webhook channels, expiration, delivery caveats). Retrieved October 17, 2026.](https://developers.google.com/workspace/calendar/api/guides/push)
7. [Zendesk : 2025 CX Trends Report (switching after one bad experience). Retrieved October 17, 2026.](https://www.zendesk.com/newsroom/articles/2025-cx-trends-report/)
8. [DataReportal : Global Social Media Statistics (Instagram reach and usage). Retrieved October 17, 2026.](https://datareportal.com/social-media-users)
9. [TechCrunch : WhatsApp now has more than 3 billion users (2025). Retrieved October 17, 2026.](https://techcrunch.com/2025/05/01/whatsapp-now-has-more-than-3-billion-users/)
10. [Telegram (Pavel Durov) : Telegram surpasses 1 billion monthly active users (2025). Retrieved October 17, 2026.](https://x.com/durov/status/1902454590747902091)
11. [California Legislative Information : SB 1001, Bots: disclosure (Business and Professions Code §17940 to 17943)](https://leginfo.legislature.ca.gov/faces/billTextClient.xhtml?bill_id=201720180SB1001)

---

Published by SetLuca.