Onboarding a business — step by step
States in code (Onboarding::STATES): new → phone_verified → calls_connected → sms_pending → sms_live.
Diagram source (Mermaid)
flowchart LR
S[1 Sign up] --> E[2 Confirm email] --> L[3 Listing + phone] --> V[4 Verify phone] --> K[5 Knowledge base] --> C[6 Calls live] --> T[7 Texting<br/>after carrier approval]| # | Step | How | Status |
|---|---|---|---|
| 1 | Sign up | /signup, choose Business, username = the 10-digit business number | Built |
| 2 | Confirm email | Click the 24-hour link sent by Resend | Built |
| 3 | Listing + phone number | Create/edit the listing on the site or with the Best Deal On Bot extension (device approval) | Built |
| 4 | Verify the phone | Verify by call (the bot calls the listing's own number with a 6-digit code) or Twilio Verify call; an admin can verify manually | Built (admin path is manual) |
| 5 | Knowledge base | Best Deal On writes the business's KB Markdown and tenant file | Manual (done by the team/Coder) |
| 6 | Calls live | Number routed to callbots-bdo, tenant deployed after John's approval | Manual; per-business call routing in the product is planned |
| 7 | Texting | Only after that business's one-time carrier (A2P 10DLC brand + campaign) approval, usually about 4–24 hours; then a person turns sms_enabled on | Manual, not yet enabled for any business |
Owners follow progress on /account (status page with a time estimate) and /account/phone-bot.