You decide what “ready to book” means.

Each service carries its own duration, the skills it needs, the buffer around it and the questions that must be answered before anyone can be sent. Readiness is measured against that template, so a request is never complete because a model felt that it was.

The template is the contract between the AI and your operation.

Nothing else in the front office decides what “complete” means. The catalog does. A service names its duration and the buffer around it, the skills a technician needs, the zones it is offered in, and the fields that must carry an answer before a slot may be held.

That is what keeps qualification honest. Ven can read a message and propose values, but it cannot decide that a boiler service is ready without a system type — because the template says the system type is required, and the readiness check reads the template rather than the prompt.

Every rule a booking depends on, in one place

A service is more than a price

Duration, buffer before and after, required skills and the service zones it is offered in. Slot search reads all four before it shows a single time.

Service templateBookable

Boiler service

90 min+15 min bufferGas licenceZones 109–120

Must be answered before booking

  • Service address
  • Boiler make and model
  • Date of the last service
  • How the technician gets in

Required questions, with their own types

Text, choice, date or number, each with a validation rule and the exact wording Ven may use to ask. A field marked required blocks booking until it carries an answer.

Service requestQualifying

Boiler service · 90 min

M. Berger · WhatsApp

Service address

Lindenstr. 14, 10969 Berlin

Message · 0.96

Equipment

Vaillant ecoTEC plus

Photo · 0.88

Last service

Question sent

09:41

Access

Not known yet

Required

Next question: parking and key handover

  • Optional stays optional

    A manufacturer the customer rarely knows is worth recording and never worth blocking a booking over.

  • Buffers belong to the service

    Travel and write-up time are part of the slot, not something the day is expected to absorb.

  • Bookable one service at a time

    Autonomy is granted per service in its own form, so a new template cannot widen what the AI may do.

  • Change it and the next request follows

    Editing a template changes what counts as ready from that point on; requests already booked keep the brief they left with.

From a service you sell to a request that can be scheduled

You write the template once. Every enquiry for that service is then measured against it, whether a person or Ven does the qualifying.

  1. 01

    Describe the service

    Duration, buffers, the skills it needs and the zones you offer it in — the same facts a dispatcher already holds in their head.

  2. 02

    List what must be answered

    The fields that decide whether the visit can succeed, each with a type, a validation rule and the question Ven is allowed to ask.

  3. 03

    Readiness follows automatically

    A request shows exactly which required fields are still missing, and slot search stays closed until none are.

A prompt is not a specification.

It is tempting to describe your services to the model in prose and let it work out the rest. That produces an assistant that is confident on Tuesday and different on Thursday. A typed template produces the same answer every time, can be read by a person who does not trust the AI yet, and is the reason readiness is a fact rather than an opinion.

  • Its own booking rules

    Duration, buffers, skills and zones, read by every slot search.

  • Its own required fields

    Typed, validated, and worded the way you want them asked.

  • Its own autonomy setting

    Bookable or not, decided for this service alone.

Write the rules once, apply them to every enquiry

Start with a single service, its duration and three required questions. That is already enough for Ven to qualify against.