Run seed-client.js to create their account

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

💡 Change core to growth or pro based on their tier. Pick a strong PIN — 8+ chars.

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

💡 vonage_number is the DB column name — it holds their Telnyx number. forward_phone = the roofer's real cell that calls get forwarded to.

Verify the client appears in Admin → Onboarding tab

Switch to the Onboarding tab above and confirm the account row shows as Active. If not, 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:

Import the ResponsePro — Outbound v4 (Telnyx) blueprint

In Make.com, create a new scenario and import the blueprint JSON. This handles the lead→SMS flow for web form submissions.

Set Client ID in the ⚙️ SET CLIENT ID HERE module

Replace YOUR_CLIENT_ID_HERE with the exact client_id you created in Phase 1. Case-sensitive.

Replace all YOUR_API_SECRET_HERE placeholders

Every HTTP module that hits the ResponsePro API needs your API_SECRET in the Authorization header as a Bearer token. There are usually 3–4 of these.

Set YOUR_TELNYX_NUMBER_HERE in the SMS send module

This is the Telnyx number assigned to this client — format: +1XXXXXXXXXX.

Configure the webhook trigger URL

The scenario's webhook URL goes into the client's website contact form as the form submission endpoint. Copy it from Make.com and paste it into their form's action URL or Zapier/webhook integration.

Map the form fields in the webhook module

Match the incoming form field names (name, phone, email, service, etc.) to the variables the scenario expects. Test with a real form submission to confirm mapping.

Customize the SMS message text

Personalize with their business name. Message must include "Reply STOP to opt out." Keep it under 160 chars for a single SMS segment.

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.

Turn the scenario ON

Toggle the scenario to Active in Make.com. It will now fire on every new form submission automatically.

Import ResponsePro — Inbound SMS (Telnyx) blueprint

Set Client ID in the SET CLIENT ID module

Replace all YOUR_API_SECRET_HERE

Set YOUR_TELNYX_NUMBER_HERE in the opt-out confirmation SMS module

Get the webhook URL from this scenario

You'll need it for the next step. Copy it from Make.com → the webhook trigger module.

Set inbound webhook in Telnyx Messaging Profile

Telnyx Portal → Messaging → Messaging Profiles → find their profile → set the Inbound Webhook URL to the Make.com URL from the step above.

Set inbound webhook in Telnyx for their number

Telnyx Portal → Numbers → their number → Edit → set Messaging Webhook URL to the Make.com URL from the step above. Method: POST.

Test opt-out and opt-in flows

Text STOP from your phone to their Telnyx number. Confirm you get the unsubscribe confirmation SMS and the row appears in opted_out_phones in Supabase. Then text START — confirm the row is deleted from opted_out_phones and a row appears in opt_in_events.

Turn inbound scenario ON

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 both are set:

• MAKE_MISSED_CALL_WEBHOOK — your Scenario 1 Make webhook URL
• TELNYX_WEBHOOK_PUBLIC_KEY — your Ed25519 public key from Telnyx Portal → API Keys → Webhooks. Required — server rejects all voice webhooks without this.

💡 These are one-time setup values — same for all clients.

Import ResponsePro — Outbound v4 (Telnyx) as the missed call scenario into Make.com

Create new scenario → Import Blueprint. Set Client ID in the SET CLIENT ID module. Replace all YOUR_API_SECRET_HERE in HTTP modules. Set YOUR_TELNYX_NUMBER_HERE to their Telnyx number. Set YOUR_BUSINESS_PHONE_HERE to the roofer's cell for the business alert SMS.

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. Turn the Make scenario ON.

Import ResponsePro — Follow-up Sequences (Telnyx) blueprint into Make.com

Create new scenario → Import Blueprint. This scenario runs on a 15-minute schedule and sends follow-up messages to leads who haven't replied.

Set Client ID in Module 2 (⚙️ SET CLIENT ID HERE)

Replace YOUR_CLIENT_ID_HERE with their client ID — same as outbound and inbound.

Replace all YOUR_API_SECRET_HERE

Same API secret as all other scenarios. Hits /api/follow-ups/due, /api/follow-ups/:id/advance, and /api/follow-ups/:id/complete.

Set YOUR_TELNYX_NUMBER_HERE in the SMS send module

Same Telnyx number used in outbound and inbound for this client.

Confirm the schedule is set to every 15 minutes

The trigger module should be a scheduled webhook firing every 15 minutes. Verify the interval in Make.com — do not set it longer or follow-up timing will drift from the expected 1hr / 24hr / 72hr / 7-day cadence.

Test follow-up sequence end-to-end

Trigger a test lead through outbound. Confirm a row appears in follow_up_queue in Supabase. After 1 hour, run the follow-up scenario manually (Run once) and verify the SMS sends and the step advances. Check that replying STOP stops the sequence.

✅ If step advances and SMS sends — turn scenario ON.

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.