Skip to content
LLDTEK
Book a demo

Integrations

How LLDTEK connects to the booking system or POS you already run, what the agents read and write, and how permissions are set per agent.

Updated 27 October 2026
On this page
  1. Booking systems with a guide
  2. What the agents read
  3. What the agents write
  4. Permissions, least first
  5. Multiple locations
  6. Double-booking

LLDTEK works beside the system you already run. Your calendar, checkout, payroll and client records stay where they are. The agents read what they need to do the job and write back only the actions you approve.

#Booking systems with a guide

Each of these has a dedicated page explaining what the platform already does well and what the agents add beside it.

VagaroSalons and spas. Books the stylist who is free into your Vagaro calendar.Square AppointmentsSquare stays the calendar and card reader. Bookings land in it.BooksyAnswers what your chair cannot and writes into the Booksy calendar.ZenotiCovers the desks across every center, with Zenoti as the book.MindbodyFitness and wellness schedules, memberships stay in Mindbody.JobberField service. Takes the calls your crew cannot take from a ladder.

Running something else? We connect to many more booking systems and POS platforms than have a page here. Ask on the demo and we will tell you on the call whether yours fits.

#What the agents read

  • Services, durations and the providers who perform each one.
  • Staff schedules, opening hours and location details.
  • Availability, including rooms, chairs or resources a service occupies.
  • The waitlist, where your platform has one.
  • The client's past visits, so rebooking can offer the same person.

#What the agents write

ActionUsed byNotes
Make a bookingFront deskOnly into slots your calendar returns as open
Change or cancel a bookingFront deskOnly where your rules allow it, otherwise handed off
Fill a cancellationRecoveryThe first client who says yes gets the slot
Book the next visitRebookingSame provider, on the service's cadence
Request a reviewReviewsOnce per client visit

#Permissions, least first

Each agent gets only the permissions its job needs. Reads are switched on and tested before any write is allowed, and writes are added one at a time:

  1. Read path. Slots that should exist, slots that should not, requests that cross closing time.
  2. Single write. One booking type on one channel, checked in your calendar after each write.
  3. Wider scope. More services, locations or agents, each tested as a new surface.

#Multiple locations

Each location keeps its own book, staff and hours. The agent books the location the customer asked for and does not mix calendars. If the customer does not say, it asks.

#Double-booking

The agents book against the availability your system shows for that provider and service length. If a slot cannot be confirmed, the agent offers alternatives or hands the request to your team instead of guessing.