Speed-to-lead workflow
Lead-response proof
A contact-form lead becomes an SMS qualification thread and a structured owner handoff instead of sitting in an inbox.
No fake screenshot here.
This proof is grounded in the rendered walkthrough and the SMS-agent code path. Public screenshots should be added after a consented test run or anonymized owner-summary capture.
Workflow
How the workflow runs.
- 1
A lead submits the Prairie AI contact form with name, business, phone, goal, and project details.
- 2
The contact API can forward the payload to the SMS service with a shared lead secret.
- 3
The SMS agent starts a fresh conversation, sends an opening text, and stores short-lived conversation state.
- 4
Inbound replies come through the Twilio webhook. The agent asks one question at a time until it has the current process, scale, desired outcome, and timeline.
- 5
When qualification is complete, Josh receives a summary email with the useful details and full SMS transcript.
What the owner sees
Who the lead is and what business they are from.
What they said they need help with.
Current process, scale, desired outcome, timeline, and confidence.
A recommended next step instead of a raw message dump.
Human review point
The agent qualifies and summarizes. Josh still decides the response, scope, pricing, and whether the inquiry belongs in an AI Audit or implementation project.
Connection to AI Audit
AI Audit is the front door: the same intake questions help identify whether the owner needs recommendations first or a build right away.
View AI AuditConnection to launch work
A Launch Sprint can turn the same pattern into the client's own follow-up workflow across forms, email, SMS, calendar, or CRM.
View AI AutomationGrounded artifacts
- Interactive sample workflow at /workflow-lab.
- Contact route forwards lead data to the SMS service when configured.
- SMS agent README documents the Twilio, Redis, and owner-summary flow.
- Summary formatter includes current process, scale, desired outcome, timeline, budget hint, next step, confidence, and turn count.
Follow-up assets needed
- Add a real rendered screenshot of the SMS conversation after a consented test run.
- Add an anonymized owner-summary capture once one is approved for public use.
Bring your version