Docs

Production Launch Guide

Use this page as the quick runbook. For full variable list, keep `.env.example`, `README.md`, and `VERCEL_LAUNCH_CHECKLIST.md` aligned in your repo.

Configure core environment

Set NEXT_PUBLIC_APP_URL, STORE_DRIVER=postgres, and DATABASE_URL.

Enable MANAGED_MODE=true to hide provider setup from customers.

Add APP_ACCESS_USERNAME and APP_ACCESS_PASSWORD for workspace protection.

Connect telephony and voice

Set TELEPHONY_ACCOUNT_SID, TELEPHONY_AUTH_TOKEN, and TELEPHONY_PHONE_NUMBER.

Set VOICE_ENGINE_API_KEY for natural voice quality.

Add telephony webhooks: /api/calls/answer, /api/calls/status, /api/calls/recording-complete.

Enable billing + AI

Set PAYPAL_MODE, PAYPAL_CLIENT_ID, PAYPAL_CLIENT_SECRET.

Caller numbers are purchased per caller identity; credit packs are 30/60/90/140/200.

Set GOOGLE_AI_API_KEY (or MANAGED_GOOGLE_AI_API_KEY) and optional GOOGLE_AI_MODEL.

Set CRON_SECRET to secure scheduled campaign dispatch endpoint.

Connect lead sources

Open Dashboard -> Sources and copy your webhook URL.

In Zapier, send Facebook Lead Ads (or any form source) to /api/integrations/zapier/lead.

Add Google Drive/Sheet CSV URL and run Sync Now, then load inbox leads into Call Center.

Push database and deploy

Run npm run db:push once against production DATABASE_URL.

Deploy to your production environment with npm run build.

System cron in vercel.json auto-runs /api/cron/dispatch-scheduled every minute.

Operational security baseline

Keep all provider secrets only in secure environment variables.

Never expose API keys in frontend code or customer settings screens.

Rotate provider and AI keys immediately if leaked.