Quickstart
LLDTEK goes live in five steps. Connect the book you already run, write the rules, test real scenarios, launch beside your team, then improve from live runs.
On this page
Going live takes days, not a rollout. You bring the operating knowledge; we do the build. Nothing is migrated, and checkout, payroll and the till stay where they are.
#Before you start
Have these ready for the first working session. Rough is fine; we tidy it up together.
- Access to your booking system or POS, such as Vagaro, Square Appointments, Booksy, Zenoti, Mindbody or Jobber.
- Your service menu with durations, who performs each service, and any room, chair or table a service needs.
- Opening hours for each location, including what changes after close.
- A representative week of calls, texts and booking questions, including the ones that were missed.
- A named person or role for each kind of exception, and how quickly they can realistically reply.
#The five steps
Connect
We link the calendar, POS and records the agents need to see, and agree the actions they may take. Reads are tested first: slots that should exist, slots that should not, and requests that cross closing time. Writes are switched on only after the reads come back correct.
Done when the agents see your real availability and a correct refusal comes back as reliably as a correct offer.
Configure
We listen to your week of calls and write a one-page operating brief for each job: the trigger, the goal, the actions allowed and the conditions that stop it. Every handoff is tied to an owner.
Done when your team can read the brief and agrees with every rule in it.
Test
We run an ordinary booking, then the cases that make a desk pause: the preferred provider is free but the room is not, two requests chase the last slot, a complaint arrives on the booking line. After every write we open your calendar and check the record.
Done when each case ends in a booking, a refusal or a handoff that follows the written rule.
Launch
We switch on the agreed job, on the agreed channel, in a narrow window first. After-hours or lunch overflow is usually easier to watch than a full Saturday. A named person watches handed-off threads, and everyone knows the pause procedure.
Done when bookings land correctly and handoffs reach their owner with the full thread.
Optimize
For the first week we review runs together for about fifteen minutes a day. Each failure is traced to its cause and fixed at the source. New channels, services, locations or agents are added one at a time.
Done when the correction queue shrinks and routine runs stop needing attention.
#What changes for your team
Very little on day one. The phone number on the door stays the same. The person at the desk still runs the floor, and the agents take the overflow: the call during a full floor, the text at 10pm, the slot that opened at 3:30.