The foundation the assistant will stand on is built. The assistant itself is not. Each card says which is which.
Built
Structured business records
Membership plans, class templates and dated sessions, instructors, members, FAQs and business notes. Each member has a flag for whether they may book through the assistant. Leads, conversations, bookings, sign-ups and handoffs have their own records too.
Built
An admin app for the team
Staff maintain everything in one place, organised into Inbox, Catalogue, People, Operations, Knowledge and Settings. This side is deployed and running in a pilot.
Built
Guard rails on the data
Every record belongs to one business, and access is refused when a user has no business assigned. Business notes are capped at 300 characters, and common instruction-like phrases aimed at the AI are removed on save. Customer numbers are unique per business.
Planned
Website chat and confirmed bookings
The website chat is the first channel. It will capture prospects, hand over to a person when needed and book classes for verified, active members. Not built yet.
Planned
Keeping answers honest
Warnings for information nobody has re-confirmed in 30 days, a place for owners to test their own assistant, and a preview of the bookings affected before a schedule change is saved.
Planned
More channels later
Telegram and WhatsApp, plus a Telegram bot for managers to check the day's schedule, cancel a class or mark attendance by chat.