Build an outbound appointment reminder agent with Famulor Famulor published a source-checked proposed configuration for an outbound voice appointment reminder agent that calls customers, reads back the booked date and time, and confirms, reschedules or cancels the appointment against a connected calendar such as Cal.com. The tutorial, the first in a "Build a … agent with Famulor" series, has users design the agent with the open-source Famulor Skill in their AI client and give it workspace access through the Famulor MCP server, running it as a sequence campaign from the "Appointment reminder" template or as a single call triggered by their own system. Famulor states no workspace was changed and no simulation, booking change or phone call was executed for the article, and cites a systematic review of 105 studies (Dantas et al., Health Policy, 2018) finding an average no-show rate of around 23%. Summarize Content With: Short answer: An outbound reminder agent on Famulor calls each customer before their appointment https://www.famulor.io/use-cases/appointment-booking-faqs , reads back the booked date and time, and confirms, moves or cancels it in the same call against your connected calendar. You design it with Famulor Skill in your AI client, give it workspace access through the Famulor MCP server, and run it either as a sequence campaign built from the "Appointment reminder" template or as a single call triggered by your own system. The calendar example below uses Cal.com; other providers have different limits. This guide walks through every step, from the first prompt to a small first batch. This is part one of our tutorial series Build a … agent with Famulor . Each part builds one working agent from the public Famulor docs https://docs.famulor.io and the open-source Famulor Skill https://github.com/Famulor-SI/Famulor-Skill . Build status: This is a source-checked proposed configuration, not a report of a deployed agent. No workspace was changed and no simulation, booking change or phone call was executed for this article. The tests below are acceptance checks to run in your own test workspace. Why reminders still decide whether an appointment happens A systematic review of 105 studies on appointment scheduling found an average no-show rate of around 23%. The same review named a long lead time between booking and appointment as one of the strongest predictors of a missed visit Dantas et al., Health Policy, 2018 https://pubmed.ncbi.nlm.nih.gov/29482948/ . The research comes from healthcare, but the pattern is familiar to every business that books time in advance: dental practices, physiotherapists, workshops, salons, consultants, tradespeople. The 23% figure is a historical healthcare finding, not a benchmark for every industry or a promised result for your business. We covered the business case in AI appointment reminders: cut no-shows https://www.famulor.io/blog/ai-appointment-reminders-cut-no-shows-by-50-in-2026 . This post is the hands-on part: how to build the agent. How teams handle reminders today Most businesses already remind customers in some way. Each common approach has a gap: - Calls from the front desk work well, but they happen during opening hours, by the same people who answer incoming calls. When the day gets busy, reminders are the first thing to slip. - SMS and email reminders are cheap and reach everyone, but they are mostly one-way. A customer who wants to move the appointment has to call back, and many don't. - Keypad phone menus "press 1 to confirm" scale, but they cannot handle "can we do Thursday instead?". What you want is the front-desk call without the front desk: a conversation that can actually change the calendar, at the volume of an automated system. What we're building One voice assistant that: 1. Calls the customer within your calling hours, says which business is calling and why. 2. Reads back the appointment it was given date, time, service . 3. Handles three outcomes in the call: confirm , reschedule to a slot that is actually free, or cancel after an explicit yes. 4. Handles the edge cases: voicemail, wrong person, "call me later", a request to speak to a person, and a request not to be called again. 5. Writes back a clear result you can measure: confirmed, rescheduled, cancelled, no response, do not call. The calendar stays the single system of record. The assistant never "remembers" a booking on its own. It reads and changes appointments only through the calendar tools. Prerequisites - A Famulor workspace on app.famulor.io https://app.famulor.io with an outbound-capable phone number. - A plan that includes Connect AI / MCP for the MCP connection and Campaign sequences for the template-based campaign . SMS or WhatsApp https://www.famulor.io/feature/whatsapp steps need those channels in your plan, too. - A calendar connection that can find and change existing appointments. According to the calendar & booking docs https://docs.famulor.io/assistants/calendar-booking , Cal.com and Acuity Scheduling support find, cancel and reschedule; Calendly supports find and cancel; the built-in Famulor booking engine adds its own management tools. meetergo, eTermin and HighLevel currently offer availability and booking only, so they can't move an existing appointment during a call. - An AI client that supports Agent Skills or MCP for example Claude Code, Cursor or Codex . - A test contact: your own phone number, and a test appointment on that number in your calendar. Don't use real customer data while you build. Architecture: campaign or single call There are two ways to place reminder calls. Both use the same assistant. | | Path A: sequence campaign | Path B: single call per appointment | |---|---|---| | Trigger | You add contacts with their appointment data to a campaign, for example once a day | Your system starts one call when an appointment reaches a point in time | | How | create campaign with a sequence, then launch campaign | make call MCP , famulor create-call CLI or POST /api/v1/calls REST | | Controls included | Calling windows, contact-local time, holidays, retries, AMD and voicemail handling, SMS/WhatsApp/email steps, analytics funnel | Full control over timing in your own code | | Good for | Most businesses with a daily or weekly appointment list | Teams that already run their own scheduling backend | Start with Path A. It gives you dialer rules and reporting without writing code. The rest of this guide follows Path A and shows Path B where it matters. Step 1: Install Famulor Skill and connect MCP The skill gives your AI client the instructions: prompt templates, channel guidance, test scenarios and references for API, MCP, CLI and SDK. The MCP connection gives it authorized access to your workspace. You need both, and the skill alone does not connect your account. npx skills add Famulor-SI/Famulor-Skill --skill famulor-skill Then add a remote Streamable HTTP MCP connection and complete the OAuth sign-in: https://app.famulor.io/mcp If you only want the tools for this tutorial, you can narrow discovery with toolsets. This does not grant more permissions than you approve in OAuth: https://app.famulor.io/mcp?toolsets=assistants,calls,campaigns Client-specific steps, such as the Claude Code plugin or codex mcp add , are in the Famulor Skill docs https://docs.famulor.io/mcp/famulor-skill and the MCP overview https://docs.famulor.io/mcp/overview . Step 2: Describe the agent in plain language Open a new chat in your AI client and give it the brief. Be explicit about what it must not do yet: Use Famulor Skill. Design an outbound appointment reminder assistant for business , a type of business in city . Language: English. The assistant calls customers 24 hours before their appointment. It knows the customer's name, the appointment date and time, and the service from campaign variables. It should: - say who is calling and why, and check it is talking to the right person - read back the appointment and ask whether it still works - confirm, move it to an available slot, or cancel after an explicit yes, using our Cal.com connection - handle voicemail, wrong person, "call me later", a request for a human, and "don't call me again" Use the voice-booking template and the assistant-design reference. Propose the prompt, variables, post-call analysis fields and test scenarios. Save the assistant as a draft, connect our calendar, and set up a campaign from the "Appointment reminder" template in English. Do not place any call, do not launch or start any campaign, and show me everything before you save. Famulor Skill tells the agent to keep drafting and launching apart: building a campaign does not authorize contacting anyone, and a launch needs your own confirmation. You will see that rule again in Step 6. Step 3: The system prompt Here is a prompt in the shape the skill's templates use. Replace the bracketed parts. {{customer name}} , {{appointment date}} and {{service}} are assistant variables that the campaign fills per contact. Identity and purpose You are name , the AI assistant of business . You are calling {{customer name}} about their service type appointment on {{appointment date}} for {{service}}. Your goal is to confirm the appointment, move it to another available time, or cancel it if the customer asks. Opening Use the configured opening: name the business and the reason for the call. Check that you are speaking with {{customer name}}. If not, ask whether they can pass on a message, do not share appointment details, and end the call politely. Do not invent an earlier conversation. If the name or appointment date is missing, do not say a placeholder. Say you are calling about an upcoming appointment and use find appointment to look it up. Confirm Before reading back the appointment, call find appointment and use the date and time it returns. If several appointments match, ask which one the customer means. If no appointment matches, ask for the booking email and full name. If lookup still fails, disclose no other records and use the configured human fallback. Never claim a booking was found. If the customer confirms, thank them and close. Reschedule If the customer wants another time, ask for a preferred day or range. Call check availability before offering any time. Offer two or three of the returned options. Never invent a free slot. Once the customer picks one and confirms it, call reschedule appointment with the exact start value from check availability. Say the appointment has moved only if the tool reports success. If nothing fits, offer approved alternative, e.g. a callback from the team . Cancel If the customer wants to cancel, repeat the date and time and ask for an explicit yes. Then call cancel appointment. Report the result as the tool returns it. Cancellation cannot be undone. Edge cases - Bad time to talk: offer approved callback option, e.g. the built-in Schedule callback tool and end the call. - Wants a person: use configured transfer or callback tool . If that fails, say so and offer the callback. - Does not want to be called again: acknowledge it, stop the reminder, and end the call. Do not ask for a reason. - Questions outside the appointment: answer only from approved information, otherwise offer a callback. Style Keep each turn short. Ask one question at a time. Speak dates and times clearly in the calendar's timezone. Do not promise an SMS or email unless it was actually sent. Finish Use end-call tool once the outcome is settled, without a second farewell. Two details from the skill's assistant design reference https://github.com/Famulor-SI/Famulor-Skill/blob/main/skills/famulor-skill/references/assistant-design.md matter here. Missing {{...}} values become empty, so the prompt needs a fallback, which is why the opening tells the assistant what to do without a name or time. And variables must be defined on the assistant before you rely on them. Your agent can do that with set assistant variables and read them back with get assistant variables . The set operation replaces the definitions, so preserve unrelated variables on an existing assistant. Give each variable a sensible default value , as the variables docs https://docs.famulor.io/assistants/variables recommend. Configure the bracketed tools, not just the words. Under Assistant Settings → Advanced → Tools , assign the actual End call , Call transfer with an approved destination and unavailable path and, if wanted, Schedule callback tools. Use their assigned names in the prompt. Without a working callback or handover action, do not promise that one was created. Their settings and availability rules are in the built-in tools docs https://docs.famulor.io/assistants/built-in-tools . The appointment confirmation in this design is an analysis result; no separate calendar “confirmed” status is written. Step 4: Connect the calendar tools Connect your calendar under Booking → Integrations , pick the event type, check the timezone, and turn on Cancel and Reschedule for that connection. Booking is a separate permission. Then assign it in Assistant settings → Calendar or PUT /api/v1/assistants/{id}/integrations . Each assigned integration adds its tools to every call: | Tool | What it does in this agent | |---|---| | find appointment | Finds the customer's upcoming appointment for the connected event type | | check availability | Returns real open slots for a date range | | reschedule appointment | Moves an appointment found in the same call, after the new time is confirmed Cal.com, Acuity | | cancel appointment | Cancels an appointment found in the same call, after an explicit confirmation | | book appointment | Books a new slot, for example on Calendly, where a "move" is a cancel plus a new booking | On an outbound call, Cal.com matching uses the number you dialled, not the assistant's own number. That only works if the phone number is stored on the booking, so make the phone question on your Cal.com event type required and collect numbers with their country code. If there's no phone match, the assistant asks for the booking email and full name. The Cal.com reschedule guide https://www.famulor.io/blog/calcom-reschedule-cancel-appointments-famulor covers this in more depth. Timezones are the most common source of confusion. The calendar's timezone governs availability, and the assistant's timezone governs relative dates such as "next Friday". Always pass the exact start value that check availability returned. Step 5: Define the result you want to measure Open Assistant Settings → Analysis and add Yes / No fields that the transcript can prove, for example: - appointment confirmed : the customer confirmed the existing appointment - appointment rescheduled : the customer agreed a new time and the assistant confirmed the move - appointment cancelled : the customer asked to cancel and the assistant confirmed the cancellation - callback requested : the customer asked to be called back by the team These are proposed extraction-field names, not built-in fields. Post-call analysis https://docs.famulor.io/assistants/analysis reads the transcript; its labels do not independently prove that the calendar changed. Check the tool receipt and the calendar record as well. Describe each field as an observable fact, not a mood. The campaign docs are clear about this: when goal tracking behaves oddly, the cause is usually the goal field's description, not the retry logic. Step 6: Build the campaign from the template Your agent can list the gallery and show the closest returned reminder template. Use its actual returned ID, never an invented template ID. If using the CLI snippets instead of MCP, the CLI docs https://docs.famulor.io/cli/overview require Node.js 22+, API Access, npm install --global famulor and famulor auth login ; enter the key only in the hidden prompt. Listing templates is read-only: famulor list-campaign-templates --language en --category appointments The same list is available as the MCP tool list campaign templates . The sequence docs https://docs.famulor.io/campaigns/sequences-and-analytics describe the Appointment reminder template as an SMS reminder first. A reply ends the sequence as successful. Otherwise a call confirms the appointment, reschedules it or records the cancellation. You can keep that shape or change it. For example, call first and send an SMS only after no response. Before the template can be saved, every SMS step needs exactly one sender from number id or rcs sender id , and every WhatsApp step needs connector id and an approved template id . Your agent should only use IDs that your workspace returns. Then set the campaign rules in Settings and Launch : - Calling window: for example Mon–Fri 09:00–18:00. With a sequence you can set contact timezone mode to contact so each contact is called in their local time, and holidays.public to skip public holidays. - Attempts and delays per call step , with a voicemail choice per attempt: hang up, or leave a short message drop message . Retrying at a different hour usually improves reach. - Answering machine detection AMD : Conservative fewer false hang-ups or Aggressive faster detection . - Outcomes: use AI decides with sentences like "The customer confirmed the appointment", or preset rules such as Goal field is true . Do not call is built in. It wins over your own outcomes and ends the contact. Now connect the appointment data to the prompt. In a campaign, a lead's custom field fills the variable with the same key at dial time, so a CSV column appointment date becomes {{appointment date}} . This only works once customer name , appointment date and service exist as workspace Custom Attributes and are selected for this assistant variable source lead . A field saved only on one contact is not enough. list variable sources shows what is available. Then add your test contact with add leads or a CSV import. Your agent stops here. A draft is not a launch. Step 7: Test before anyone gets a call Famulor Skill separates test layers, and each one proves something different. A chat simulation checks behavior and tool use against simulated responses. A voice test checks speech, turn-taking and tools on the real audio path. Voice simulations execute the configured tools, so bookings can be real. Point them at your test appointment. Ask your agent to create tests with create assistant test and run them with run assistant test CLI: famulor run-assistant-test