Short walkthroughs that turn the platform into your operations team: automated pipelines, instant follow-ups, AI-handled admin. One video, one less thing to do manually.
Wire TrustPager's scheduling API into your voice agent so callers can check availability and book a time without any human involvement.
TrustPager's scheduling system can be wired directly into your voice agent. When a caller asks to book a time, the agent checks live availability and locks in the booking — without any human in the loop.
Your voice agent uses two tools from the TrustPager Scheduling API:
The agent asks the caller for their preferred time, shows them the options, and books the one they choose. The booking lands in TrustPager, syncs to the host's Google Calendar, and fires a confirmation email to the caller automatically.
You need a TrustPager API key with scheduling permissions. Generate one at https://app.trustpager.com/settings/api and add it to your agent's tool headers as X-API-Key.
Make sure the event type you want the agent to book is published and has at least one user assigned to it — the API only returns slots for published event types with a host.
Your tool should POST to the scheduling endpoint with the event type ID and the caller's timezone (if known). The response looks like this:
Offering: Discovery Call (30 min)
Host: Sarah Chen
Description: A quick call to understand your goals.
Monday 04/28: 9:00 AM [slot:2026-04-28 09:00], 9:30 AM [slot:2026-04-28 09:30], 10:30 AM [slot:2026-04-28 10:30] (+2 more)
Tuesday 04/29: 2:00 PM [slot:2026-04-29 14:00], 3:30 PM [slot:2026-04-29 15:30]
To book, pass the exact slot value (e.g. slot:"2026-04-28 09:00") with the caller's name and email.
The agent reads the slot options to the caller and notes down which one they choose. The [slot:...] values are what gets passed to the booking step — the agent should treat these as opaque identifiers, not display them to the caller.
Once the caller picks a time, the agent calls the booking tool with the slot value, the caller's name, and their email address. On success, the response looks like this:
Booked! John Smith's Discovery Call (30 min) is confirmed for Monday, 28 April 2026 at 9:00 AM, ending at 9:30 AM. A confirmation has been sent to john@example.com.
Host: Sarah Chen
Description: A quick call to understand your goals.
Video link: https://meet.google.com/xxx-yyyy-zzz
Booking ID: 7f3e9c42-...
The agent reads back the confirmed time to the caller and lets them know the confirmation is on its way. If the event type is a video meeting, the Google Meet link is included in the confirmation email sent to the caller.
In your agent's tool configuration:
POST, point it at your TrustPager scheduling endpoint, and include your API key in the headers. The event type ID is a fixed parameter — hardcode it per agent.slot (the exact value from the availability response), name, and email.Tool arguments are passed inside body.args — make sure your endpoint reads from there, not the request body root.
TrustPager converts slot times to the caller's local timezone automatically when you pass visitor_timezone in the request. If the caller's timezone isn't known up front, the agent can ask for their state and TrustPager will resolve it — Australian state names are supported (e.g. "Western Australia" maps to Australia/Perth).
If no timezone is passed, slots are returned in the host's timezone.
Tip: Test your agent by calling it yourself before going live. Check that slot times are read in natural language ("Monday the 28th at 9 AM" not "2026-04-28 09:00"), the confirmation is clear, and the booking shows up in TrustPager immediately after the call.
Talk to Evie right now, or book a real human for a deeper walkthrough. Whichever feels right.
Hear her in 10 seconds.

60 minutes with a real human · Google Meet · Free.