Clients and messages

Stenz keeps client details attached to the studio that received the request. Contact information is personal data: open it only when needed for the project and avoid copying it into unrelated tools.

Client records

Client lookup and search stay within your studio. Some views deliberately mask personally identifiable information unless the current connection has the clients:pii permission. A general request-reading permission does not automatically grant access to every email address or phone number.

Correct a client record only when you have a reliable source. A correction can affect future communication but does not rewrite historical messages or legal documents.

Send a message

1. Open the relevant request or client context.
2. Choose a saved template or write a focused message.
3. Verify recipient, subject, body, and any status effect in the preview.
4. Confirm the exact send operation.
5. Check the activity record instead of sending a duplicate when the result is uncertain.

Messages that leave Stenz are external effects. Assistants treat them as confirmed actions even when the text was drafted automatically.

Sender identity

System mail uses Stenz infrastructure. Eligible studios can configure a separate sending domain and sender address from Email settings. DNS verification may take time. A custom email domain is independent from the public form domain.

Never paste passwords, authorization codes, session cookies, access tokens, full client histories, or unredacted logs into a support message. See Contact support for safe diagnostics.