AI Chat — asking Bookodile how things work and how you're set up

AI Chat is an assistant in your dashboard. Ask it how something in Bookodile works, or how your business is set up, and it answers from the help pages and from your own settings. It can also set things up for you, and move or cancel bookings: every change is shown on a card first. A card that only writes texts — bios, your about text, service descriptions — or changes your website's draft is applied as soon as it appears, with Undo; everything else waits until you apply it.

It is part of every account, for everyone on your team. AI Chat is in the menu, near the top, and in the search (⌘K).

What it can answer

• How Bookodile works. It searches these help pages, reads the one that answers you, and links it at the end of its reply so you can read it yourself.
• How you're set up. It reads the branch you're in: your team and their working hours, your services, your resources, your opening hours and your booking settings. It reads them with your own account's access, the same rules that decide what your account can read anywhere else in Bookodile.
• Why a day is empty. Ask why Thursday has no times, or why customers can't book someone on Monday, and it checks what your booking page offers that day: which services have free times, who works, and the reason when there are none — closed that day, the team member doesn't work then, is on time off, or has nothing free, nobody who does that service is in, your minimum notice, or a day beyond how far ahead customers can book. A combination of services is checked stage by stage, with the team member set on each stage.
• A day's bookings. Ask what tomorrow looks like, or what one team member's day holds, and it summarises them: times, services, who, and what's still pending. It sees only the bookings your role shows you.
• The last booking. Ask when the last booking was, when a customer was last in, or when a team member last had a client, and it finds the latest bookings however long ago they were — and the next one after, so a customer booked again for tomorrow isn't described as gone.
• Who's away. Ask whether anyone has time off planned, or when someone is away, and it lists the team's time off for the next 90 days, or the days you name. If your role can't manage the team, it sees only your own time off.
• Your best customers. Ask who spends the most or who comes most often, and it ranks this branch's customers over the last year, or the period you name: what each spent and how many visits. It counts the way Statistics does — bookings that weren't cancelled and weren't a no-show — but only visits that already happened, and a visit of several services once. Only a role that sees every customer, every booking and the statistics can ask; no screen ranks customers this way.
• Who changed what. Ask why a customer is booked at a time, who moved or cancelled a booking, who changed a price or switched a setting, or what changed today, or what happened to one team member's bookings, and it reads the activity log: who did it, how and when. For one booking it also says when and how it was first booked, and what the customer was sent about it. It sees only the history your role shows you, and never the words of a note.
• In All branches, the organisation owner can compare branches and copy between them (see All branches); everyone else gets how-to answers only. Pick a branch to ask about its setup or its bookings.

It replies in the language your dashboard is in. When it writes something your customers will read, it writes it in your business's main language; Bookodile then translates it into your other languages by itself, within a few minutes (Other languages your customers read). Asked why something isn't translated yet, it says the translation is on its way and points you to See translations under the text, where you can read and correct each language.

Setting things up from the chat

Tell it what your business looks like, for example a team of four with three rooms or stations every service needs, and it asks for anything missing (names, hours), then shows one card with everything on it. A service's price or length you didn't give is left empty on the card for you to fill in — see Prices and durations on the card. Nothing changes until you press the card's button — except a card that only writes texts (see Texts are applied at once).

What a card can do:

