This Preview explains a safe next step; it does not create a ticket or transmit information.
SmoozenExplore
Smoozen support
Clear escalation paths for client teams.
The Preview support surface provides guidance only. It does not create a ticket or transmit information.
Support boundary
Route the concern without creating a new data path.
Share only the minimum useful context and remove secrets or sensitive records before contacting support.
A live safety or canonical-record event belongs in the client’s established incident workflow.
Choose the safest next step
Give the team enough context to help safely.
Choose the path that matches the work, then keep the message limited to the minimum useful detail.
Explore a workflow
Share your client category, desired module, and operating model before sending any implementation detail.
Start with contextReport a Preview issue
Include the environment, tenant reference, approximate time, affected module, expected result, and a redacted reproduction.
Keep it reproducibleEscalate a sensitive issue
For privacy, security, safety, payment, or canonical-record concerns, stop the affected capability and identify the authorised incident owner.
Use the incident ownerSafe support pattern
Triage should reduce risk, not create a new data path.
Context first
Name the client, environment, capability, and approximate time so the right team can understand the scope.
Redact before sending
Remove credentials, health information, payment details, identity documents, private messages, and unredacted customer records.
Keep authority clear
Support can help route a concern, but the client remains responsible for its safety, consent, canonical records, and final communications.
Include
Client name, environment, tenant reference, approximate time, affected module, expected result, and a redacted reproduction.
Never include
Passwords, tokens, API keys, health information, payment data, identity documents, private messages, or unredacted customer records.
Client-owned safety path
Review security boundaries A live safety event belongs in the client's established escalation workflow.
Support can help route a product concern, but it does not replace the client's safety owner, emergency process, consent record, or canonical system of record.