Cloudflare Core
Pages/Hono runtime with D1, KV, and the call-handling runtime configured in wrangler.jsonc.
What is connected today, what is still a stub, and which outside services each call or message path depends on.
Twilio, Cloudflare Email, and Hono API routes feed the inbox.
Demo events, service windows, rate cards, jobs, inquiries, call rules, and business notes live in D1.
Staff-approved knowledge and deterministic tools handle pricing, availability, and booking decisions.
These integrations are wired into the current demo flow.
Pages/Hono runtime with D1, KV, and the call-handling runtime configured in wrangler.jsonc.
Primary job-intake path. It uses business notes, then calls server-side tools for availability, pricing, job holds, payment stubs, and escalation.
Staff can upload PDFs or paste policies, store searchable notes in D1, and use the right snippet across web, email, SMS, and voice.
Inbound business email is parsed by the email worker, stored in D1, processed through the same intake path, and replied to by email.
The purchased demo number handles inbound SMS and voice webhooks, verifies Twilio signatures, and records the full conversation in the dashboard.
Voice generation is wired for the call handling preview and Twilio audio playback when the reply is suitable for generated speech.
Dashboard authentication uses Google OAuth and signed JWT cookies when the production secrets are present.
Secondary paths that are working, but not the primary demo route.
Outbound email fallback for Lost Docket replies when Cloudflare Email is unavailable or deliberately bypassed.
The codebase has stubs or planned surfaces, but these are not production-grade integrations yet.
Future business-management sync for confirmed jobs, customer profiles, and service window inventory.
Future payment-link generation for deposits, callout fees, and job balance collection.
Future signed service window agreements with generated PDFs, object storage, and e-signature delivery.
Future staff alerts when a job needs a human handoff or a high-value booking needs approval.
Future observability and controls for call-handling requests once the gateway is actually bound and used.
A quick check of the deployed Cloudflare and vendor surface.