Skip to main content

Your booking agent scheduled a job with no address.

Check each record your agent creates before it reaches your calendar, your CRM, or your books.

How do you check the bookings and invoices an AI agent creates?

You write the rules for each record, such as a complete address, a ZIP code in your service area, or totals that match the order. Your agent submits each record to Vindex before it is saved, with any order or visit notes it depends on, and an independent model rules on it, naming any rule it did not pass.

  1. You write the rules

    Office Manager, Bookkeeper, and Dispatch Lead

  2. Your agent does the work

    Appointment bookings, lead records, invoice entries, and billing codes.

  3. Vindex rules on it

    An independent model checks each output against the rule version in force and names any rule it did not pass.

Each branch checks the others. The agent never reviews its own output.

The rules you write

These are examples to adapt. Your company drafts, versions, and owns every rule, in plain language or from public rules. An agent can draft a rule. Only a person makes it law.

  • Complete booking

    The booking includes the service address, a callback number, and the job type.

  • Service area

    The service address is in a ZIP code on your service-area list.

  • Lead owner

    Every lead record names one owner and a next contact date.

  • Invoice matches order

    The invoice total and line items match the purchase order and receipt supplied with it.

  • Code matches service

    The billing code matches the procedure described in the visit notes supplied with it.

Some checks compare two documents, so submit the order and receipt, or the visit notes, with the record. Checks that need payment history, such as duplicate invoices, belong in your accounting system. Vindex does not give coding or billing advice.