A plumber finishes a job, climbs back in the van, and checks their phone to see 6 missed calls from people who need service. They call back one by one, check their mental schedule, and try to fit everyone in. This is how home service businesses operate — and it costs them jobs every day.
Back-to-back bookings in opposite ends of the city sound efficient on paper. In practice, the technician is always late to the second job. Without buffer time built into the scheduling logic, a plumbing company with 5 technicians runs a chaotic daily dispatch.
A homeowner's pipe bursts on a Sunday evening. They search for an emergency plumber, find your website, and fill out a contact form. They get an autoresponder saying someone will call Monday morning. By Monday, they've already hired the first company that confirmed availability via online booking.
Set buffer time on every event type — 30 minutes for travel, 15 minutes for job wrap-up. Orita blocks that time automatically when checking availability. Your AI dispatcher never schedules a technician for back-to-back jobs across town.
Each technician is a provider in your Orita account. Your platform logic assigns jobs by zone, specialty, or availability — then passes the right `provider_username` to the API. Orita handles the booking. One integration, every technician in your fleet.
Every confirmed booking triggers your webhook instantly. Trigger an SMS confirmation to the homeowner, a job notification to the technician, and a 1-hour reminder before the appointment. Your customer experience runs automatically, 24/7.
Your AI dispatcher finds an available technician and creates the booking. Travel buffer is automatic — no double-booking across town.
{
"provider_username": "tech-sullivan",
"event_type_id": "plumbing-repair",
"homeowner_name": "Robert Kim",
"homeowner_email": "robert@example.com",
"start_time": "2026-08-14T09:00:00Z",
"notes": "Leaking pipe under kitchen sink. 2nd floor apt, unit 4B"
}Job duration (60 min) + travel buffer (30 min) block 90 minutes on the technician's calendar. Next available slot starts at 10:30 AM.
Yes. Set a post-appointment buffer on each event type (e.g., 30 minutes for a standard plumbing job). Orita treats that buffer as unavailable time when checking availability. No back-to-back jobs across town.
Yes. Each technician is a provider in your Orita account. Your dispatch logic assigns zone or job type; Orita handles their individual availability and booking creation. One API key manages your entire field team.
PATCH /bookings/:id lets you reassign or reschedule any booking. Your dispatch system can automatically find the next available technician and update the booking in one API call. The homeowner gets a new confirmation immediately.
Yes. Use the availability endpoint to find the earliest open slot across your technician network. Pass a narrow time window (e.g., next 4 hours) to surface same-day availability. Your AI agent or website can show and book that slot instantly.