A confirmed visit is already somebody's job.

Confirming the visit creates the job at the same moment. The technician gets one dependable brief with the address, access notes, equipment and customer answers — not a trail of messages to piece together on the road.

The whole brief in one place

Service, address, access, equipment and every answer, gathered as the visit is booked — plus whatever your dispatcher adds in their own words. If the customer moves the date or swaps what they asked for, the brief is updated with it.

You always know if the confirmation arrived

Every confirmation shows whether it was delivered. If one fails you can see it and resend it, instead of hearing about it from the customer.

01

Confirmation creates the job

Confirming writes the appointment, the work order and the brief together. Confirm twice and you get the same job back, not a second one.

02

Dispatch and status

Created, dispatched, in progress, completed, cancelled. Five states, kept few on purpose so they stay accurate.

03

Finished work shows up in the report

Completed jobs are the last stage of the report, which is what makes enquiry volume mean something.

The brief as it was at booking

A snapshot of the request as it stood when the visit was promised.

A confirmation that landed

A failed send is retried on a widening delay, and the run stops the moment one lands.

The last stage of the report

The last stage of the report that turns conversations into countable work.

Lavenity closes it by making both one fact. A confirmation writes the appointment and the job together, and a unique index, not a check in the code, is what makes a repeated confirmation return the job you already have.

  • Numbered out loud

    JOB-0117 — because people say the number to each other on the phone.

  • Cancels without collateral

    Cancelling a visit withdraws work nobody started and leaves work already underway alone.

  • Linked both ways

    The job knows its request and appointment; the customer's confirmation links back to both.

  • An event to build on

    Every created job publishes a domain event — the seam future connectors read.

Send every technician out with the full job brief

Every confirmed visit becomes a job with the address, access notes, equipment and answers already attached.