Use case
An AI scheduling agent books, confirms, reschedules, and reminds, so your calendar fills without your team touching the routine calls. On PeachDesk that agent is a call flow you design in the agent builder, run on telephony you control, and keep.
You assemble the scheduling agent from building blocks, then tune each branch against real booking calls. The pieces:
Scheduling is a high-volume surface. Every booking call, every reschedule, and every reminder is a call, and on a typical turnkey scheduler each one runs on a per-minute meter. Reminders alone can outnumber the appointments they protect, so the meter grows with your calendar, on someone else's terms.
On PeachDesk the alternatives are structural. Bring your own provider keys (BYOK) and inference cost is your own agreement with your providers. Self-host and route stages to Local mode on your GPUs and there is no per-minute provider charge on those stages; you pay for GPU capacity. Either way, the flow and the calendar connection are assets your team designed and can keep improving, not a configuration trapped in a rental.
For the numbers behind that trade, see PeachDesk pricing. If scheduling is one branch of a broader front-desk flow, read AI receptionist call flows.
PeachDesk does not ship a built-in calendar product. The connection between the agent and your scheduling system is something you build with custom HTTP tools and webhook nodes, which is exactly why it fits your booking rules instead of a vendor's defaults. If you want a finished scheduling app with a calendar baked in, a turnkey tool will serve you better.
Frequently asked questions
Through the connection you build. PeachDesk agents can call custom HTTP API tools and send templated HTTP requests from inside a workflow, so you point a tool at your scheduling system or booking API and the agent reads availability, writes bookings, and updates them mid call. There is no built-in calendar product; the calendar connection is yours to wire and yours to keep.
Yes, if you design those branches, and most teams do. A typical flow confirms the booking on the call, offers a reschedule path when the caller hesitates, and uses the same custom tools to change or cancel the appointment in your system. The branches and the logic live in your flow, not in a vendor template.
Run reminders as outbound calls restricted to calling windows by day, time, and timezone. When a reminder hits a busy line, no answer, or voicemail, PeachDesk retries automatically with per-reason controls, so a missed reminder gets another attempt instead of becoming a no-show. Every reminder is a call you designed, on economics you control.
The Pay As You Go platform charge is $59/month, and the Bibha Plan meters minutes at $0.06/minute, as low as $0.03/minute at volume. Bring your own provider keys (BYOK) and your inference cost is your own agreement with your providers. Self-host and route stages to Local mode on your GPUs and there is no per-minute provider charge on those stages; you pay for GPU capacity.
Bring your booking scenarios to a demo. We will map them to a flow you own, on economics you control.