The FTC already wrote your sales call report template

Almost every sales call report template in circulation is a feelings form. Date, prospect, outcome, next step, and a free-text box where a rep writes “good convo, will follow up Tues”. It is filled in from memory at 5pm, it is unverifiable, and the fields nobody can be bothered to complete are quietly dropped from the template at the next revision.

Meanwhile, if you run outbound calls into the United States, a federal rule already specifies in detail what you must record about every one of those calls and how long you must keep it. Most teams have never read it, build their template from a blog post instead, and end up with a document that is simultaneously more annoying to fill in and less complete than the one the law describes.

So here is the inversion: start from the regulator's field list, which you have to retain anyway, and add only the commercial fields that actually change a decision. You end up with a shorter report, a defensible audit trail, and — because every mandated field is machine-observable — one that mostly fills itself in.

What goes in a sales call report?

Section 310.5(a)(2) of the Telemarketing Sales Rule lists what a record of a telemarketing call must contain. It is not vague, and it is not a summary of the conversation. These are the nine field groups, in the rule's own order.

Six of those nine come straight off the telephony platform. Two come from campaign configuration set once. Exactly one — which script version was in use — needs a system that versions scripts rather than editing a shared doc in place. None of them require a rep to remember anything.

The sales call report template

Take the nine mandated fields as the spine, drop nothing, and add three commercial fields. Three, not twelve — every optional field you add is a field that gets left blank, and a report with blanks is a report nobody trusts.

That is the whole template. Twelve fields, nine of which arrive without anyone typing. The rep fills in three, all at the moment of the call rather than at 5pm, and two of those three are single taps.

Note what is not on it: call quality score, mood, temperature, and the free-text summary. Not because they are worthless, but because they are not a report — they are notes. Keep notes in the CRM record. A report is the thing you can aggregate, and you cannot aggregate a paragraph.

Why do most sales call report templates fail an audit?

Three failure modes, and they are always the same three.

1. The caller ID field is missing. The template records which number dialled out, but not what name and number the recipient's handset displayed. Those diverge constantly — a number can be dialling correctly and still be displaying as unknown, or worse. This is also the field that explains a sudden answer-rate collapse, which is why the diagnosis usually arrives weeks late. See number reputation management.
2. Script version is not captured. The report says the rep used “the cold call script”. Six revisions later, nobody can reconstruct which words were on screen during the quarter being reviewed, so no A/B conclusion from that period survives scrutiny. Version the script; see cold calling scripts.
3. Consent is a checkbox. The rule wants six sub-fields for consent under 310.5(a)(8): who gave it, the request as it was presented to them, the purpose, a copy of what they gave, the date, and the linked record. A tick in a box labelled “consented” is not any of those. The obligations are set out in 47 U.S.C. § 227 and expanded in our TCPA compliance guide.

All three are failures of the template, not of the reps. A rep cannot type in a field that does not exist, and cannot observe what a stranger's screen displayed.

How do you fill in a sales call report?

If the answer involves a rep and a spreadsheet at the end of the day, the report is already fiction. The sequence below is what filling one in looks like when the mandated fields are captured where they are observable.

What does a sales call report sample look like?

One rep, one morning, four calls. This is the aggregate view the template produces — no prose, no scores, and every column either machine-written or a single tap.

Read the third row again. Same rep, same script, same minute of the morning — and the recipient's handset showed nothing where the other three showed a brand name. That is a live deliverability fault, visible in a routine call report, on the day it happened. A feelings-based template would have recorded “left VM” and moved on, and the fault would have surfaced a month later as an unexplained dip in an answer-rate chart.

This is the argument for the mandated fields in one row: they were written to make calls auditable, and auditable turns out to be the same property as diagnosable.

When is call reporting software worth it?

The honest threshold is lower than most teams assume, and it is not about headcount. It is about whether the nine mandated fields can be produced without a human. If they can, a spreadsheet is fine and a two-person team should stay on one. If they cannot, no amount of process discipline fixes it, because the missing fields are not knowable by the person being asked.

The last row is worth separating out, because real-time call reporting is a different product from reporting. A daily report tells you what a shift did. A live one lets a supervisor see a script version underperforming, or a caller ID failing to transmit, while there is still a morning left to change it. That is the difference between reporting and operating; the broader metric set is in the call centre metrics reference.

If the calls run through a platform at all, the mandated fields are a configuration question rather than a purchase. Every field on this template is recorded per call in AI Dialer, including the caller ID as transmitted and the script version at connect.

The part that makes this worth doing

A sales call report designed around the rule has an odd property: it is shorter than the one it replaces, and it survives contact with a lawyer. You were going to retain those nine fields for five years regardless. Building the sales report on top of the compliance record — rather than beside it, in a second system, with different definitions — means one set of numbers, one retention policy, and no quarterly argument about whose figure is right.

It also removes the thing that kills call reporting everywhere: asking reps to hand-record facts a machine already knows. Nine of twelve fields arrive free. The three that remain are the three that genuinely need a human in the room. Every template that gets abandoned within a quarter got that ratio backwards.

Do-not-call obligations are recorded and retained under the same section — check numbers against the National Do Not Call Registry and keep the evidence of having checked. Volume changes the tooling but not the fields; see the auto dialer guide for what changes when the dialing itself is automated.