Don't just tell an auditor you're compliant. Show them.

▸ WHAT'S ACTUALLY IN THE FILE

Pick a campaign and a date range, and DialerSeat generates a CSV — nine columns, one row per call. Here's a real excerpt of the format:

▸ PHONE NUMBERS ARE MASKED BY DEFAULT

Every export redacts the lead's phone number automatically — area code visible, the rest masked (+1713XXXXXXX). This is the default specifically because a compliance export is often handed to someone outside your organization — a client, an auditor, a lead vendor — and there's rarely a reason that third party needs the full number to verify your calling behavior. Full, unmasked numbers can still be pulled when genuinely needed; masking is the default, not a hard limit.

▸ WHO CAN GENERATE ONE

Only a campaign's owner can export its compliance record — the same permission boundary as every other campaign-level action. On a Manager+ team, that means the owner can pull a record for any campaign they created; it's not something an individual agent generates for a campaign they're just dialing on.

▸ WHEN THIS ACTUALLY GETS USED

• A lead vendor asking for proof. If you're buying leads under a contract that requires demonstrating TCPA-compliant handling, this is the receipt.
• An internal audit before a busy quarter. Pull the last 30 days on a predictive campaign and check the abandon-rate column directly instead of trusting the dashboard summary alone.
• A regulatory inquiry. If a complaint ever traces back to a specific call, the export gets you to the exact record — timestamp, disposition, and recording link — in minutes, not a support ticket.
• Handing off to a client. Agencies running campaigns on behalf of a client can share a redacted record without exposing their client's full lead list.