How it works

It does the work.
You decide what ships.

Four stages, in order, every time. The operator reads your tools, prepares the work up to the send button, holds it for your approval, and then goes back to confirm the change actually landed. It cannot skip a stage.

01 · Observe

It reads what you already have

Connect Housecall Pro and QuickBooks. The operator reads them and builds one picture of the day.

Jobs, appointments, customers, invoices, and the money attached to each. It reconciles them against each other rather than trusting any single tool, and it tells you how fresh each source is — so you know whether you are looking at this morning or last Tuesday.

Where it stops

It changes nothing while it reads. Access is read-only at this stage, and it stays read-only until you connect something more.

What this needs first

A connected workspace and fresh Housecall Pro read access are required.

ObserveVerify
How this works

02 · Prepare

It does the work up to the send button

The follow-up, the lead, the schedule change — written, attached to the right record, and waiting.

A missed call becomes a drafted lead with the customer's context already on it. An aging invoice becomes a follow-up with the amount and the history filled in. A gap in the schedule becomes a proposed change against a specific job. The work is finished, not suggested.

Where it stops

Nothing has left the building yet. A draft is a draft, and drafts expire rather than escalate.

What this needs first

A captured request, Housecall Pro setup, owner approval, and enabled write controls are required before an external lead is created.

PrepareApproveExecuteVerify
How this works

03 · Approve

You see the exact change before it happens

Not a summary of the change. The change.

Every prepared action shows the precise text that will be sent, the exact record it will touch, and what it will look like afterward. You approve it, edit it, or throw it away. There is no bulk-approve-everything button, because that is how you end up apologizing to a customer.

Where it stops

No approval, no action — and provider writes sit behind an environment kill switch that is off by default, so approval alone is not enough.

What this needs first

An existing job, Housecall Pro setup, owner approval, enabled write controls, and provider verification are required before a schedule change is treated as complete.

PrepareApproveExecuteVerify
How this works

04 · Verify

It proves what happened

The operator goes back and checks the provider actually took the change.

An approved action is not treated as done because it was sent. The operator re-reads the provider, confirms the record changed the way it was supposed to, and records the result. When a provider silently rejects something, that shows up as an exception rather than as a success.

Where it stops

It will not report an outcome it could not confirm. An unverified action stays unverified on your screen.

What this needs first

A connected workspace and fresh QuickBooks read access are required.

ObserveVerify
How this works

The gates

Three gates before anything leaves. One proof after.

These are not settings you can talk the operator out of. The first three are enforced before a send can happen, each in a different layer — and once it has, the operator still has to prove the change actually landed.

  1. Gate 1

    Connect the provider

    Nothing exists until a provider is connected and reading. An unconnected workspace shows you an empty operator, not a demo.

  2. Gate 2

    Approve the action

    Every outbound action starts approval-gated. The only way a send type runs on its own is a lane you explicitly flip to earned-auto after it builds a clean approval streak — and you can revoke it at any time.

  3. Gate 3

    Enable the write control

    Provider writes sit behind an environment kill switch that ships off. Approval without it prepares the action and stops.

  4. After the send

    Verify the result

    The operator re-reads the provider and confirms the change landed. An unconfirmed action never reports as done.

See it read your actual business.

Connect one provider and the operator builds your first owner queue from real records — not a sample workspace.

Request a demoSee pricing