A potential client fills out your contact form at 11 PM. Someone on your team sees it the next morning, checks the attorney's calendar, sends an email with three time options, and waits for a reply. By then, the lead has already booked with a competitor who had a scheduling link.
Every email thread arranging a first consultation is time an attorney — or a paralegal billing at $150/hr — spends on administration instead of legal work. Intake scheduling is a pure overhead cost that doesn't require human judgment to execute.
Legal platforms that connect clients to attorneys across practice areas have no API-native way to route a 'family law' inquiry to the right attorney's calendar. Most end up building custom matching logic on top of fragile calendar APIs that weren't designed for it.
Your AI intake agent captures lead information and immediately calls the Orita API to find availability and create a booking. The lead gets a confirmation before they close the tab. No follow-up email, no back-and-forth — just a booked consultation.
Pass `provider_username` to route bookings to any attorney in your network — by practice area, location, or availability. One Orita API key manages your entire firm directory. Build the matching logic once, never maintain per-firm integrations.
Register your CRM or case management system as a webhook endpoint. Every confirmed consultation triggers an immediate POST with client details, attorney info, and meeting time. Your pipeline updates automatically — no manual data entry.
Your AI agent routes the lead to the right attorney and creates the booking. The webhook fires instantly to your CRM.
{
"provider_username": "atty-rodriguez",
"event_type_id": "initial-consultation",
"client_name": "James Carter",
"client_email": "james@example.com",
"start_time": "2026-03-10T14:00:00Z",
"notes": "Employment dispute — wrongful termination, 3 years tenure"
}Response includes booking_id, confirmation_url, and attorney details.
Yes. Your routing logic lives in your AI agent or platform code — you decide which provider_username to pass based on practice area, jurisdiction, or load balancing. Orita handles availability checks and booking creation for whichever attorney you select.
Orita handles the scheduling step — the actual booking creation. Your AI agent or intake form handles data collection before calling the API. Pass relevant notes (practice area, case summary) in the `notes` field so the attorney sees them before the call.
PATCH /bookings/:id lets you update the start_time for a booking. The webhook fires again with the updated details so your CRM, calendar sync, and notification system all stay current.
Buffer time is configured at the event type level in Orita. Set a pre/post buffer on your consultation event type, and Orita automatically blocks that time when checking and creating bookings.