PRODUCT OVERVIEW

Speed-to-Lead AI User Guide

Product: v7.7.0 • Guide: v1.5

Speed-to-Lead helps service businesses respond to incoming leads quickly, continue the conversation by SMS, identify booking intent, and let a human take over when needed.

Remember: the AI understands what the lead means. Speed-to-Lead decides what the system is allowed to do.

1. Customer journey

A lead comes from a hosted form, embedded form, existing website form, API, ad, CRM, or another connected source.
The lead is saved in the tenant's database.
If SMS consent exists, the first-touch workflow is queued.
The customer replies by text.
The AI classifies the request and prepares an approved response.
High-intent leads receive the booking path; exceptions can be handed to a human.
The operator console records conversation, stage, handoff and booking state.

2. Business setup

Sign in with your business account, then open /setup. Configure the business name, timezone, booking URL, industry template, services, SMS consent language, first SMS template, approved FAQs, qualification questions, pricing policy and human-handoff rules.

3. Connect a website or use Speed-to-Lead by itself

Go to Setup → Integrations → Website → Connect Website. Four connection methods are available.

Use Speed-to-Lead only

Share the hosted customer lead page. No website is required.

Embed on my website

Copy the iframe code into an existing website page.

Connect my existing form

Keep the current website form and POST its fields to the private Speed-to-Lead webhook URL. Map Name, Phone, Email, Service and SMS Consent.

Developer / API

POST JSON from a custom website, CRM, Make or Zapier to the generated endpoint.

Use Test Connection to create a real test lead in the local console. If the test lead has SMS consent, first-touch automation is queued. Without consent, the lead is captured but automated texting does not begin.

Security: treat the private webhook URL like a password. If it is exposed, use Rotate webhook URL.

4. Operator console

Open /console. The dashboard shows lead volume, contacted leads, booking progress, response speed, automation health and conversations that need attention. Open a lead to see the SMS thread, intent, confidence, stage, activity timeline and handoff state.

Lead stages

NEW means captured; CONTACTED means an outbound message was sent; RESPONDED means the customer replied; QUALIFYING/QUALIFIED track discovery; HIGH_INTENT signals strong purchase or booking intent; BOOKING_LINK_SENT means the approved booking path was sent; BOOKED requires confirmed calendar reconciliation; HUMAN_HANDOFF requires staff; OPT_OUT/CLOSED suppresses normal automation.

5. AI and human takeover

AI may only use approved business facts, FAQs and current workflow state. It must not invent prices, availability, guarantees or policies. Use Take over when a person should reply. While in human mode, AI outbound messages are blocked. Use Return to AI to resume automation.

6. SMS consent, booking, and opt-out

Automated SMS should only begin when the lead has appropriate consent. Connected websites can still capture a lead without consent, but the first-touch SMS is not queued. STOP and other supported opt-out signals close automated messaging for that lead.

Booking: AI may detect booking intent and send the configured booking path, but Speed-to-Lead must not claim an appointment is booked until the real calendar/booking provider confirms it.

7. Support Center

Open /support or use the Support Center link in Setup or the Operator Console. Submit the issue category, priority, subject and description. Speed-to-Lead stores the application version automatically, returns an immediate support analysis, and places the ticket in the product owner support inbox.

When OPENAI_API_KEY is configured, the first response is generated by the support AI. If the AI provider is unavailable, the ticket is still saved and the interface clearly labels the local fallback response instead of pretending AI is connected.

Product owner: sign in with a platform-administrator account and open /support-admin to review the issue, AI suspected cause, recommended fix, conversation history, SLA, and confirmed resolution.

Security: never paste passwords, bearer tokens, API keys, Twilio auth tokens, or private webhook URLs into a support ticket.

AI Content Studio

Open /content-studio to turn safe, approved application data into a video script, storyboard, preview, and provider handoff package. Supported content includes personalized prospect demos, weekly results, approved case studies, onboarding, support how-to content, social media, and feature announcements.

Safety rule: the Content Studio does not use private lead-level names, phone numbers, email addresses, private SMS conversations, or credentials as marketing-video inputs. Weekly videos use aggregate metrics. Case-study videos require a customer-approved case study. Prospect videos use the saved prospect demo workspace.

The local build supports a provider-ready JSON export and a Lumen5-oriented handoff package. These let you review the exact script, scenes, metrics and brand instructions before using a video generator. A generic automated video-provider webhook can be enabled later without changing the Content Studio workflow.

8. Troubleshooting

Problem	Check
Website test fails	Confirm phone format, field mappings and that the website connection is active.
Lead appears but no SMS	Check SMS consent first, then integration status and workflow delivery.
Existing form sends blanks	Verify the mapped field names exactly match the submitted JSON keys.
Webhook URL leaked	Rotate the connector URL and update the website immediately.
AI stops responding	Confirm the conversation is in AI mode and the lead is not opted out or closed.

8. Billing, onboarding and Go Live

Open /account to manage the plan, billing status, invoices/payment events, usage, team, API keys, onboarding checklist and launch readiness. Local development can simulate payment success/failure. With Stripe test credentials configured, Activate / pay opens Stripe Checkout and Billing portal opens Stripe Customer Portal.

Go-Live gate: Speed-to-Lead requires required business configuration and active billing before marking a workspace LIVE. Production can additionally require all external integrations to pass readiness.

Public website/hosted-form submissions are blocked before LIVE in staging/production by default. Local Docker enables pre-live form testing only for acceptance work.

9. Support triage and service levels

Support tickets are automatically classified by issue type and severity. Critical/high incidents create operational alerts. Feature requests are copied to the platform feature backlog. SLA timestamps are calculated from the customer's plan and severity and are monitored by the operational sweep.

10. Platform operations

Platform administrators use /admin for workspaces, operational alerts and feature requests, and /support-admin for support tickets. /readyz shows integration readiness. Serverless hosting uses the protected dispatch-drain and operational-sweep endpoints rather than an infinite worker loop.