• add team members (they work your opening hours and do every service, unless you say otherwise). The chat adds a name only: add their email or phone, and invite them to sign in, from Team
• change a team member's working hours: one day or several, a day off, or a break in the middle of a day. The rest of their week stays as it is
• write or change a team member's bio, the short text customers see beside their name on your booking page, at most 200 characters. Ask for placeholder bios and it writes short, friendly ones without inventing facts like years or awards; the card shows each one before and after
• write or change your about text — the few lines about your business that customers read on your booking page, at most 500 characters — and a short description for each service, at most 600 characters each. Ask "write my about text" or "describe my services" and it writes them from your setup (your services, team and opening hours) without inventing facts; the card shows each one before and after, and a description changes only that text, never the service's price, length or who does it
• set your social links — Instagram, Facebook, TikTok and YouTube — the icons in your website's footer. Give it the username or the profile's address and it checks each one the way the website editor does; it never guesses a username from your business's name
• set your Google Maps link (Business profile) — the business every map on your website and its Directions show. Give it the link from Google Maps (the Share link works); it follows and checks it the way Business profile does, and never makes one up or searches for one
• add resources, and say which services need them
• add services, or change a service's price, duration or who does it
• give some team members their own price or length for a service; everyone else keeps the service's own. A junior team member might charge less for a haircut, or a newer coach take longer for an assessment
• build a combination of services from stages, each with its own length and the team member and resource it always uses
• choose the add-ons customers can pick with a service
• create categories of team members, like Junior and Senior, and put people in them
• switch a team member, a service or a resource off, or back on. Their bookings stay. The card says what else would stop being offered, which services a service you switch off stops being an add-on with, and how many upcoming bookings stay as they are. Switching a service off (archiving it) takes it off your booking page completely, add-ons included
• show a service only as an add-on: off your booking page's list, still an extra with the services that offer it. Or list it on its own again. The card says when no service offers it, because then no customer can book it online
• change the order your booking page lists services or team members in ("show Gay Hair last", "put Daniel first"). Services move inside their own category; the order of the categories themselves is dragged on the Services screen. The team's order is also the calendar's and every list of your team. The card lists the new order with what moved
• change who customers see first for one service, or for every service in a service category ("for the hair wash, put the juniors first"). It is the order the booking page lists the people who do it in, and the order "Anyone" goes through: the first one free gets the booking. Ask it to go back to the team order and it switches the custom order off. It can also tell you who an "Anyone" booking goes to, and link you to the place it is set
• set your opening hours, and the booking settings: minimum notice, how far ahead customers can book, the cancellation window, late cancellation, how often start times are offered, and automatic confirmation

If you add to a setup card before confirming it ("and we're open Saturdays too"), the new card keeps everything from the one before; say "start again" to drop it. A chat has one card waiting at a time, though: a card of another kind — an add-on, a booking, blocked time, a copy between branches — replaces a setup card you haven't confirmed, and that card's changes are not made. It never guesses a price or a duration. It changes an existing service rather than adding a second one with the same name.

Service names are written in your main language, as businesses of your kind there name them on their price lists — the usual term, not a word-for-word translation. Bookodile translates them into your other languages afterwards, on its own.

Prices and durations on the card

Until you apply a setup card, each service on it shows its length and price in fields you can change. One you didn't give the chat is empty, and the card's button waits until it is filled in; anything you type is kept if you ask the chat to add something else before applying. A price per team member and a combination's stages aren't changed on the card: ask the chat. The numbers are checked the way the Services screen checks them — a length from 5 to 480 minutes, a price of 0 or more.

What your role allows. A card only does what you could do in the dashboard yourself:

• team members, their working hours, bios, categories and order need the team permission;
• services, their descriptions and their order need the services permission;
• opening hours, booking settings, resources, add-ons, your about text, your social links, your Google Maps link, your logo and your brand colour need the settings permission — and a resource that says which services need it, the services permission too;
• moving, cancelling and handing over bookings need the permission to change bookings.

Someone whose role allows none of these can still ask questions. A card that contains something your role can't do is refused as a whole.

Booking spots. A card that adds people who take bookings shows how many booking spots that adds and whether your plan includes them. If it doesn't, the card offers the same options as adding someone in Team, and applies only once your plan allows it. The chat never starts a plan or a trial for you.

Finishing your setup after sign-up

The last step of Getting started — the card at the top of the sidebar after you sign up — opens AI Chat on a few setup questions, asked one at a time. Each answer becomes a card, so you see every change before it happens.

A second business or a new branch, added later from New workspace, has its own setup: the card shows that one step for it, and its questions are about that business, whatever you finished for the first (Adding another location or a second business).

