Skip to content
Supportman
Approvals

Create an Audit Trail for Support Approvals in Intercom

An audit trail for support decisions is not just a compliance requirement — it is the infrastructure that makes consistent policy enforcement possible. When every decision is logged, patterns emerge, outliers are visible, and accountability is built into the process.

— Use case —

The informal record-keeping approach

  1. 1Agent notes the approval in the Intercom conversation.
  2. 2Manager screenshots the Slack DM as a record.
  3. 3Finance exports refund data quarterly to reconcile.
  4. 4Discrepancies trigger a manual investigation.

The problem: Intercom conversation notes and Slack DM screenshots are not an audit trail. They are fragmented records that require human effort to reconcile and are easy to manipulate or lose.

— With Supportman —

With Supportman

Every approval request, decision, approver, and reason is automatically logged on the Intercom conversation — no screenshots, no manual notes.

  1. Route approvals through Supportman instead of informal Slack DMs.
  2. Each request records: requestor, timestamp, decision, approver, and justification.
  3. Review approval history in Supportman or read the decision directly on the Intercom thread.
Quick recap

If it did not go through Supportman, it did not happen — every approval decision lands on the Intercom conversation with who decided, when, and why.

— Common questions —

Can the audit trail be exported?

Approval history is visible in Supportman and on each Intercom conversation. Bulk export for finance reconciliation is on the roadmap — today, finance teams typically reconcile against payment system exports and spot-check conversation records.

How long are approval records retained?

Approval records stay on the Intercom conversation for as long as the conversation exists. Supportman retains approval history in the product dashboard.

Connect Slack and Intercom – that's the whole setup.