Activity — who changed what, and when

Activity is a record of everything that changes in your account: a booking made, moved, handed to someone else or cancelled; a customer's card edited; a price changed; someone's hours or time off; a setting switched. Each change says who made it, how and when, so a question like "why is this customer booked at 10?" has an answer instead of a guess.

It is part of every account, for everyone on the team. There is nothing to switch on: Activity is in the menu (under More).

What a change says

Every line has:

• What happened — "Booking moved", "Booking cancelled", "Service edited", "Time off added", "Settings changed"…
• What it is about — the service and the customer for a booking, the team member for their hours or time off.
• What changed, from → to — the time, the team member, the price, the status, which day's hours, which booking rule.
• Who did it, by name — or Customer when the customer did it themselves, or Automatic when nobody did it by hand.
• How, when it is not the dashboard — "via AI Chat", "on the booking page", "with the link in their email", "in My Bookings", "from the waiting list", "online payment".
• When, in your business's time zone.

Changes are grouped by day, newest first. Several services of one visit changed together — a visit of a cut and a beard trim moved at once — read as one line with both services under it.

Who made a change

• A team member — anything done in the dashboard, under their own sign-in. When they asked AI Chat to do it and confirmed the card, it says "via AI Chat", still under their name: the chat never changes anything on its own.
• Customer — the customer booking on your booking page or the widget on your website, cancelling from their confirmation email or from My Bookings, taking a place offered from the waiting list, signing up for an event, or opting out of review or feedback requests from an email. When someone on your team books for a customer on your booking page while signed in, it is under their name instead.
• Automatic — something nobody did by hand, such as an online payment confirming or refunding a booking.
• Bookodile support — a correction made directly by Bookodile.

Finding one booking's or one customer's history

• One booking: open it in the calendar. The last change is at the top of the booking window — what happened, who did it, when — and History opens the rest in place: the whole visit (every service booked with it) and what the customer was sent about it. A booking with nothing recorded since the activity log started shows no line.
• One customer: open the customer and press History.
• One team member: open them and press History — changes to their bookings, hours and time off, whoever made them.
• One service: History at the top of its page.
• Everything else: on Activity, narrow it by what changed (bookings, customers, services, team, settings), by who made the change, by whose bookings they were, or by day.

Export CSV on Activity downloads what the filters show, up to 5,000 changes, in your language — for a dispute with a customer, or your own records.

A worked example. A hair salon's customer says they booked 10:00, but the calendar shows 11:00. The booking's history says the customer booked 10:00 on the booking page on Monday, and the receptionist moved it to 11:00 on Tuesday. The same question at a gym — "why is this member in the evening class?" — reads the same way: who put them there, and when.

Asking AI Chat

AI Chat reads the same log, with your own access. Ask it in your own words:

• "Why is this customer booked at 10 tomorrow?"
• "Who cancelled the 3 pm?"
• "Who changed the price of a haircut?"
• "Who turned the reviews off?"
• "What changed in the bookings today?"

For one booking it also says when and how the booking was first made — on the booking page or in the dashboard — which holds even for bookings made before the activity log started.

What the customer was sent

A booking's history also lists the messages sent to its customer about it: the confirmation, reminders, the new time after a move, a cancellation, the thank-you after the visit, a review request, a place offered from the waiting list — and whether each went by email or text, or did not go through. These come from Bookodile's record of what it sent; nothing extra is stored for them. Messages you write yourself are in Messages.

What is recorded

• Bookings — made, moved (a new time), handed to another team member, a different service, resource or customer, confirmed, cancelled, marked completed or no-show, a price or discount change, a payment changing its payment status, a late cancellation, a note edited, deleted. Blocked time added, changed or removed — a repeating block is one line when it is added, ended or deleted, not one per repeat.
• Customers — a new card, tags, marketing and privacy consent, opting out of texts, messages, review or feedback requests, the name, email, phone or address edited, a note edited, the card deleted.
• Services and resources — added, deleted, and changes to the name, price, how the price is shown, pricing, duration, the break after, deposit, paying online, category, whether it is active, and how many extras a booking can have. A resource's name, capacity and whether it is active.
• Your team — someone added or removed, their role, category, whether they are active and take bookings, their working hours day by day, their name or photo changed, their profile edited, time off added, changed or removed.
• Settings — the location's name, booking page address, time zone, currency, customer languages, country, opening hours day by day, every booking rule (minimum notice, how far ahead, free cancellation, required email or phone, automatic confirmation, time slots, search engines, privacy consent), paused notifications, Google Calendar sync, and every add-on switched on or off.

Who sees what

You see the history of what you can already see — nothing more:

• Bookings — someone who sees every booking sees every booking's history. A team member who sees only their own bookings sees only those bookings' history, including a booking handed to them or taken from them.
• Customers — the history of customers' cards needs access to every customer.
• Services — everyone working at the location.
• Your team — everyone who sees the team. Each person always sees changes to their own hours and time off.
• Settings — everyone with access to Settings.
• The owner sees everything, at every location.

What each role can see is set in Roles and permissions. Nobody — the owner included — can edit or delete a line of the history.

Limits

• History starts the day the activity log was switched on (October 2026). A change made before that is not in it, and a booking made before then has no history line. For an older booking, AI Chat can still say when and how it was made.
• History is kept for 24 months, then removed automatically, every night. There is no setting to keep it longer.
• The words of a note are never recorded, only that it was edited — a customer's note, an internal note, a reason for cancelling or blocking time, a team member's profile, the privacy consent text. The same goes for a customer's contact details: the history says the phone was edited, never the number.
• Some things are not in it: changes on the website editor (it keeps its own History), conversations in Messages, reviews and feedback, individual payment records (see Payments — a payment shows as the booking's payment status changing), prices and lengths set per team member or per category, which team members do which service, what a role is allowed to do, and billing.
• A customer editing their own details in My Bookings is not recorded — those are their details, not the business's.
• Deleting all data or a whole location in Settings → Data is not recorded line by line, and a deleted location's history goes with it.
• Demo workspaces start empty. They reset every night and the reset is not recorded; anything you change in a demo shows up under your name.
• When a customer card is deleted, the changes stay but stop pointing at that customer: their bookings' history no longer says whose they were.