In order, it asks:

• Which language your customers read, when it isn't the one you use the dashboard in. It is your main language: your booking page, your website and the emails customers get start in it, and every name and text the chat writes for them is in it. It starts on the language set for your business; picking another changes it, as Main language in Business profile does. Other languages are added afterwards, under Also in there or in the website's Languages.
• What else you offer. Your kind of business's usual services are there to pick, or type your own. Picked services get the names your customers read them by. A length or price you don't say is an empty field on the card to fill in (Prices and durations on the card): it never guesses one. The services wait for you to apply the card.
• Whether you have an old website. Give its address and it reads the texts on it and writes your about text, bios and service descriptions from them, in your main language. It asks before adding any service the old site lists that your booking page doesn't have. Its photos come over when you bring the old site into the website itself (Your website).
• How long you've been at it, and what customers come back for. From your answer it writes your about text, your bio and a description for each service. What you tell it, such as the year you started, goes in as you said it; nothing else is invented.
• With a website: the design (keep it, or look through the other designs over the chat and use one), photos of your work (from your phone or computer, into your website's gallery), where customers park and how they find the door (on your website's contact page), and whether to publish your website.

A barber is asked what else the barbershop offers, with beard trims and hot towel shaves to pick; a physiotherapist is asked what else the practice offers, with initial assessments and follow-up sessions.

Skip any question. Finish later keeps your place: the sidebar's Getting started card brings you back to the question you left. A question already answered another way isn't asked — an old website's texts answer the one about you, and a website already published isn't offered again. Texts and website changes apply at once and keep an Undo (Texts are applied at once).

Texts are applied at once

A card that only writes texts — a team member's bio, your about text, service descriptions — or only your social links or your Google Maps link is applied the moment it appears, without a button: these are words you can read straight away and change back just as easily. The chat says where they show, Undo under the changes puts the old texts back, and on the AI Chat page the preview of your booking page opens beside the chat (or stays on the page it already shows) so you see them in place.

A change to your website's draft is applied the same way, the moment it appears — it is private until you publish (see Your website).

A card with anything else on it — a team member, a price, working or opening hours, a booking setting, an add-on, your logo or brand colour, a booking — waits for you to press its button, even when it also writes texts. A coach asking for placeholder bios sees them on the booking page at once; a salon adding a stylist and her bio presses the card's button first.

After you apply. The chat lists what changed, each with a link to where it lives in the dashboard. If something fails partway, the card says so and lists the changes that did happen. A change that applies itself — texts, social links, the Google Maps link, the website — isn't left on screen as a card: the list shows each new text under its name, and on the AI Chat page a website change can be opened in the preview beside the chat.

Every card shows what it will set up in full: for a service, its length and price, who does it, and the resources it needs; for a resource, the services that use it; for a new team member, the services they do. Once you apply it, each line opens what it made, in a new tab.

Add-ons

Ask what an add-on does ("what does the waiting list do?") and the chat answers from its help page and says whether it is on in your branch, with links to its page and its settings. Ask it to switch one on or off, or to change a setting ("stop sending reminder SMS", "show our reviews on the booking page"), and it shows a card first, like any other change. Every add-on is free; SMS are the exception that needs a paid plan, and the card says so when nothing would be sent. Where SMS are not available yet in your business's country, the chat says so instead of switching them on.

Your logo and brand colour

Ask it to change your logo ("let's change the logo") and it shows a card with an empty place for the file: choose it there, or drag it onto the card or anywhere in the chat. An image you drag in before asking waits in the message box and goes onto the card by itself. The chat never sees the picture.

That is the only thing a picture in the chat can become. A screenshot tells the chat nothing — it can't see it, says so, and asks you what it shows — so describe the booking or the screen instead.

A card with a new logo first asks how many versions of it you have, and changes with your answer:

