statement: VAPI serves as the SIP Gateway layer between telephony carriers (Telnyx) and voice AI platforms (VoiceAIWrapper), abstracting SIP complexity.

source: Architecture Pattern


statement: All VAPI assistants must use 'assistant-speaks-first' mode for professional inbound call handling to establish rapport immediately.

source: UX Best Practice


statement: Deepgram Nova-3 with en-AU language code is the mandatory transcriber for Australian voice agents to ensure accent accuracy.

source: Regional Optimization


statement: Emergency triage must always trigger the 'escalate_emergency' function tool before any other booking actions when keywords like 'flooding', 'burst', 'fire' are detected.

source: Safety Protocol


statement: VAPI function tools (check_availability, book_appointment, escalate_emergency) must map directly to GHL calendar and CRM endpoints for real-time sync.

source: Integration Requirement


statement: Industry-specific templates (trades, medical, legal, generic) must be used to ensure compliance and appropriate conversation flow for each vertical.

source: Compliance Standard


statement: VAPI SIP integration requires IP whitelisting (44.229.228.186, 44.238.177.138) and G.722 codec for HD audio quality.

source: Infrastructure Requirement


statement: silenceTimeoutSeconds should be set to 1.5-2.0 seconds to balance responsiveness with allowing customers to complete their thoughts.

source: Conversation Design


statement: backgroundDenoisingEnabled must be true for all production agents to handle mobile callers and noisy environments.

source: Audio Quality


statement: Agent names in VAPI are limited to 40 characters - use pattern '{BusinessName} - RAI' to maintain consistency.

source: Platform Constraint