Every job has a dozen small handoffs.
None of them should need remembering.
The permit email that lands at 4:40 on a Friday. The certificate that lapsed in March. The payment that failed on Tuesday. The proposal that got signed while you were on a roof and nobody told the office. None of it is hard — it's just things somebody has to notice. This is the page about what stops needing to be noticed.
The permit office writes at 4:40 on a Friday.
The carrier writes on Saturday. Somebody has to open it, work out which job it belongs to, move the punchlist and file the PDF — and that somebody is doing it Monday, if they remember, and after the homeowner has already called to ask.
Nobody does that here. Your connected inbox is checked every minute: the email is read, matched to the job, the punchlist moved and the PDF filed onto the contact before anyone opens it.
- Only the senders you set a rule for are touched — a recognizer you configured has to match, and everything else is left completely alone.
- When it isn't sure, it doesn't guess. Low confidence or an unknown sender goes to a review queue with a bell alert, for a person.
- It files and it moves. It doesn't create contacts or jobs, and it never sets an outcome twice.
You know the rule you want. You don't know where it lives.
So it stays in your head — and the thing you wanted to happen by itself keeps happening by hand, or keeps not happening at all. Nobody quits a CRM because it couldn't do the thing. They quit because they couldn't find where the thing lived.
Type it the way you'd say it out loud: “when a financing deal is signed, email the sales manager and move it to Proposal Signed.” The trigger, the conditions and the actions come back drafted on the canvas. You fill in who, and save.
And the rule you actually need always has an exception in it. Stack the conditions that have to be true together, then add a whole second way to qualify underneath — metal jobs over $20,000, or any insurance job at all. Each field only offers the operators it really has: greater-than on money, is-any-of on a picklist, is-between on a date, contains on a name.
- It can only build what the engine actually runs — so it can't hand you a rule that silently never fires.
- It comes back as a draft on the canvas, not a saved automation. Nothing runs until you say so.
- The When / If / Then reads back in plain English, so anybody on the team can check what fires and when.
- The exception is part of the rule, not a second automation you have to remember you wrote.
The rules that run — and the one thing they won't do.
Every rule in the engine talks to your team. It emails a person, a role or both. It posts to the bell — including to whoever owns that job, resolved per event. It moves a contact to a stage, or into a different pipeline entirely, where it lands on that pipeline's own entry stage. It moves a job along its board. It assigns work, puts a subcontractor on it, ticks a to-do to an outcome, sets the permit tracker. It appends property & owner data. It releases accrued commissions. Any of it, only when your conditions match.
The four below are examples, not the menu. There are 51 moments the engine already watches for you — proposal declined, appointment canceled, a tracker moved (the permit, or one of your own), requirement at risk, subcontractor certificate expiring, missed call, ACH deposited, payout failed, punchlist all clear. You are not picking from a shortlist somebody guessed at three years ago.
What it will not do is message your homeowner.
There is no send-to-contact action in the engine — no text, no email, no status update to the person who owns the house. Every rule here notifies your own people. We'd rather tell you that on this page than let you find out on the first rule you write.
Don't know how to do something? Just ask.
The job doesn't wait while somebody hunts through settings for the switch they were shown once. You don't have to learn it to use it — you can just ask for it, the way you'd say it out loud.
Ask where a setting is and it walks you there. Ask it to do the thing and it does it — after showing you a card describing exactly what it's about to write.
- It works as you — every lookup and every action runs against your own permissions, not a service account's.
- Nine of its tools write anything at all, and every one of the nine puts a card in front of you first: creating a task, scheduling an appointment, updating a contact, moving a job, sending a payment link. Cancelling an appointment makes it state a reason on the card.
- When the answer isn't in your CRM it can go and look — up to eight web searches in a session, each one showing up as it runs, so you always know whether an answer came off your own records or off the web.
- Chat or voice, docked wherever you're already working.
Claude Opus 4.8 answers chat · Google Gemini answers voice · usage metered to the token.
Every one of these is somebody remembering.
Stop making it somebody's job.
Month-to-month · usage metered to the token · your data stays yours.