The dispatch flow, one job end to end

This walkthrough follows a single job from the moment the AI answers the phone to the moment the invoice is emailed. Every step maps to a real write action in the product, and the action name is printed on the step so the demo stays checkable against what the app actually does.

Switch the trade to see how the same flow changes shape. Where the work happens is part of the trade configuration — a field trade travels to an address, a shop trade books a bay — so the steps differ for a plumber and a barber even though the underlying flow is the same.

The seven steps, and who does each one

The short version: the first step is the AI, the last is automatic, and the ones in between are a tap each from whoever is doing the work.

  1. Booked by the AI — the call is answered, the slot is checked against the live calendar, and the job is created. Nobody on your team is involved.
  2. Assigned — one tap from the board to put the job with a person. On Pro, Ansdale suggests who to send.
  3. On my way — one tap sends the customer a message, so the "what time are they coming?" call never happens.
  4. Checked in — the tech marks arrival, and the customer is told work has started.
  5. Arrived on site — the job is live, with the address and notes already attached.
  6. Visit report filed — notes and photos captured at the property rather than reconstructed at the end of the shift.
  7. Invoice emailed — the completed job becomes an invoice with the report and photos attached, without anything being retyped.

What needs which plan

Every plan answers calls and books jobs — that part is not gated. The dispatch board itself is a Growth feature, and the assignment suggestion is a Pro one. The demo shows the plan gate where it falls rather than hiding it.

Is this real customer data?

No. Every name, address and figure in the demo is fixture data generated in the page. Nothing here comes from a live Ansdale account, and no real customer information is used to build these screens.