Incoming message received
The channel, thread and routing context can be attached when a message enters the workspace.
AUDIT HISTORY
Traceable history for AI-assisted messaging workflows.
Enabled workflow events can be recorded with available message, reviewer, rule, channel and timestamp context, subject to workspace configuration, plan capabilities and provider support.
WHAT VERBUM RECORDS
Typical audit events may include
Illustrative event categories, subject to enabled workflow features.
Audit history is designed to make message workflows reviewable. The exact record depends on enabled workflow features, workspace configuration, plan capabilities and channel or provider support. Typical audit events may include the following.
AI draft generated
Draft creation is kept separate from human decisions so reviewers can understand what the AI produced.
Approval requested
Sensitive drafts can be routed to a reviewer with the channel and workflow context needed for review.
Approval accepted or rejected
The decision state, reviewer and timestamp help teams reconstruct how a message was handled.
Verbum Automate rule applied
Automated actions are tied to the configured rule and guardrail that allowed the workflow to proceed, where applicable.
Message sent
Delivery and channel events are recorded where supported by the connected provider.
Built to support control evidence. Audit history can support accountability, operational review, security evidence and reviewer attribution, but it does not replace customer recordkeeping, retention, legal hold or compliance obligations.
FROM MESSAGE TO AUDIT TRAIL
A reviewable trail from message to recorded event.
The value is not only that an event happened. It is that AI assistance, human or rule decisions, delivery outcomes and audit metadata stay connected without turning metadata into workflow steps.
- Channel
The customer, workplace or internal channel identifies where the message entered the workflow.
- AI action
AI-generated drafts, summaries or assistant outputs can be recorded separately from final delivery decisions where enabled.
- Human decision
Where review is required, reviewer approval, rejection or edit context can explain the human decision. Verbum Automate rule execution remains a separate event type when enabled.
- Timestamp and final outcome
Time context and the final send, hold or delivery outcome can be attached when the channel and provider support the event. Delivery and channel events are recorded where supported by the connected provider.
- Workspace/user context
Enabled events can retain available workspace, user, reviewer or rule context so teams can review workflow history later.
WHY IT MATTERS
Audit history turns messaging into reviewable operations.
Accountability
Teams can see whether a human reviewer or configured Verbum Automate rule allowed a message to move forward.
Security review
Traceable history can support security questionnaires, control review and qualified procurement conversations.
Operational consistency
Managers can review how approval rules, channels and reviewers are being used across recurring workflows.
Dispute review
Reviewable event history helps teams understand what was drafted, approved, sent or held when a conversation is questioned.
Regulated communication
Traceable records can provide evidence support for teams that need documented message controls while remaining responsible for their own obligations.
AI, HUMAN AND VERBUM AUTOMATE DECISION TRAIL
AI actions, human decisions and Verbum Automate rule executions are distinct event types.
When a message is drafted by AI, that draft event is separate from the final decision. In Verbum Assist mode, human review is attributed to the reviewer when required. In Verbum Automate mode, automated actions are tied to the configured rule and guardrail that allowed the action.
These event types are linked but distinct when enabled, helping teams understand what the AI produced, what a human decided and what a rule allowed. Accountability stays visible without treating audit history as a substitute for a customer's compliance program.
Verbum Sense analysis
Context, intent and risk signals remain distinct from customer-facing actions where enabled
AI action
Draft generated · context reference · timestamp where enabled
Human decision
Approval accepted or rejected · reviewer · timestamp where review is required
Verbum Automate execution
Configured rule applied · guardrail matched · action timestamp where enabled
AUDIT HISTORY WORKS WITH
Evidence support across the governed messaging workflow.
Approval workflows
Approval requests, acceptances, rejections and escalations become reviewable workflow events.
Review resourceSecurity
Security resources explain how traceable history supports reviewable controls and evidence support.
Review resourceTrust Center
Trust resources explain how traceable history fits Verbum's governance and security posture.
Review resourceContact security review
Request security package context through a qualified review path when supporting evidence is needed.
Review resource
MAKE MESSAGING ACCOUNTABLE
See how traceable history supports AI drafts, approvals and Verbum Automate actions.
Security package requests route through contact with security context. Sensitive evidence may require qualified review or a confidentiality process.