Measuring Whether Call Notes Record the Customer's Stated Decision Maker

Research question and evidence scope

When a caller speaks with someone who seems to decide, does the note preserve who that person is and what authority they hold? The scope is one outsourced calling queue during a defined period, not an industry benchmark. A note can contain a friendly name and still leave the next caller unable to tell a decision maker from an assistant who gathers information. The audit asks whether the recorded role and authority are findable, consistent, and tied to the customer reference.

This review does not judge whether the conversation was persuasive or whether the person actually signed an agreement. Those questions need the recording, the contract, and a separate quality review. The narrow purpose is to show whether the decision-maker claim survives note-taking and reaches the next person who dials. Record the definition, sample, and observation window beside the result so another reviewer can repeat the check.

The unit is one completed conversation that contains a decision-maker claim. A record where the caller spoke to two people should be coded as a multi-contact record rather than forced into one claim. If the customer later named a different decision maker, keep both entries linked and note the date of the change. That history shows whether the team recorded a real update or simply overwrote the earlier name.

Operating scenario and evidence

Start with a dated export of conversations completed inside the review window. Include the customer reference, call time, caller, campaign, contact name, stated role, and the field where authority appears. Add records with no decision-maker claim so the audit can report the share that is absent. Exclude internal calls and test records, and state those exclusions in the working note.

A claim is usable when a later reviewer can read a name, a role, an authority statement, and a source for the claim. The source might be the person's own words, a transfer from another team, or a document the customer referenced. A free-text sentence can be usable if it carries those elements, but it is harder to count. Record which format was used so structured fields and narrative notes are not mixed without a label.

Method and review criteria

Classify each record as complete, partial, conflicting, or absent. Complete means the note has a name, role, authority, and source. Partial means one element is missing, such as the role or the basis for authority. Conflicting means two entries disagree about who decides. Report counts by state rather than one pass rate, because each state points to a different repair.

Split the result by campaign and by shift, since the working rules may differ. A renewal desk may speak mostly to account owners, while a reception desk may speak to whoever answers first. Compare the observed note format with the campaign's written instruction. A mismatch is a process finding and belongs to the campaign owner rather than to one caller. Report the count inside each split so a small group is not overweighted.

Check whether the note separates an influencer from a decision maker. A person who can recommend a change is useful to record, but the note should not call that person the final authority without support. Preserve the customer's own description when it is unusual, such as a committee or a shared household decision. If the authority is unclear, mark it unverified rather than choosing the friendlier label.

Authority and practical implications

Include the channel and the number used for the conversation. A decision-maker claim from a brief voicemail is not equal to one from a live conversation at the listed number. Record whether the claim came from the person named or from a colleague speaking about them. Write it beside the claim rather than in a separate summary. That distinction keeps a referral from being counted as direct confirmation.

Use a census for a small queue and a documented sample for a larger one. Oversample records that crossed a shift boundary, a weekend, or a transfer between teams, because names are easiest to lose there. Freeze the selection before reading the notes and report later additions separately. Have a second reviewer check a subsample and record disagreements against the written definition.

Separate a missing name from an unreadable one. A blank field is a clear absence, while a note with two names and no role can be ambiguous without being empty. Ask a second reviewer to read a sample of ambiguous notes before scoring them. Keep the two states separate in the report. That step keeps a formatting problem from becoming a false accusation about a caller.

Limitations, conclusion, and sources

The result can support a change to the intake form, the script, or the handoff checklist. It cannot prove that the named person had legal authority to approve a contract or that the customer was satisfied. Pair the audit with a sample of next calls that relied on the recorded name. Preserve the original note when a definition changes and label the transition date.

Run the audit after any change to the form, the dialer, or the campaign brief. A monthly cadence suits a stable queue, while a weekly check may fit a campaign with frequent rule changes. Archive the export, coding sheet, and notes so another reviewer can reproduce the result. Label the review window on the first page. Use the same states next time so the comparison stays honest.

Sources: FCC consumer guidance on unwanted calls; FTC guidance on the Telemarketing Sales Rule; NIST Privacy Framework; U.S. Small Business Administration guidance on managing a business. Each source was checked on November 7, 2026 and is used for general operating context, not as a local performance benchmark. These references frame privacy, contact permission, and record-keeping expectations but do not validate any single queue's notes. Record the definition and sample size beside the result so the review can be repeated.