Appointment intent and callbacks on inbound lines

Let us be clear at the top, because it is the single most important thing on this page: Agent Vani does not run outbound reminder or callback campaigns today. It does not dial your appointment list to remind people, and it does not auto-call people back. At launch it answers inbound calls to the numbers you attach. Outbound calling using the same agent is a later release. If your plan depends on the agent phoning patients, customers, or leads, that capability is not shipped yet — plan around inbound.

What Agent Vani does do, and does well, is handle the appointment side of your inbound line as a real, two-way conversation. When someone calls to ask about their appointment, reschedule, check your availability, or request that a person call them back, the agent talks with them live — two-way and realtime, so they can interrupt, correct, and steer, and the agent keeps up instead of making them wait through a slow, turn-based script. It captures what they need and leaves a clean record for your team.

Why the honesty matters here

"Appointment reminders and callbacks" usually implies outbound: the system reaches out to people. Plenty of tools promise exactly that. We are telling you plainly that this one, right now, does not — because shipping a page that implies auto-dialling when the product answers inbound would be dishonest, and a caller-facing product built on a dishonest promise is not one you should trust with your phone line. When outbound arrives, it will use this same agent, and this page will say so. Until then, everything below is about the inbound conversation and about capturing intent your team acts on.

What the inbound appointment conversation covers

On calls that come to you, the agent can:

• Answer availability questions. "Are you open Saturday?" "What times do you have next week?" — grounded in the knowledge and hours you configured.
• Take reschedule and cancellation intent. When a caller wants to move or cancel, the agent captures exactly what they want — the existing appointment, the preferred new time — as a clean request for your team to confirm.
• Capture new appointment requests. For callers asking to book, it records what they want and when, as booking intent your team confirms. This overlaps with sales and booking intake.
• Take callback requests. When a caller wants a person to ring them back, the agent captures who, why, and how to reach them — so your team can return the call. The agent itself does not place that return call; a person does.
• Answer the routine questions around appointments: what to bring, where to go, timings, policies — from your approved knowledge.

Every one of these produces a visible record in your workspace: who called, how long, what they asked for, how it ended. Your team's follow-up starts from a real conversation, not a guess.

What "captured, not completed" means

This is the honest mental model for the whole page. The agent captures intent on inbound calls; your team or your own systems complete the action.

• A reschedule request is captured; a person or your booking system confirms the new slot.
• A callback request is captured; a person calls back.
• A new appointment is captured as intent; your team confirms the slot is actually held.

Treat every captured item as a request until it is confirmed on your side. If you tell callers "you're all set" before your team has confirmed, you will end up with people arriving for slots that were never held. Wire your follow-up so captured intent is actioned promptly, and make sure the agent only promises what you will actually deliver.

What you control

• Persona and voice. How the agent sounds when it handles appointment calls, and what it may say about availability and policies.
• Knowledge. Your hours, what services you offer, what to bring, location details, cancellation policy — the agent answers from what you approved.
• Hours and numbers. Bring the line people already call for appointments; set when the agent is on. It can cover overflow, after hours, or every call.
• Capture rules. What information the agent must collect for a reschedule, a callback, or a new request so your team has everything it needs to act.
• Handoff line. When an appointment call should go straight to a person — a complicated case, an upset caller, anything outside the routine.

A checklist for appointment lines

• Write down what "captured" must include. For a callback: name, number, reason, urgency. For a reschedule: which appointment, preferred new time. Incomplete captures create phone tag.
• Ground availability answers. If the agent states hours or open days, make sure those facts are current in its knowledge. Stale hours are worse than no answer.
• Never let it confirm what it cannot hold. The agent captures; your team confirms. Configure it to say "I'll have the team confirm and get back to you," not "you're booked."
• Set the follow-up SLA. Decide how fast captured callbacks and reschedules get actioned, and make sure they land where your team looks. Coverage without follow-up is just a nicer way to lose people.
• Test the reschedule dance. Call in, ask to move an appointment, change your mind about the time, interrupt. This is the messiest common appointment call — make sure the agent handles it.

Failure modes to design around

• Implying outbound. Do not configure the agent to say "we'll call you back at 3pm" as if it will place the call. A person places it. Say "our team will call you back," and make sure they do.
• Confirming un-held slots. The most damaging failure is a caller who believes they have an appointment they do not. Keep the agent to capturing intent unless you have genuinely wired confirmation on your side.
• Dropped captures. A callback request that never reaches a human is worse than a missed call, because the caller thinks they have been helped. Make the follow-up path reliable.
• Stale knowledge. Availability and policies change. If the agent answers from old facts, it will confidently mislead callers. Keep the knowledge current.

Where this fits with other coverage

