Use Cases

Four common patterns that combine the API, inbound webhooks and outbound events, plus the events each one relies on.

Showing instructions for Xebit VoiceCloud.Showing instructions for Xebit VoiceKit, on your own infrastructure. Switch with the selector at the top. Updated 22 October 2026.

Most integrations combine three pieces: API requests to start or change things, inbound webhooks for tools that can only send a POST, and outbound events that report back. These four patterns show how they fit together.

1. Automated appointment confirmation

Keeps show rates high for service businesses without front desk staff ringing round.

How it works

  1. Trigger: a customer books a slot on your website or app.
  2. Schedule: your backend asks Xebit to place a call 24 hours before the appointment.
  3. Conversation: the agent calls: "Hi Alex, I'm confirming your dental appointment tomorrow at 10 AM. Will you be coming?"
  4. Closing the loop: when the customer says yes, Xebit sends a call.completed event. Your system reads the outcome and updates the appointment with PATCH /v1/appointments/{appointment_id}.

Operations used

  • POST /v1/calls (API)
  • call.completed (outbound webhook)
  • PATCH /v1/appointments/{appointment_id} (API)

2. Instant lead qualification

Calls a new lead within seconds of a form being submitted.

How it works

  1. Form submission: a visitor fills in a "Get a quote" form on your site or in your CRM.
  2. Inbound trigger: the form handler or your automation tool posts to your inbound webhook URL and the call starts immediately.
  3. Qualification: the agent asks the qualifying questions, such as budget and timeline.
  4. CRM sync: when the call ends, Xebit sends the summary and sentiment in an outbound webhook.
  5. Action: your CRM tags the lead as high intent and alerts the sales team.

Operations used

  • POST /v1/hooks/{YOUR_SECRET_TOKEN} with action: call.create (inbound webhook)
  • call.completed (outcome data)

3. Payment reminders that stop themselves

Automates collections without ever calling someone who has just paid.

How it works

  1. Overdue: your billing system spots an invoice that is 7 days past due.
  2. Schedule: it asks Xebit to place a reminder call.
  3. Early payment: ten minutes before the call, the customer pays through your portal.
  4. Cancellation: your billing system immediately posts a call.cancel action to your inbound webhook.
  5. Outcome: Xebit finds the pending call_id and cancels it, so the customer is not called about a bill they have already settled.

Operations used

  • POST /v1/calls (API)
  • POST /v1/hooks/{YOUR_SECRET_TOKEN} with action: call.cancel (inbound webhook)

4. Real time booking integration

Copies appointments booked by the voice agent straight into your clinic system or CRM.

How it works

  1. Inbound call: a patient rings your clinic's agent and books a General Checkup.
  2. Booking confirmed: the agent creates the appointment in Xebit, which sends an appointment.created webhook.
  3. Your system reacts: your backend takes the appointment object and creates a matching record in your EMR or CRM.
  4. Status sync: when staff mark the appointment complete in the dashboard, an appointment.completed event arrives and you update your record.
  5. Cancellations: if the appointment is cancelled in the dashboard, appointment.cancelled starts your cancellation flow and frees the slot in your own system.

Operations used

  • appointment.created (outbound webhook)
  • appointment.completed (outbound webhook)
  • appointment.cancelled (outbound webhook)
  • GET /v1/appointment-slots/availability (API), to check availability before sending patients elsewhere

Events these patterns rely on

EventCarriesTypical use
call.completedFull transcript and AI summaryUpdate CRM records and customer history.
call.failedError reason (busy, no answer)Reschedule the call or hand the contact to your own follow-up process.
call.disallowedPolicy reasonTell an administrator about balance limits or a call scheduled outside your calling windows.
appointment.createdFull appointment object with appointment_type_nameCreate matching records in your EMR, CRM or calendar.
appointment.updatedUpdated appointment objectSync changes such as doctor or session to other systems.
appointment.cancelledAppointment object with status: "cancelled"Run cancellation flows and free slots in your own system.
appointment.completedAppointment object with status: "completed"Mark visits done and start post visit workflows.
slot.updatedSlot object with new capacity or statusKeep your availability screens in step with calendar window changes.