Provisioning checklist — founder steps
Everything a customer can do alone is already built. The items below need the founder's own credentials, payment, or signature — they cannot be done by the platform itself, and this page does not collect any of them.
Loading live readiness…
In order
- Rotate the leaked keys. The Bland and NVIDIA keys in the public GitHub history must be rotated at the provider and the repo history purged, before any client voice or LLM use. Never reuse the leaked values.
- Provision a phone number (Bland). Buy a dedicated number, paste the voice script from the dashboard, set the inbound webhook. Until then voice stays 503.
- Approve a WhatsApp sender (Twilio). Sender approval + webhook. Until then WhatsApp stays 503.
- Connect a calendar (Google Calendar OAuth). Calendar writes are not implemented yet — this step also needs the calendar-write code, not just a key.
- Collect money (Stripe or manual invoicing). Stripe keys + webhook, or founder manual invoicing for the 50% setup deposit. No deposit is taken by the platform today.
- Sign the contract + set the support channel. A client contract template and one real support channel, reviewed — never invented wording.
- Set the owner token + confirm backups. OWNER_TOKEN gates FAQ/admin writes; the daily DB backup (installed 2026-10-27) must be confirmed running before client data depends on it.