Appointment calls rarely arrive on their own line. They come in mixed with support questions, sales enquiries, and after-hours calls. So this pattern usually rides alongside others: inbound support for the general questions, after-hours coverage for the calls that land when your desk is closed, and sales and booking intake for new-business appointments. The agent is the same; you configure it to handle whatever mix your line receives.

What this costs you

The control plane where you configure persona, knowledge, hours, capture rules, and numbers — and where you review every call — is free, with no per-seat charge. Agent Vani is billed by the minute of conversation. Appointment and callback calls tend to be short and structured, so they map to modest, predictable usage you can see in the console. You can start on a trial with no credit card and run real appointment-style calls before committing. See pricing and, for the launch mechanics, the going-live checklist.

Going live for appointment lines

1. Configure the persona and load current hours, services, and policies.
2. Define exactly what a captured reschedule, callback, or new request must include.
3. Attach your line and set hours.
4. Set the follow-up path so captured intent is actioned fast — by a person.
5. Call in and test reschedules, callbacks, and availability questions, including messy ones.
6. Publish, review the first real calls, and tune capture completeness and the handoff line.

Because the calls are visible in your workspace, you will quickly see whether captures are complete and whether your follow-up is keeping up. For the full path, see the going-live checklist and the product overview.

A walkthrough of one appointment call

A caller dials in on a Tuesday morning: "Hi, I've got something booked Thursday but I need to move it." This is the most common appointment call and also the messiest, because callers change their minds mid-sentence. The agent answers in their language, confirms which appointment they mean, and asks for a preferred new time. The caller offers Friday afternoon, then reconsiders — "actually, can you do Saturday morning instead" — and the agent follows the change without forcing a restart, because the call is two-way and realtime. It captures the reschedule request: the existing appointment, the preferred new slot, and how to reach the caller. Critically, it does not tell the caller "you're moved to Saturday" — it says the team will confirm the new time and get back to them, because the slot is not held until your side holds it. The caller hangs up knowing exactly what happens next. Your team opens the workspace to a complete reschedule request they can confirm in one action, not a vague voicemail they have to decode and call back to clarify. That is capture done honestly.

Designing the capture so follow-up is one step

The value of an inbound appointment line lives entirely in whether the captured request is complete enough to action without a second call. A half-captured reschedule — "someone wants to move something, call them" — just converts a phone call into phone tag. So design the capture deliberately:

• For a reschedule: which appointment, the preferred new time (and a backup), and the best number to confirm on.
• For a cancellation: which appointment and, if you care, a light reason so your team can decide whether to offer an alternative.
• For a new request: what service, rough preferred window, and contact details — treated as intent, not a held slot.
• For a callback: who, the reason, the urgency, and the best time and number to reach them, so the person returning the call succeeds on the first try.

The test is simple: could a team member action this captured record without calling the person back just to gather more information? If not, tighten what the agent must collect. Because every call is visible in your workspace, you can audit capture completeness directly and fix the fields that keep coming back thin.

FAQ

Can Agent Vani call my customers to remind them of appointments?

No. This is the most important answer on the page: at launch Agent Vani answers inbound calls only. It does not place outbound reminder or callback calls, and it does not run dialling campaigns. Outbound using the same agent is a later release. Today, plan for inbound conversations and captured intent.

So what does it do for callbacks?

On an inbound call, it captures the callback request — who wants a call, why, and how to reach them — as a clean record. A person on your team then places the return call. The agent does not dial the caller back itself.

Can it actually book the appointment, or just capture the request?

It captures the request as booking intent. Your team or your own booking system confirms the slot. Until confirmed, treat it as a request — do not tell callers they are booked before your side has held the slot. See sales and booking intake.

Does the appointment call feel like a real conversation?

Yes. It is two-way and realtime — the caller can interrupt, change the time they want, and steer, and the agent keeps up instead of running a slow, turn-based script. That responsiveness is what makes rescheduling by phone feel easy rather than painful. See two-way realtime vs turn-based AI calls.

How do I make sure captured callbacks actually get returned?

Set a follow-up path and an SLA: decide how fast captured requests are actioned and make sure they land where your team looks. Every call is visible in your workspace, so you can audit whether follow-up is keeping pace. See the product page.

What will this cost?

The control plane is free with no per-seat charge; Agent Vani is billed per minute. Appointment and callback calls are usually short and structured, so usage stays modest and predictable. You can trial it with no card. See pricing.

How does this differ from general support coverage?

The mechanics are the same agent and the same visibility; the difference is what you optimise for. Appointment lines live or die on capture completeness — a reschedule or callback that your team can action in one step without ringing back to gather more detail. General inbound support optimises more for resolving questions outright. Most teams run both on one line, since real callers mix appointment questions with everything else, and you simply configure the agent to handle the whole mix.