Customization and AI Behavior
Business rules (service areas, advance-notice windows, call-type eligibility, pricing) can be delivered two ways: configured directly in Avoca during onboarding — how current production integrations work — or exposed via API using shapes like the reference designs below for rules that change frequently. The endpoints on this page are a recommended specification for your API, not existing Avoca endpoints.
Business Rules API Options
Eligibility & Validation RulesTraining & Fine-Tuning Data Requirements
Historical Data for AI Training – Request anonymized historical data: Booking Patternsdate_range_start, date_range_end, anonymized=truePurpose: Understand booking patterns, peak times, conversion factors
Data needed: timestamps, service types, booking lead times, completion rates, cancellation reasons, interaction counts before booking Conversation Transcripts (if available) – Anonymized call transcripts, common questions and objections, successful booking flows, cancellation/modification patterns. Service Performance Metrics – Popular services, seasonal demand, geographic distribution, pricing sensitivity. Data Privacy Commitments
- All training data fully anonymized (no PII)
- Data used solely for AI improvement
- Retention limited to training purposes
- Compliance with GDPR and CCPA processing requirements
- Data processing agreement (DPA) established before transfer
Branding & Content APIs
Dynamic Script Content- Scripts and content cached with 24-hour TTL
- Webhook notifications (
content.updated) for immediate updates - Version numbers enable cache validation