Skip to documentation
Merchant app
Browse chapters

Chapter 15 of 23 · Updated 22 October 2026

Activity logs & history

Find past visits and understand recorded actions and access scope.

Location: Merchant Account > Activity Logs. Token-specific history is under Reports > Token History > Token Audit. Queue Dashboard History is a permission-controlled customer/visit tool, not the owner's complete account audit console.

  1. Open Activity Logs and check its date/filter scope.
  2. Identify the action label, actor and time. Open or read the item details where offered.
  3. Cross-check the token or service involved using its number/ID and business day.
  4. Keep the approximate time/action description if support is needed. Do not send an entire unredacted customer list.

Recorded activities can include owner/service/staff/account changes, queue actions and billing/device events, depending on the emitting workflow. Not every button press or customer read of a link becomes an audit entry. A failed action may leave a failure record instead of a successful state change. A real-time screen and a history report need not refresh at exactly the same moment.

Token Audit includes Customer Info, Counter/Staff, Performance Metrics, Services & Billing, Customer Feedback and Audit Trail as data is available. Issue, call, service-start and completion times are different timestamps. Historical custom answers are saved with the token; renaming a current field does not rewrite what was collected earlier.

Customer-facing activity-log retention and a merchant download-all-log control were not verified. Internal operational job logs are not customer activity logs and are not a menu customers should use. Use the privacy policy for retention context and support for a specific access request; do not promise indefinite history.

Edition 1.0. Use the controls available in your account. Get help if a step is unavailable.