• One logo — the same file on every background. The card reads whether the artwork is dark or light and picks for you: a white logo gets a dark tile on light pages, and a dark one a light tile in dark mode. You can turn that round on the card. A dark logo gets an Add a white version button that adds one straight from the card. Picking one logo when you already have a version for dark backgrounds removes that version when you apply the card.
• Two versions — one for light backgrounds and one for dark. The card has a place for each, drawn on the background it is for, and each sits on its own background as it is — never on a tile, even where your old logo had one.

Once the files are on the card, it shows your logo on a light and on a dark background, exactly as it will look there, and says under each where that is: your booking page and emails on light, your booking page in dark mode on dark, and your website under whichever its background is. Nothing changes until you apply the card.

Ask for a new brand colour and the card shows the old and the new. The brand colour is your booking page's buttons and highlights and your emails'. A colour too light for the white text on the booking page's buttons is never set as asked: the chat offers the same colour a little darker, and says why.

Nothing changes until you press the card's button, and Undo puts the old logo or colour back. It is the same setting as Settings → Design & Branding, where the logo and colour can also be changed by hand. Logo files are PNG, SVG, JPG or WebP, up to 2 MB.

Your booking page beside the chat

A preview of your booking page can open beside the chat: by itself when a card changes your logo or brand colour, from Preview on Settings → Website & booking page (which opens it beside the website editor instead while your website is on), or from the preview button at the top of the chat. It is your real booking page with your real services, times and prices, and you can walk it all the way to the end — nothing is booked, no email or text is sent, and nothing is remembered for your next visit. The logo goes where it goes for customers. While a change to your logo or brand colour waits on its card, the preview already shows it; after you apply it, the preview shows what was saved. The arrows step back and forward, the screen buttons switch between a computer and a phone, and the cross closes it. Drag the line between the chat and the preview to make either one wider; double-click the line to go back to the usual width. Each browser remembers the width you chose.

A chat remembers its preview: open it again from History and the preview opens where you left it.

Your website

The website editor opens on Ask Bookodile — this chat, beside a live preview of your website. Ask for what you want to see ("make it feel warmer", "add the questions customers always ask", "a photo at the top of the team page") and it changes the website's draft: texts in any of its languages, the look and the template, sections and pages, questions and answers, which services and team members the website shows and in what order, photos by their descriptions, the gallery's categories — "put the beard photos in their own category and link it to the beard trim" — and custom touches from a fixed list. It sees a photo's description and category, never the picture, so it leaves a photo with no description for you to sort, and asks you to upload one when a page needs it. In the website editor it makes photos too: one you ask for by name starts straight away, several wait on a card for your press, ten at a time, and it changes a photo that's there when you say what should change. Never photos of people, your team or the outside of your business (Ask Bookodile to make photos).

A website change is applied to the draft the moment it appears, with Undo, and the preview shows it at once — except one that deletes photos or asks whether to: starting over on a website that has photos asks whether they stay (they do unless you choose Delete), and emptying the gallery says how many go; both wait for you to press Apply. Nothing is public until you press Publish in the editor — the chat never publishes. Prices, durations, opening hours and the team come from your booking setup, so the chat changes those where they live, on an ordinary card, and the website follows by itself. Like the website itself, all of this needs a role that can open Settings.

• Your old website. Give it the address and it reads up to 20 pages of that site and rebuilds them as the website's sections, with the old words as they are and its photos (up to 40) in the places they stood — a photo it brought over from that site before is used again, not copied twice. Ask it to remove duplicate photos and it takes out every copy of the same file, keeping the one a page shows; it tells a photo your website shows nowhere from one in use. It reads the old site's version in your website's language when there is one, and offers its other languages once the website is done — and, when its header has a logo, asks whether to use that as your logo too, never setting it unasked. Facts like prices and hours are never taken from it. When there is nothing to bring over — the site didn't answer, turns away automatic readers, or draws its pages with scripts in the browser — it says which, and takes the texts pasted into the chat instead.
• Your website's texts, rewritten for your business. After taking a template with its texts, or when you ask — one page or every page — it writes each text again from your setup, in your website's language, showing each page as it goes, on one card with Undo.
• Your website's languages. Ask for one ("add English") and it adds it with every text translated — the way a local copywriter would, not word for word — on one card with Undo; services, categories and team bios follow on their own within minutes, and the language goes public with your next Publish. It is the same list as your booking page's: each language is offered on the booking page too, and its emails follow (Other languages your customers read). It removes a language with its texts, or translates one again when it reads badly, keeping every line you corrected by hand. The website's main language is your business's own, set in Business profile, not from the chat.
• Your own domain. Ask how to connect a domain, or whether it is working, and it checks what the domain answers right now and says what is wrong, one step at a time. It never connects or disconnects a domain — that is done on Settings → Website & booking page.
• Switching the website on or off and changing its address are done in Settings, not from the chat.

