Appointment Activity Log: Track Booking Changes in FindSlot
An appointment activity log helps a service business answer a practical question: who changed this, and what changed? FindSlot's Activity Log brings supported appointment and business-setting changes into a readable history, with filters for the person, category and date.
For owners and managers, this adds context when a booking moves, a service changes or a different person takes over the front desk. Instead of relying entirely on someone's memory, you can review the recorded action and then check the current record.
What is an appointment change history?
An appointment change history records supported actions that affect a booking, such as rescheduling, cancellation or reassignment. It answers a different question from a client's appointment history: the client profile shows their booking relationship, while the activity log explains recorded changes made along the way.
You may also see this described as a booking audit trail. In FindSlot, that means the supported operational entries described here, with 60-day retention. It does not mean an exhaustive or permanent compliance archive. For the client's visits and upcoming appointments, use client profiles and booking history.
Where to find the Activity Log
Open Settings → Activity Log in FindSlot. Owners and managers have access by default. Other roles need the relevant permission to view it.
The log is available across FindSlot plans. Access is controlled by permissions, so inclusion in a plan does not mean every employee can read the business's activity history.
Entries use sentences that describe the action, with additional before-and-after details where recorded. Category, person and date filters help narrow a busy log to the change you are investigating.
Which appointment changes are recorded?
The Activity Log covers supported appointment actions such as acceptance, decline, cancellation, rescheduling, reassignment and changes to Missed or Completed status.
That makes it useful for questions including:
- Was the appointment moved to another time?
- Did a client cancel, or did someone on the team make the change?
- Was the booking reassigned to another provider?
- Was a missed appointment recorded correctly?
- Did the business accept the request before preparing for the visit?
Read the activity entry alongside the actual appointment. A history entry explains an action at a point in time; the current appointment shows the latest state.
For example, a rescheduling entry followed by a cancellation means the appointment was moved and later canceled. Reading only the earlier change would give an incomplete picture.
Business settings have a history too
Booking problems do not always begin with the appointment itself. A different service duration or a changed staff schedule can affect what the team expects to see.
FindSlot's Activity Log also covers supported changes to services, staff, roles assigned to staff, saved schedules, clients, booking links, booking-form fields, company settings and calendar connections.
Booking-page design and the FindSlot badge setting appear as separate fields in the recorded changes. This can help an owner understand which setting changed without treating every update as an unexplained edit to the whole company.
Saved schedules generate an entry when something actually changed. The aim is a useful account of changes your team made, rather than a record of every time someone opened a screen.
Read the actor before drawing a conclusion
The actor indicates where the recorded change came from. Depending on the action, you may see a staff member's name, Client, System, or FindSlot support.
These labels have different meanings. A System entry can reflect automated work rather than someone using the booking interface. A Client entry is different from a staff member making a change after a phone call.
Treat the label as the start of the investigation. Open the relevant record, look at the time and read the action before assuming why the change happened.
A calm review is more useful than a blame exercise. The purpose is to establish what the system recorded, correct any remaining problem and make the next handover clearer.
A simple process for investigating a booking change
Suppose a client believes they have a 10:00 appointment, but the team sees a different time. Start with the current appointment, then use the log to understand how it reached that state.
- Confirm the appointment. Make sure you are checking the right client, date, service and provider.
- Narrow the activity date range. Use the business's local dates around the expected change.
- Choose the appointment category. Reduce unrelated service or company-setting entries.
- Review the actor and action. Read the relevant change and its before-and-after detail.
- Check for later changes. Another action may explain why an earlier entry no longer matches.
- Resolve the current booking. Agree the correct arrangement with the client and save it in FindSlot.
If the issue was unclear communication, review your appointment confirmation messages. If it came from a late change, make sure the team understands the rescheduling policy.
The log supplies context for these decisions. It does not make the customer conversation unnecessary.
What the Activity Log does not cover
The current business-facing log is selective. It does not include appointment notes, edits to custom role definitions or staff-to-service assignments.
That means the absence of an entry is not proof that every aspect of a record remained unchanged. If you are investigating one of those areas, inspect the current configuration and check with the responsible person.
The business-facing view also does not show IP addresses, browser details or request identifiers. It is designed around readable operational changes.
The log does not provide an undo button. If a setting or appointment needs to be corrected, use the appropriate controls to make a new, deliberate change.
How long are entries available?
FindSlot keeps activity entries for 60 days. Use the log for recent operational questions and handovers, and investigate problems while the relevant entries are still within that period.
It should not be treated as a permanent archive of every booking-related event. The current feature does not promise indefinite retention or a comprehensive compliance record.
The original action text remains useful when a related record is later renamed or deleted. A historical sentence describes the recorded action at the time; check the present record before relying on its current name or status.
Build a clearer team handover
A useful handover combines three things: current appointments, accurate staff availability and a short explanation of any unusual changes.
The Activity Log supports the third part. A manager can review recent changes before taking over, then concentrate the handover conversation on unresolved questions rather than reconstructing every routine action.
For a small team, start with one habit: review the relevant log entries when a booking discrepancy appears. You do not need to read every event every day.
Frequently asked questions
How can I see who rescheduled an appointment?
Open Settings → Activity Log, select the relevant dates and appointment category, then read the rescheduling entry and actor. Check for later changes and compare the history with the appointment's current time.
Can every employee see the log?
No. Access requires the appropriate permission. Owners and managers have it by default.
Can I recover a deleted record from an entry?
An entry may help explain what happened, but it is not a restore function.
Is the log available on the Free plan?
The Activity Log is included across plans. User permissions still determine who can view it.
Does it record every action in the application?
No. It covers the supported changes described above. Opening a screen or changing an excluded field is not the same as a recorded activity event.
Next step: Open Settings → Activity Log, choose a recent date range and review a recorded appointment change. See FindSlot features and current plans for the wider booking workflow.