AI Intake Architecture: Voice Agents, Secure Webhooks, CRM and Field Dispatch

Architecture: keep the marketing website separate from the private operations service

Use a web presence and educational guides for discovery, but handle contact records and dispatch in a separate client-approved service. GA4 records opt-in website intent, while the actual CRM and telephony provider maintain accepted records. The Next.js frontend should never store carrier master tokens, raw recordings, payment card data, live webhook secrets or a client’s full dispatch database.

1. Carrier + AI provider: Use approved services such as Twilio and Vapi or Retell AI with clear consent and call-transfer rules.
2. Authenticated middleware: Validate the signed request, tenant, timestamp, schema version and event ID, then enqueue safely with deduplication.
3. CRM and scheduling: Map real contact, opportunity and job fields in GoHighLevel or an authorized ServiceTitan tenant. Never invent a job or pipeline value.
4. Staff notification: Use an approved pager or communications integration; a notification sent is not proof the technician accepted the job.
5. Customer updates: Only send consented status texts backed by actual provider results, not fictitious arrival times or public tracking URLs.

Exact event states prevent phantom dispatches

Safe payment and phone-tokenization boundary

Use a real, merchant-approved payment processor. For phone payments, the Twilio <Pay> documentation describes an isolated DTMF capture and processor connector. It requires PCI-mode and compatible payment configuration. An AI should never solicit a caller’s full card details into its speech transcript or a generic JSON webhook. A secure authorization status is not a settled payment or an instruction to dispatch.

Illustrative pricing from an earlier scoping example included a $189 diagnostic, $497–$997 monthly infrastructure retainer, a $1,500 one-time outbound data-mapping fee and a $50 per-booking bounty. These are not published Mandile SEO prices or approved terms. Each must be agreed in writing, with clear service scope, financial approval, acceptance criteria, disputes and refunds.

Consent, outbound calls and referrals

Existing customers are not automatically eligible for AI-voice reactivation calls. Check the specific contact’s permissions, DNC rules, applicable federal and state requirements, hours and opt-outs before any automated call. Do not assert that annual maintenance is required to preserve all HVAC warranties; check the manufacturer’s actual terms. For referral rewards such as illustrative $25/$20 credits, provide a shareable invitation so the friend opts in rather than automatically calling a number supplied by someone else.

Holiday coverage and first-week QA

Before holidays, verify the schedule, primary and backup on-call contacts, approved diagnostic fee, dangerous-emergency diversion and a real carrier failover. During the first 72 hours, review call start/answer data, recording permission, duplicate CRM records, staff acknowledgment, webhook error rates, processor statuses and unnecessary PII in logs. On days 4–7, verify address parsing, tenant field mappings, retry idempotency and fallback behavior. A proposed 1.2-second voice target or 15-second SMS target isn't a measured promise.

If service is unavailable, the automated response should disclose uncertainty: “Your request was received, but a technician and arrival time have not yet been confirmed.” Never tell a panicked homeowner that a truck is heading toward them when no dispatcher accepted the job.

Weekly revenue and lead integrity

Build the weekly summary from actual GSC visibility, consented GA4 service CTA clicks, accepted Reach/CRM entries, acknowledged dispatches, confirmed appointments and paid invoices. Compare similar cohorts and document consent-denied gaps. A sample $16,000 holiday success story, 76% call abandonment figure, 940ms latency or 100% matching claim is hypothetical unless a client approves an evidence-backed case study.

For detailed discussion of the measurement funnel, read Clean Conversion Tracking for Local Businesses. The contractor after-hours guide explains the business workflow and customer-facing escalation process.

Free intake reference files

The implementation architecture and owner review checklist are available without logging in: download the sanitized intake architecture (JSON) and download the client onboarding checklist (text). These resources intentionally contain no live endpoints, account secrets, client data or payment credentials. They describe how to scope a safe integration; they do not activate one.

Vendor access, onboarding and project ownership

A client should delegate the smallest appropriate access to actual Twilio, CRM, payment and field-service accounts. Do not share master passwords or assume a “standard API key” is automatically limited to phone provisioning. Validate current provider scopes, keep secrets in an approved vault, rotate credentials and enable audit logs. Contracts should define who owns the phone number, CRM data, automation configuration and source, which third-party products are licensed, what support is covered, and how a customer can export their data at termination.

All technical stacks listed here are examples; Mandile SEO is not claiming present partner status with Twilio, GoHighLevel, Vapi, Retell AI or ServiceTitan. No live client deployment, payment capture, booked technician, holiday revenue or outbound campaign is represented by these guides.