Undo

Undo under the changes reverses the whole card, for setup and add-on cards. It only reverses what nobody has changed since: a team member or service that already has a booking, or a setting changed again afterwards, is kept, and the chat says which. A website change's Undo puts the draft back as it was, unless the draft has been changed again since.

Cards that move, cancel or hand over bookings, block time or mark someone away have no Undo — people may already have been told. Change those back in the calendar, where blocked time is also removed.

Moving or cancelling a booking

Ask it to move or cancel a booking ("move Declan's 9:30 tomorrow to 14:30", "cancel the 10:00 on Friday") and it finds the booking, then shows a card first.

• A visit moves as one. When a customer booked several services one after another, the whole visit moves together and keeps its shape: each service keeps its length and the gaps between them. A barbershop's beard trim, wash and hot towel all move; so does a physiotherapy session with a massage after it. You can cancel just one service of a visit and keep the rest.
• The card shows what will happen: every service, its old time and its new one, in your business's time, and anything the new time clashes with: a team member who isn't working, already has a booking, or is on time off; blocked time; the business being closed; a resource that isn't free. It says who and when, never whose booking it clashes with. You can still move it there on purpose, as in the calendar.
• Telling the customer. The card has an Email tick and an SMS tick, each shown only where that way can reach the customer: email when they have an address; SMS when your business sends SMS about changes, your monthly SMS cap isn't reached, and the customer has a number and hasn't turned your SMS off. A few words of your own go in the email; the SMS is a short set text with a link. The team members whose services moved are told as when you move it in the calendar.
• Nothing changes until you confirm. If the booking was changed by someone else after the card appeared, or something new now clashes, the card says so and changes nothing; ask again for a fresh card.
• Who can. Your role needs the permission to change bookings. If your role shows you only your own bookings, you can move only a visit one of your own services is in.
• No Undo. The chat links to the calendar, where you move it back.

Links and asking from anywhere

When the chat mentions a screen, it links it, and every link opens in a new tab, so the chat stays where it was.

Customers and bookings in an answer are things you can open: point at one, or tap it, for a small card. A customer's card shows their contact details and next visit, with Open customer and Mention in chat. A booking's card shows when it is, the service, the team member, its status and the customer, with Open booking (the booking itself, opened over the chat, exactly as the calendar opens it), Open in calendar (the calendar opens on that day with the booking open), Open customer, and Move or Cancel, which start the message for you; the change itself still happens on a card you confirm. You see only customers and bookings your role lets you see.

You can also ask from anywhere. The croc button at the top of every page opens the chat beside the page — from the bottom on a phone — and it knows which page you are on, so "what does this switch do?" needs no explaining. Open in full takes the conversation to the chat page. Or open the search (⌘K, or Ctrl+K), type your question and choose Ask Bookodile.

Moving many bookings at once

Ask for several at once ("move all of tomorrow to next Monday", "cancel Friday afternoon") and the chat shows one card with every booking: its time now, its new time, the customer, and anything the new time clashes with. Untick any you want to leave, and confirm once.

