Organization alerts and signals, when available, summarize records within the organization, property, operating-unit, role, capability, filter, period, and environment currently shown in the product. They are prompts to review the underlying authorized record; they are not proof of a cause, service outcome, fraud, complaint, employee conduct, payment result, guest preference, or required action.
Confirm scope, evidence, and environment
Before acting on a signal, confirm the selected organization and operating scope, active environment, visible period or filter, source record, and available context. Live, Sandbox, and Demo records are separate. A non-live signal, activity, rating, payment, allocation, Wallet result, payout, or report does not establish the corresponding Live state.
Signal names, severity, grouping, freshness, visibility, link destinations, and available follow-up controls depend on the current product and authorized scope. Do not promise a fixed alert type, threshold, priority, real-time update, notification, cross-property aggregation, employee metric, or resolution state.
Take only the approved next step
Review the linked or underlying record using the current authorized workflow. A signal does not by itself authorize contacting a guest, employee, or external party; changing a record; issuing a refund, reversal, adjustment, allocation, or payout; publishing feedback; or opening a recovery action. Use the applicable capability, policy, consent, and operational process before taking any action.
Treat employee and guest data as private. Do not use an alert to make an employment, performance, financial, legal, or customer-service decision without appropriate evidence and authorized review. Never include payment data, bank data, identity documents, passwords, verification codes, tokens, or private guest information in an alert comment or support request.
Escalate safely
For an alert issue, provide the authorized scope, active environment, visible signal or source record, approximate time, and non-sensitive reference. Support can investigate recorded product state but cannot infer an outcome, bypass Business authorization, or expose another person’s private data.