Activity log

The Activity log answers "who changed what, and when?" and, more widely, who did what.

Owner & Manager Where: Activity 5 min read

It's a newest-first trail of what happened across your business — setting changes, your team's actions, and visitors joining or leaving. By design, it never shows a visitor's personal details.

What it records

Setting changes — a setting flipped, a line renamed, a role changed, a counter added. Your team's actions on the queue, such as calling, completing or holding a visit. Visitors joining or leaving. And a few money-related choices: when someone downloads a report file, and when someone turns extra visits or any pack on or changes its monthly limit. A pack entry shows who did it, when, and the exact words they ticked.

Each row shows…	…which is
When	With the date, the time to the second and the time zone of the device you are looking at, which is named in the column heading.
Who	Who did it — "System" when it was automatic.
What happened	In plain English.
What it applied to	The setting, line, role or counter it touched.

Click a row for the full detail, including the raw action code.

Who sees it

Who	What they see
Owners and managers	The whole business.
A manager	The log too (unless the owner has switched off “See the activity log” for managers), scoped to the locations they manage, plus anything they did themselves even if it touched the whole business (like inviting a teammate) — never another person's business-wide changes.

Changed the wrong setting? Put it back

A setting change records what it was before as well as what it became. Open the entry and, if it can be undone, you see exactly what would be restored and a Put back button. A small Can be put back badge on the row tells you without opening it.

Can be put back	Why / how
Line settings	Everything saved in Line settings — capacity, party size, timeouts, appointment rules, the TV and rating switches, ticket numbering, which channels the line uses.
A line's open hours	The whole week and its one-off days go back to the schedule from before the change.
A location's details	Its name, the language visitors are messaged in, the check-in rule, the Google-review settings and the business's own privacy notice.

Not covered	Why
A location's time zone	Changing it moves your upcoming appointments to a different local time, and has its own warning. Change it back deliberately.
The reply-to email	An address is personal data and is never written to the log, so there is nothing to put back.
The serving order mode	Switching it on a live line reorders who's next and has its own confirmation.
The running-late banner, branding, messages, billing, team changes	Their own tools undo them — the banner clears in one tap, and removed team members can be restored from the Team page.
Older entries	Anything logged before this existed never recorded the old value.

It only works while nothing else has changed that line or location since. If anyone has saved anything there afterwards, the entry says so and offers nothing — it can never overwrite somebody's later work. Change the setting by hand instead.
Once only. The entry then reads that it has been put back, and the put-back is logged as its own entry naming the change it undid.
Only for someone who could have made the change — the owner, or the manager of that location. A manager cannot put back a change at another location.
No visitor details, ever. Only plain settings are kept: numbers, switches, short choices, and the business's own published notice.

Finding an entry

Search by action, target or person.
Filter by Action, Person, Target type and, with more than one location, Location. From and To pick real dates.
A date range can be up to 3 months at a time. If you pick a longer one, the page says “Up to 3 months at a time — pick a shorter range.”, the calendar greys the days that are too far, and the list and the downloads wait until you pick a shorter range. With no dates picked you get the plain newest-first list.
Filters survive a refresh — a link to "what changed last Tuesday" keeps working.
Clear filters resets it, with a live count of what's shown.
The list loads the most recent 500 entries at a time. If there are older ones, a note above the list says so, and a Show older entries button under the list loads the next page.
Download has an Excel button and a PDF button. Each saves what your search, filters and dates match, newest first, as a file. A very long list is cut at the newest entries, so narrow the dates to get the older ones. The file shows times in 24-hour form in the business time zone.
A line under the list says entries are kept for 1 year.

No visitor data

Rule	Detail
What it's about	Your configuration, not your visitors — it never contains a visitor's name or contact.
When an entry touches a visit (a call or a transfer)	The visitor is referenced by their ticket number only — "A012", never a name — because the trail is kept for one year, far longer than visitor details are.

Need to act on a visitor's personal data? That's handled separately, under Visitor data requests.

Chasing an unexpected change? Filter by the person and the day, open the entry, and you'll see exactly what was set — the fastest way to answer "who turned this off?"

Counters that changed hands, contact changes

What happens	What it means
Counters that changed hands	A list under the log, headed “Counters that changed hands”. It lists the times somebody left a counter other than by signing out — taken over by a colleague, moved to another counter, removed from the team, or timed out because nobody signed out — and why. It follows the page's date filters; with none set it shows the last 30 days. A shift that simply ended with a sign-out is not a hand-over and is not listed.
A visitor's contact was changed	The entry says staff did it at the visitor's request, and shows the old and new address unless the data was erased.

What happens

What it means

Counters that changed hands

A list under the log, headed “Counters that changed hands”. It lists the times somebody left a counter other than by signing out — taken over by a colleague, moved to another counter, removed from the team, or timed out because nobody signed out — and why. It follows the page's date filters; with none set it shows the last 30 days. A shift that simply ended with a sign-out is not a hand-over and is not listed.

A visitor's contact was changed

The entry says staff did it at the visitor's request, and shows the old and new address unless the data was erased.