A received message can contain more than the information your team needs to handle the request. Devotel Orbit now lets workspace owners and admins use Redact PII on an eligible received message to permanently erase its body, media, and sender and recipient phone numbers while retaining billing records.
This is a message-level erasure action, not a live content filter: it does not mask selected PII classes before an agent reads a message, and it does not apply class-by-class rules. You decide which eligible message to redact. The action removes the listed content together, so review the message and your retention process before confirming.
Where it fits in your privacy controls
Received-message redaction complements, rather than replaces, other controls. The PII egress guard for AI agents can scrub supported identifiers from an agent's tool arguments before dispatch when you enable it. The tenant-authored guardrail DSL lets you define rules for agent input and output. These controls address different stages; neither changes what the received-message Redact PII action erases.
Your team owns when to use these controls for each channel and workflow. For example, a healthcare intake team may redact a received message after transferring the required intake details to its approved record, while a payments team may redact a message containing a card number after handling the request. These are operational examples, not automatic policies or pre-agent masking configurations; follow your own retention and review requirements.
What to expect
The dashboard action is available to owners and admins on eligible received messages. Confirming it permanently erases the message body, media, and both phone numbers; billing records remain. Redaction is not reversible. It does not cover every identifier or let you choose individual PII classes, and it cannot prevent an agent from seeing content before the message is redacted. The action does not detect or match values with regex or heuristics; because it erases the full message content, review the selected message before confirming.
For the product's security and privacy posture, visit Trust. For healthcare controls and shared-responsibility context, see the HIPAA checklist and the on-demand message redaction guide.