1. Customer inquiry form (sample)
Please don't type real names, numbers or addresses. Nothing you enter leaves this page: no data is saved or sent, and no text or email goes out.
2. What the owner sees
Submit a sample inquiry to see the lead summary and notification previews.
3. Lead list (this page only)
In a real setup this would be a row in the client's shared sheet or CRM. Here it lasts until you reload the page.
| ID | Received | Urgency | Name | Need | ZIP | Status |
|---|---|---|---|---|---|---|
| No sample leads yet. | ||||||
4. Built-in test cases
Before a handoff, every rule is checked against written test cases like these. Click to run them against the rules on this page.
| # | Test | Expected | Got | Result |
|---|---|---|---|---|
| Not run yet. | ||||
5. How this would be set up and tested for a real business
This page imitates the workflow with fixed rules so you can try it safely. For a real client, the same steps would run inside tools the business already uses or approves. Every setup is scoped and confirmed in writing first.
Configuration
- Inputs. The business's existing website form, a missed-call text-back from its phone provider, or both. We connect to them through access the owner grants and can remove; we never ask for passwords by email.
- Summary and urgency. The owner approves the urgency rules in plain words (for example: "water coming in" or "tarp" means urgent). An AI step can write the one-paragraph summary; it isn't allowed to promise prices, dates or coverage.
- Notifications. The owner chooses who gets texts, who gets email, and quiet hours. Urgent leads can text right away; others can roll into one daily digest.
- Customer reply. The owner approves the exact auto-reply wording, including an after-hours version. Texts to customers are sent only where the customer gave permission, and every text says how to opt out.
- Records. Each lead becomes a row in the owner's own sheet or CRM, not ours. What's stored, and for how long, is written into the scope.
Testing before handoff
- Written test cases with expected results (like section 4), including blank fields, very long messages, wrong phone formats and duplicate submissions.
- Test leads with fictional details go through the client's real tools to test numbers the owner controls, during and after business hours, before any customer traffic.
- A fallback: if the summary step fails, the owner still gets the raw inquiry by email, so a lead is never lost.
- The owner signs off on a handoff checklist: what it does, what it doesn't do, how to pause it, and who to contact. See testing and handoff.
What this demo does not do
- It doesn't send texts or emails, save anything, or call any outside service. The "AI-style" summary is a template filled in by simple rules.
- Results in a real setup depend on the client's tools, plan limits and approved rules.