Turn finished jobs into public reviews — and catch the unhappy customers privately, before they post.
Three minutes of questions first. If it does not fit, we say so and you pay nothing.
The problem
Reviews decide who gets called first, and almost nobody asks for them. The staff who could ask are busy finishing the next job, and when someone does remember, it is usually a week late and sent to everyone — including the customer whose appointment ran two hours over. Asking manually is either skipped or done at exactly the wrong moment.
What it does
What you provide
Accounts stay in your name and are billed to you, so nothing depends on us staying in the picture.
What you get
A running automation on a server you own, wired to your systems and tested with your data before it goes live. The email version works the day you buy it — it needs one account of yours and nothing else. The text-message version does the same thing by SMS and cannot start until US carriers have registered your business to send, which takes days to weeks, happens in your legal name, and nobody can shorten. Buy the email one now and switch the texts on when your registration lands, at no extra cost. Either way you get a login, a one-page guide, and a pause switch. If it breaks, we're alerted before you notice, and once a month you get an email showing what it did.
Before you ask
Then we haven't finished. We don't consider a build done until it's run against your real data, including the messy cases. If we can't make it work for you, you don't pay the setup fee.
Watching it, and the work that comes out of watching it. When a run fails we're told automatically and we go and fix it — you don't have to notice it or report it. When your phone system changes a setting, or a provider changes something underneath, that's ours to sort out too, and small changes to the wording or the rules are included rather than quoted. Once a month you get a plain email showing what it actually did, which is also how you decide whether this is still worth paying for.
Thirty days' notice and the monthly fee stops. The automation doesn't — it's on your server, under your accounts, so it carries on working without us, and we hand over everything needed to keep it that way. There's nothing to migrate off and nothing to export. What you're cancelling is us watching it, not the thing itself.
You do, entirely. It runs on your own server, under your own accounts, with your own API keys. There's no platform to be locked out of. If you leave, it keeps running and we hand over the keys.
No. You tell us what happens now and who it happens to. We build it, test it against your real data, and hand you one page explaining what it does and how to switch it off.
We're told automatically, usually before you notice. Every automation we build has failure alerting wired in before it goes live — that's not an upgrade, it's a condition of us shipping it.
Onto infrastructure you control and nowhere else. We never hold your API keys — you enter those yourself, and they're encrypted where even we can't read them back. For regulated work this is usually the whole reason people call us.
About fifteen minutes to connect your accounts, a description of the process you want automated, and someone to answer a question or two while we build. That's it.