Run seed-client.js to create their account

Open PowerShell, navigate to your backend folder, and run:

💡 Args used here: tier, role=client, timezone, telnyx_number, forward_phone, active.

Set the client's follow-up timezone (used for 8am-9pm local quiet hours):

Then set their Telnyx number and forwarding phone in the DB:

💡 telnyx_number receives calls/SMS. forward_phone is the roofer's real cell for call forwarding.

💡 Replace America/New_York with the value selected above (IANA timezone format).

Verify the client appears in Admin → Onboarding (or Ops directory)

Onboarding tab: confirm the submission row. Ops → Client directory: confirm the client_id exists and is active. If missing, the seed script may have failed — check your DATABASE_URL.

Test their login URL

Open this in an incognito window — it should auto-login and show their (empty) dashboard:

Get the Worker intake URL for this client

The intake endpoint is: https://responsepro-intake.bluediamondcart.workers.dev/{CLIENT_ID}. Replace {CLIENT_ID} with the exact client_id from Phase 1.

Set the Worker URL as the form action on their website

Point their website contact form's action URL to the Worker intake endpoint. The Worker accepts both JSON and form-urlencoded POST requests. Fields: name, phone, email, service, source.

Verify the Worker env vars are set in Cloudflare

Cloudflare Dashboard → Workers → responsepro-intake → Settings → Variables. Confirm: API_BASE (Render URL), API_SECRET (Bearer token), TELNYX_API_KEY, TELNYX_MESSAGING_PROFILE_ID.

Run a test submission end-to-end

Submit a test form with your own phone number. Confirm: (1) SMS arrives within 60 seconds, (2) a row appears in the dashboard Lead Analytics tab, (3) no errors in the Error Log tab.

Confirm the intake is live

The Worker runs 24/7 on Cloudflare's edge — no scenario to toggle. Once the form URL is set, every submission is automatically processed: normalized, deduped, SMS sent, owner alerted, follow-up queued.

Set inbound webhook in Telnyx Messaging Profile

Telnyx Portal → Messaging → Messaging Profiles → find their profile → set the Inbound Webhook URL to: https://responsepro-api.onrender.com/api/sms/inbound (POST)

Set inbound webhook in Telnyx for their number

Telnyx Portal → Numbers → their number → Edit → set Messaging Webhook URL to the same URL: https://responsepro-api.onrender.com/api/sms/inbound. Method: POST.

Test opt-out and opt-in flows

Text STOP from your phone to their Telnyx number. Confirm the row appears in opted_out_phones and no further automated outbound SMS is sent to that number. Then text START — confirm the row is removed from opted_out_phones and a row appears in opt_in_events.

Test HELP reply

Text HELP from your phone to their Telnyx number. Confirm you receive the help response with support contact info. The server handles STOP/START/HELP automatically — no external scenario needed.

Create a Telnyx Call Control Application

Telnyx Portal → Voice → Call Control → Create Application. Set:

💡 One Call Control Application covers all clients — you don't need a new one per client.

Link their Telnyx number to the Call Control Application

Telnyx Portal → Numbers → find their number → Edit → assign it to the Call Control Application you just created. This tells Telnyx to hit your webhook URL when that number receives a call.

Confirm env vars are set in Render

Render Dashboard → ResponsePro API → Environment → confirm this is set:

• TELNYX_WEBHOOK_PUBLIC_KEY — your Ed25519 public key from Telnyx Portal → API Keys → Webhooks. Required — server rejects all voice webhooks without this.

💡 One-time setup value — same for all clients. The server handles missed call SMS directly via /api/voice/event (no external scenario needed).

Review the missed call SMS message text

Personalize with the client's business name. Must include "Reply STOP to opt out." Example: "Hi, you just called [Business Name] and we missed you. Still need a roofing estimate? Reply here and we'll get right back to you. Reply STOP to opt out."

Test by calling the Telnyx number and not answering

Call their Telnyx number from your cell. Let it ring out — don't answer. Wait ~30 seconds then check: (1) Missed Calls tab shows a new row, (2) SMS arrives on your phone, (3) error log is clean.

✅ If all three pass — voice is live. The missed call SMS flow is fully server-side, no external scenario to enable.

Verify pg_cron job is active in Supabase

Supabase Dashboard → SQL Editor → run: SELECT * FROM cron.job; Confirm there is a job that calls POST /api/internal/follow-ups/process every 5 minutes. This replaces the old Make.com follow-up scenario entirely.

Confirm the follow-up cadence

The 4-step cadence is: 1 hour, 24 hours, 72 hours, 7 days after initial contact. Sequence stops on reply, opt-out (STOP), or all 4 steps sent. No per-client configuration needed — the cadence is the same for all clients.

Test follow-up sequence end-to-end

Trigger a test lead through the Worker intake. Confirm a row appears in follow_up_queue with step = 1 and a valid next_send_at. The first follow-up is scheduled ~1 hour after intake (not immediate). After send, confirm it advances/reschedules to the next step. Verify replying STOP cancels future sends.

✅ If queue rows schedule correctly and steps advance after sends, follow-ups are live. pg_cron handles execution automatically.

Send the client their dashboard login URL

💡 Send via text or email. Tell them to bookmark it — that link logs them in automatically.

Walk them through the dashboard (5 min)

Show them: Lead Analytics KPIs, the weekly chart, Missed Calls tab, and how to read response times. Keep it simple — they care about leads contacted and response speed.

Confirm billing is set up

Make sure they've paid the setup fee (if applicable) and their first month is collected. Don't leave this step until billing is confirmed.

Update onboarding status to Active

Onboarding tab → find their row → click ✓ Active. This is your internal record that they're fully live.

Schedule 7-day check-in

Set a reminder to follow up in 7 days. Ask: Are they getting SMS alerts? Any issues? This is also your shot to get a testimonial early.

Give your hire their own dashboard login

They only see Prospects, Call Script, Objections, and Pipeline—so they can work leads without touching customer analytics or your admin tools.

Run in PowerShell from your backend folder (same as seeding a client; role is partner in the DB):

One login per rep

Each salesperson should have their own ID and PIN so pipeline ownership and activity stay clear.

Point leads at this rep

In the database, each prospect row belongs to a rep by ID. Assign the territories or lists this hire should work so their Prospects tab fills in.

Confirm they have enough accounts to call

Before go-live, sanity-check counts so the rep isn’t staring at an empty list.

Send them the login link

They sign in with the same dashboard URL you use—only the tabs change based on their role. Replace REP_PIN with their real PIN when you share (use a secure channel).

Watch them click through once

Have them open Prospects, move a stage, skim Call Script and Objections, and check Pipeline. Fix access issues before they’re solo on the phones.

Set expectations

Confirm how you want notes entered, stages used, and follow-ups logged. This CRM is internal—your process, your rules.