Docs

From form submit to first text

1. Your lead source sends a JSON webhook to https://intake.responsepro.app/{your_client_id}.
2. Our intake layer checks the request format, phone number, and payload size before forwarding anything.
3. ResponsePro checks whether this phone already contacted you in the last 24 hours (duplicate leads are skipped).
4. We check whether the person previously texted STOP (opted out). If so, no SMS is sent.
5. If the lead passes all checks, the instant reply goes out through your dedicated texting number.
6. We record the lead in your dashboard, email you an owner alert, and queue the follow-up sequence.

Your website form gets a fast success response. It does not wait on carrier delivery time.

Follow-up timing

Each follow-up is scheduled from the moment that lead first arrived. A lead that comes in at 3:00 PM gets the one-hour follow-up at 4:00 PM, even if our batch processor runs at 3:07 PM.

Every automated message ends with standard carrier language: message and data rates may apply, and reply STOP to opt out.

When follow-ups stop

A sequence cancels automatically if any of these happen:

• The lead replies by text (or you reply from the dashboard before the next step)
• The lead texts STOP or another opt-out keyword
• Your plan only includes two follow-ups and both have already sent (Core)

Quiet hours

We do not send outbound texts between 9:00 PM and 8:00 AM in your local timezone. If a follow-up would land in that window, it moves to 8:00 AM the next day. Your timezone comes from onboarding, or from your business state if you left it blank.

Track leads by source

Include a source field in your webhook JSON so your dashboard shows which channels produce booked jobs. Common values: website, google_lsa, facebook, angi. Unknown values are stored as generic. See the multi-source tracking guide.

Missed-call recovery (Core and Pro)

When someone calls your business line and the call is not answered, ResponsePro can send an automated SMS text-back from your dedicated number on Core and Pro where missed-call recovery is configured. The same opt-out and quiet-hour rules apply. You set up call forwarding so missed calls reach our voice routing. See the call forwarding guide.

On Pro, Voice AI live call answering is rolling out — it may answer inbound missed calls before or alongside the text-back path when enabled.

Voice AI (Pro)

On the Pro plan, an AI assistant can answer inbound calls, ask qualifying questions, and log call outcomes in your dashboard. Call audio and transcripts may be processed to generate summaries and insights. The assistant can transfer the caller or end the call when appropriate — it does not book or schedule appointments.

You are responsible for any recording disclosure required by your state (one-party or two-party consent laws). Voice AI is not an emergency dispatch system. Dashboard call-insight views are rolling out as the feature ships; your signed Pro agreement describes the full scope.

What ResponsePro handles for you

• 10DLC brand and campaign registration with carriers — properly registered messaging so your texts are less likely to be filtered than unregistered DIY setups
• STOP, START, and HELP keyword handling on inbound texts
• Opt-out list that blocks instant replies, follow-ups, missed-call texts, and manual dashboard sends
• Quiet hours (9:00 PM to 8:00 AM local) on all outbound messages
• Compliance event logging for opt-ins, opt-outs, and suppressed sends

Opt-out keywords

If someone texts STOP, UNSUBSCRIBE, CANCEL, QUIT, or END, we immediately flag their number as opted out and send a short confirmation. They will not receive further automated messages from your ResponsePro number. You can still reach them by phone directly.

If they later text START or UNSTOP, we only re-subscribe them if they were previously opted out. A welcome-back message confirms they are opted in again.

HELP or INFO returns your business name and direct phone number. HELP replies are limited to once per 24 hours per number to prevent abuse.

Your consent responsibilities

You are responsible for getting proper consent before marketing texts go out. For recurring automated marketing SMS, your lead capture form must include, next to an unchecked-by-default checkbox:

• Clear language that the person agrees to receive automated texts from your business
• Giving consent is not a condition of purchase
• Message frequency disclosure, STOP and HELP instructions, and message and data rates may apply

See our SMS Consent guidelines and the webhook integration guide for copy you can adapt on your website.

What gets logged

Every opt-out, opt-in, suppressed send, and compliance confirmation is written to an audit log tied to your account. Your dashboard error log surfaces delivery issues and rate-limit events without exposing customer phone numbers in plain text.

Blocking a number from the dashboard

You can block a number from your dashboard. That flags the contact as opted out in our system so no further automated texts go out. This follows the same enforcement path as a STOP keyword.

How the verification code works

1. Enter your business phone number on the onboarding form.
2. Click Send code. A one-time code arrives by SMS within a few seconds.
3. Enter the code (4 to 8 digits) and click Verify code.
4. Once verified, the rest of the form unlocks for signature and payment.

Codes expire on their own. If yours expires, request a new one. You can try up to three send requests per phone every ten minutes.

Why this step exists

• Confirms the phone on your application belongs to you before we provision a sending identity
• Reduces fraud and wrong-number signups
• Aligns with carrier rules for business messaging registration

This verification is separate from carrier brand review after payment. Sole proprietors may receive an additional one-time code from the carrier during brand registration. If that happens, our team walks you through it.

If verification fails

Double-check that you entered a mobile number that can receive SMS. Landlines and some VoIP numbers cannot get codes. If you still have trouble, email support@responsepro.app from the same address on your application.

What works today

Lead intake is a simple HTTPS POST to your per-account URL:

POST https://intake.responsepro.app/{your_client_id}

Send JSON with at least a phone number. Optional fields include name, email, message, and source. Our intake layer validates the payload and forwards it to ResponsePro. There is no public OpenAPI document yet.

For field names, examples, and form wiring, see the webhook integration guide.

Coming soon

We are building a documented REST API for partners who want to push leads, pull analytics, or white-label ResponsePro. Contact us to join the waitlist.