Powered by EZKore governance and orchestration
Integration model

Connected where it matters.
Explicit about what is active.

Integrations are enabled per deployment. The status language below distinguishes the current website foundation, initial operating tools, and governed expansion path.

Current foundationPer deploymentGoverned layer
Current foundation
GitHub + Netlify
Source and web delivery

GitHub is the intended source of truth; Netlify builds and deploys the static national website.

Carrier-dependent
Twilio
Voice and customer-care SMS

Phone and messaging workflows require approved number configuration, carrier registration, and compliant use.

Phase-one operations
Airtable
Operator intake queue

The initial operating model uses a structured queue for review and human follow-through.

Governed layer
EZKore
Intelligence and orchestration

Provides the control model for versions, consent context, audit evidence, security, and managed handoffs.

Per deployment
OpenAI
Conversational processing

AI processing is configured through approved application workflows, prompts, safeguards, and operating boundaries.

Per deployment
Business systems
Calendar, CRM, dispatch, and alerts

Adapters are scoped and verified for the customer’s tools; their availability is not implied by default.

Marketing-email platforms are not part of the default customer-care messaging story. Any promotional communication requires a separate, appropriate consent and compliance basis.
Build the response layer

Bring the tools your team already uses.

We will identify the minimum responsible integration path, define ownership, and confirm what is live before it appears in your workflow.