Automation Lab
Watch a lead travel. Then break it on purpose.
What happens after a customer gets in touch: the enquiry is saved, sent to a CRM, followed up, and watched. Switch parts of the system off and see how it copes.
Interactive preview. The CRM and the receiving system on this page are simulated in your browser, with made-up people. The logic you see (signed messages, retries, duplicate protection, a run log) is what we are building into the live product.
Try this A guided tour
1 A customer gets in touch
Saved in Assist Street 0
- Nothing yet. A lead is always saved here first, whatever happens next.
2 The CRM is…
3 The client's CRM (simulated)
New enquiry 0
Contacted 0
Booked 0
The CRM is empty. Send an enquiry and watch a card appear.
4 Bookings and reminders
Ready customers get a booking link in their follow-up. Pretend to be one of them:
- No appointments yet. Pick a customer and a time above.
5 Invoices and payment reminders
When a job is finished, an invoice goes out and reminders chase it politely until it is paid. Assist Street never handles the money: customers pay the business directly, and the owner (or their accounting tool) marks the invoice paid.
- No invoices yet. Send an enquiry, then mark a job done above.
6 What just happened
- Send an enquiry to begin.
7 Emails sent (simulated)
- No emails yet.
8 Paperwork: read, check, file
Invoices and forms arrive by email. The system reads each one, checks it the way a careful person would, and then files it, holds it, or sends it to a person. Ordinary paperwork needs nobody. Anything odd (wrong sums, a changed bank account, a missing consent, a second copy) stops and waits. Nothing is ever paid by this system: the practice pays from its own bank, and the system only reminds.
These are made-up documents, read as text by fixed rules in your browser. A real build adds a scanner step (OCR) in front of the same checks, and a person always settles anything the checks cannot.
9 The weekly summary
Every Monday at 08:00 the owner gets a plain-English summary, built from the same run log you see below. A daily health check also watches for trouble, such as a quiet week or leads stuck outside the CRM.
No summary yet. Simulate a week, or preview this week, to see one.
The week of activity is made up for this demonstration. The counts in the summary are real counts from the engine on this page.
10 The run log
Every automation run is recorded. Nothing fails silently. Select a row to see each attempt.
| Started | Lead | Automation | Status | Attempts | Next step | |
|---|---|---|---|---|---|---|
| No runs yet. | ||||||
What runs for every enquiry
- Acknowledge the customer within seconds, in their own language.
- Email the owner with an English summary.
- Hot-lead alert when the customer is ready to book, with a faster follow-up.
- Needs-a-person alert when the assistant could not fully answer.
- Send to the CRM, with retries and a record of every attempt.
- Reply deadline: a reminder after 2 hours and an escalation to a manager after 4, unless someone has contacted them.
- Follow-up after 2 days (1 day for hot leads), cancelled if the customer replies.
- Booking: a confirmation in the customer's language, reminders 24 hours and 1 hour before, a "we missed you" message after a no-show, and the old reminders cancelled if they move or cancel.
- Invoices: sent in the customer's language with a payment link, then a heads-up 3 days before, a reminder on the due date, a firmer one at 7 days late, a final notice at 14 days that also asks the owner to call. It all stops the moment the invoice is paid, and part payments reduce what is asked for.
- Weekly summary every Monday at 08:00, and a daily health check that warns about a quiet week or leads stuck outside the CRM.
How the retry rule works
A message is sent straight away. If the CRM is temporarily unavailable, it tries again after 1 minute, 5 minutes, 30 minutes, 2 hours and 6 hours. If it still fails, the run is marked dead and you are alerted. If the CRM says the address is gone for good (an error such as 410), it stops straight away, because trying again can't help. Each message carries a unique ID, so if one is delivered twice by accident the CRM ignores the repeat.
Want this for your business?
We are building this with a small number of founding clients. Tell us how enquiries reach you today, and we'll show you what it would look like for you.