Ask to move them to part of a day ("move this morning to the afternoon", "move them to 4 pm") and the chat puts each booking at the first time it fits, with the same team member, one after another. It never gives one team member two customers at the same time. A booking with no free time then stays where it is, and the card says so; ask the chat for another day. Before it suggests a time, the chat checks it against the calendar the way the Move button does: working hours, time off, blocked time, other bookings, and any room or equipment the booking needs. If one of them was changed by someone else in the meantime, or meets a new clash, that one is left as it is and the chat tells you which; the rest still go.

The card can tell every customer by email, SMS or both, as for one booking, with a few words from you at the top of the email; the chat writes them in your main language and you can change them on the card. Each email goes out in the language its booking was made in, while those words stay as written.

Blocking time

Ask the chat to block time ("block tomorrow from 2 to 5, I'm going for lunch", "close on Friday afternoon", "room 2 is out of use tomorrow morning") and it checks the bookings already in that time first. If there are none, it shows a card with the blocked time; confirm, and nobody can book it. If there are bookings, it tells you which ones and asks what to do with each: move it (by default to the first free time after the blocked time), give it to a colleague who does that service and is free then, cancel it, or keep it in the blocked time. Then one card blocks the time and makes those changes together when you confirm. A booking with nowhere free to go stays where it is, and the card says so.

It can also block time that repeats — "block my lunch 12 to 1 every weekday", "every other Friday afternoon off until the end of June", "the 1st of every month". That is one repeating block, as in the calendar (Repeating blocks): the card shows how often, on which days, when it ends and the next few days it blocks. A repeating block never moves bookings. If some are already in its times, the chat tells you how many and which come first and asks whether to block anyway; they stay where they are. To move some of them, ask the chat to move those first.

It blocks your own time unless you name someone else, a resource, or the whole business. Blocking someone else's time, a resource, or the whole business, and changing the bookings in it, need the permission to change bookings. Without it you can block your own time and keep what is in it. For whole days away, use time off in your vacations instead.

It checks the bookings your role lets you see. If your role shows you only your own bookings and you block a colleague's time or the whole business, the chat can't see the bookings in it and they stay inside the blocked time — check the calendar first.

When you can't work

Tell the chat you're ill or away ("I'm ill tomorrow, hand my bookings over") and it finds, for each of your bookings on those days, a colleague who does that service and is free at the same time, and shows them all on one card. Bookings nobody can take are listed and left as they are; ask the chat to move or cancel them. The card can tell the customers by email, SMS or both, with a short note in the email, and mark you away on those days so nobody can book you. A manager can hand over someone else's bookings, but only that person can mark themselves away. If your role shows you only your own bookings, you can hand over only your own.

Naming a customer

Type @ and the first letters of a customer's name to pick them from a list. The customer becomes a chip in your message: one item, removed whole with Backspace. The chat sends the AI a reference instead of the name, and shows you the name. You find only the customers your role lets you see.

If you type a customer's full name as it is on their card, it is sent the same way, and a line under your message says so. If you write it in another form (in Slovak or Czech, "Sofie Martinez" for Sofia Martinez), the chat asks "Did you mean @Sofia Martinez?" and changes nothing until you pick. A team member's name is always sent as written.

Any other name you type does reach the AI.

Naming a team member

Type @ and a team member's name to pick them as well: they are listed under Team, apart from customers, and shown in another colour, so a colleague never reads as a customer. A team member's name is sent to the AI as written, as it always is.

In an answer, the team members it names are highlighted the same way. Point at one, or tap it, for how many bookings they have today and when the next one starts, with Open team member, Open their calendar (the calendar opens on their bookings only) and Mention in chat. Only a name written exactly as on the team is highlighted.

All branches

In All branches, the organisation owner can ask the chat to compare the branches — opening hours, team, services and prices, booking settings, and how many bookings each had in the last 30 days and has in the next 7 — and to copy services, opening hours or booking settings from one branch to another. A copy is a card for the branch it goes to, applied and undone like any other.

It doesn't copy team members, resources, prices set per team member, categories or combinations of services. A service the other branch already has, with the same name, takes the copied price and duration. A new service is done by everyone at the other branch who takes bookings.

