Booking & rebooking deskMessage in → location, service, person → draft reply with real open slots → staff approve

Before

    After

      Sample messages:

      Follow-up lists

      How it works

      1. Read. Each text, web form or email is read for who it's from (matched to the client record by phone or email), what they want, which location, which person and when. Every field is marked clear, assumed (for example from their usual stylist) or needs a look. This page uses a deterministic rule reader; a production build adds a language model held to the same field list, with these rules kept as a test check.
      2. Find real openings. Slots come from the calendar itself: working hours, existing bookings, service length and, for salons, the stylist level a service needs. Nothing is offered that isn't free.
      3. Hold, don't guess. Complaints, refunds, unclear requests, two locations at once, and in dental mode any mention of pain or swelling or a cost question go to a person with a holding draft and no slots. The tool never assesses symptoms or suggests treatment.
      4. Draft, then approve. Replies and follow-up drafts sit in a queue. Staff edit and approve; in a real build approved messages go out from your existing texting tool or inbox. Opted-out clients are skipped.
      5. Follow up. Lapsed regulars (past their usual gap), overdue recalls and recommended-but-unscheduled treatment become lists with drafts offering their own provider's openings. Dental drafts carry plan IDs only, with estimate clarity notes for the coordinator.

      Production architecture

      Architecture: messages from texting tool, web forms and email, reader, calendar and client-record lookups, slot finder, approval queue, and approved replies sent from your existing tools