Docs
How lead intake, auto-provisioning, and messaging fit together — plus what to expect for carrier (10DLC) timing.
Getting Started
ResponsePro is fully managed — we host SMS, voice, compliance logging, and your dashboard. After you pay, we auto-provision your dedicated number and 10DLC registration. Here's the typical flow:
- Choose a plan and complete the online onboarding form. You will verify your business phone number via SMS code, e-sign your service agreement, and complete Stripe checkout — all in one flow.
- We register your brand and campaign with carriers, order a local number in your state, and email you a unique intake webhook —
https://intake.responsepro.app/{your_client_id}— to paste into lead sources (website, Google LSA, Angi, Thumbtack, etc.). See the webhook integration guide for step-by-step instructions for common platforms. - 10DLC timing: carrier campaign review typically takes several business days. Until approval completes, some messages may be delayed or blocked by carriers — your dashboard shows live provisioning status.
- When a lead hits your webhook, an instant SMS goes out (usually within about a minute) and the follow-up sequence starts. Timing is anchored to when the lead arrived — not when the cron next runs. Core: 1 hour and 25 hours after intake. Pro: adds 97 hours and 265 hours (approx. 4 and 11 days), plus missed-call SMS recovery where included.
- Log in to your dashboard for inbox, analytics, missed-call log, and weekly summaries.
How It Works
When a lead hits your intake URL, a Cloudflare Worker validates the payload — including phone format, request size, and client ID — and forwards it to our API. The API deduplicates, checks opt-out, enforces tier caps, and queues an outbound SMS through Telnyx.
Follow-up timing is per-lead: each step is scheduled relative to when that specific lead came in, not when the cron runs. Every step honors STOP, quiet hours (9 PM–8 AM in the client's local timezone), and cancels automatically if the lead replies or the call connects.
Pass a source field in your webhook payload (website, google_lsa, facebook, etc.) to track which channels produce booked jobs. See the multi-source tracking guide.
Compliance & Opt-Out
All messaging is built around TCPA and carrier requirements. STOP, UNSUBSCRIBE, CANCEL, QUIT, and END keywords trigger an immediate opt-out and a compliance confirmation message. START re-subscribes only if the number was previously opted out. HELP returns your business name and direct phone number.
Opt-outs are logged, respected immediately, and cannot be bypassed by follow-up sequences. Quiet hours (9 PM–8 AM local time) are enforced on every outbound message. Missed-call SMS recovery (Pro) is subject to the same opt-out and quiet-hours rules.
You remain responsible for obtaining proper consent from your leads. Lead capture that opts consumers into recurring marketing SMS must include, next to an unchecked-by-default checkbox, disclosure that giving consent is not a condition of purchase (along with STOP/HELP, message frequency, and msg & data rates). See our SMS Consent guidelines and the webhook integration guide for copy you can adapt.
Phone Verification at Onboarding
During onboarding, we verify your business phone number using a one-time SMS code powered by the Telnyx Verify API. This confirms you own the number before it is provisioned as your sending identity. Codes expire automatically; you can request a new one if needed. The verification step is required before your service agreement is signed or payment is processed.
API Reference
Today: lead intake is a simple HTTPS POST to your per-account webhook on intake.responsepro.app (handled by our Worker + API). There is no public OpenAPI catalog yet.
Roadmap: a documented REST API for partners who want to push leads, pull analytics, or white-label — contact us for the waitlist.