For anything about one branch's bookings or free times, switch to that branch. Anyone other than the organisation owner gets help answers only in All branches.

What it can't see

The AI never reads your customers' names, emails or phone numbers from your data. When it talks about a booking, it refers to the customer by a code, and the chat shows you the name, only if your role lets you see that customer; anyone else reading the chat sees "a customer". It doesn't read booking notes. If you type an email address or a phone number into the chat, it is replaced with [email] or [phone] before the AI reads your message. A name you type reaches it unless you pick the customer with @ (see Naming a customer).

Speaking instead of typing

The microphone button in the message box records you, up to two minutes, and turns what you said into text in the box. Nothing is sent until you press send, so you can fix a word first. What you say is turned into text before anything is replaced, so a name or number you say reaches the speech provider.

It hears the language your dashboard is in: English, Slovak, Czech or Vietnamese. Your browser asks for permission to use the microphone.

Your chats

History at the top lists your most recent chats; you can open or delete any of them, and New chat starts again. A chat is deleted 180 days after its last message.

A chat stays where you started it. History shows the chats from the branch you're working in — or, in All branches, the ones started there. If you work in more than one branch or more than one business, a chat started in one of them is listed, and continued, only there: switch to it to carry on. A business never sees a chat from another business, even when the same person writes in both.

Who else can read them. The people who manage your business: by default the Owner and Manager roles, through the permission "Read the team's AI chats", which the business can switch on or off for any role. They read a chat only from the branch they're working in, and never one that looked up something their own role couldn't see. They can't write in it. The workspace owner can always read them, and only they can read chats started in All branches. The chat tells everyone who can't read others' chats that these people can read theirs. See Roles and permissions.

What a chat changed stays in its record for 180 days, even if you delete the chat.

If you leave. When a team member's access is removed or they are switched inactive, they can no longer open, read or delete the chats they wrote at that business. The business keeps them: the people above can still read them, as before. Switched back on, the team member sees them again.

Where your words go

The chat runs on an AI model hosted in the EU, and asks every host not to keep or train on what you send. When that host is busy, the same model answers from another host, which may be outside the EU; a question that changes nothing may also be answered by the same model's previous version. The chat never sends your customers' names, emails or phone numbers from your data (see What it can't see for what you type). Speech is turned into text in the EU. Bookodile doesn't keep your recordings, only the text you send.

Limits

• It can be wrong. Check anything that matters against the screen it points you to.
• It doesn't write to customers in Messages. The only messages it sends are the ones a booking card sends about a change, as the calendar does.
• It can't create a booking, or move one to another branch.
• For add-ons it switches them on and off and changes their settings; it doesn't create discount codes, vouchers, events, promotions or announcements, or set revenue-split percentages — it points you to the page for those.
• It doesn't set prices per category of team member; set those in the service.
• It doesn't see your logo or any image you give it: it reads only whether the artwork is light or dark, to pick its background. On your website it works from each photo's description.
• It doesn't publish your website, change its main language, switch it on or off, or connect a domain; those are in the website editor and in Settings.
• It doesn't read payments or the statistics screens. It ranks customers by spend and visits, nothing more detailed than that.
• One card holds at most 40 bookings or visits. One look at the bookings covers at most 14 days — or the 10 latest, however far back — a hand-over at most 14 days, and blocked time at most 31.
• It compares at most 12 branches at once.
• It reads the last 20 messages of a conversation; for something older, say it again. History lists your 30 most recent chats in the branch you're in.
• Each organisation has a daily allowance, shared by every branch, which the microphone uses too. When it is used up, the chat says so; it starts again at midnight UTC. Each person can send ten messages a minute. On a very busy day the chat can also take a break for everyone until midnight UTC, and says so.
• In a demo workspace, a card shows what would change but can't be applied, and each visitor can send 15 messages a day.
• Speaking works in English, Slovak, Czech and Vietnamese, in the language your dashboard is in, up to two minutes at a time.