Scheduling¶
Intelligent booking intent extraction and response drafting from messages.
| Port | 8107 |
| Container | hai-scheduling |
| Use case | Appointment booking from emails/web forms, scheduling automation |
| Compliance | GDPR, CCPA, SOC 2 |
How it works¶
Submit any incoming message (email, chat, web form) and the system extracts booking intent: what service they want, preferred dates, urgency, contact info, and a draft reply.
API¶
Parse a booking request¶
curl -X POST http://localhost:8107/api/v1/parse \
-H "X-API-Key: hai_your_key" \
-H "Content-Type: application/json" \
-d '{
"message": "Hi, I saw your website and would love to schedule a consultation about AI automation for our dental practice. We have about 15 staff members. Would next Tuesday or Wednesday afternoon work? My email is dr.smith@brightsmiledental.com and you can reach me at 415-555-0123.",
"source": "web_form",
"business_hours": "Mon-Fri 9AM-5PM PT",
"services": ["AI Quick-Start", "Document Search Setup", "FAQ Chatbot"]
}'
Response:
{
"has_booking_intent": true,
"requested_service": "AI Quick-Start (AI automation for dental practice, 15 staff)",
"preferred_dates": ["Next Tuesday afternoon", "Next Wednesday afternoon"],
"preferred_duration": null,
"urgency": "medium",
"contact_name": "Dr. Smith",
"contact_email": "dr.smith@brightsmiledental.com",
"contact_phone": "415-555-0123",
"draft_reply": "Hi Dr. Smith,\n\nThanks for reaching out! AI automation for dental practices is a great fit — we've set up similar systems for healthcare offices.\n\nI have availability next Tuesday at 2 PM or Wednesday at 3 PM PT. Either work for you? It'll be a 30-minute call to understand your workflows and identify the best starting point.\n\nLooking forward to it.\n\nBest,\nNiels",
"notes": "Dental practice, 15 staff. Healthcare sector — may need HIPAA considerations.",
"latency_ms": 1567,
"model": "claude-sonnet-4-20250514"
}
Batch parsing¶
Process up to 25 messages at once:
curl -X POST http://localhost:8107/api/v1/parse/batch \
-H "X-API-Key: hai_your_key" \
-H "Content-Type: application/json" \
-d '{"requests": [...]}'
Integration patterns¶
| Source | How to connect |
|---|---|
| Forward to API via webhook or IMAP polling | |
| Web form | POST form submissions directly to the API |
| Chat | Route chatbot "book appointment" intents to this API |
| Calendar | Use the parsed data to create calendar events via Google/Outlook API |