Merchant services cold call script for statement review bookings

What the statement review call is for

Every shop owner has a fee story: the statement fee that appeared, the increase nobody explained, the terminal lease that outlived the terminal. The call exists to find that story, quantify it, and book the review where a side-by-side of the owner’s own statement settles the question. Owners agree to reviews; they do not agree to pitches, and reps who cannot tell the difference burn lists fast.

The review is also where this category’s risk gets managed. Savings claims tied to the owner’s actual statement, lease and early-termination answers given plainly, and no implied affiliation with the processor: the review is where the honest version of all three gets delivered.

Before you dial: list and hours

Load the merchant list as a CSV with business, phone, category, owner name where known and any equipment notes. Tag by category, because restaurants, salons and retail answer at different hours and a rep who ignores that calls at the worst times.

Calls between businesses generally sit outside the FTC Telemarketing Sales Rule under 16 CFR 310.6(b)(7), but the exemption does not cover the wireless rules, and shop owners answer on personal cells constantly, so 47 CFR 64.1200 restrictions on autodialed and prerecorded calls to wireless numbers still apply. Keep solicitation inside 8 a.m. to 9 p.m. local time at the called party’s location.

The opening: the fee complaint, not the rate

“Has anything on your card processing statement annoyed you lately? Most owners say the statement fee or a random increase.”

The opener works because it asks about a grievance the owner already holds, and the second sentence normalizes answering honestly. It is a question about their experience, not a claim about your pricing. The owner who says “actually yes” is in a conversation; the owner who says “we are fine” gets logged and redialed another month.

The talk track, in order

The script runs grievance, processor, lease, volume, review close. Three habits make it work.

First, ask who processes and let the owner say the name. The answer sets up everything, and reps who guess the processor sound like they did not listen.

Second, always ask about the terminal lease. The bundled lease is the category’s most misunderstood contract, and the rep who explains the buyout plainly, before ever asking for business, is the rep who gets the review.

Third, close on a named slot with a specific deliverable. Two statements, fifteen minutes, a side-by-side, and a promise to say so if the numbers are already good. The walk-away promise is what earns the booking.

Objections you will hear

“Our rates are fine.” Ask when they last compared the statement line by line. Most owners have never seen a full side-by-side, and the question is honest: maybe they are fine, and saying so builds the trust the review needs.

“We are in a contract.” Ask when it ends and what the early termination terms are. A contract end date is a future review with a reason, and the disposition carries the month.

“Someone from a processing company burned us before.” Slow down and ask what happened. The grievance is qualification, and the answer tells you which promise this owner needs in writing.

“Are you with our processor?” Answer plainly and immediately. Falsely implying affiliation with a processor or card brand is exactly what the FTC’s Impersonation Rule at 16 CFR 461.3 prohibits, and the honest answer costs nothing.

“Just email me rates.” There are no rates without the statement. Ask for the review and offer to send the comparison afterward, in writing.

Dispositions in ISO terms

• Statement review booked with day, time and which statements to bring.
• Send comparison after the review, in writing.
• Callback with date and reason.
• Gatekeeper, call back with owner name and best hour.
• In contract with the end month.
• Uses competitor happily with why, for next year’s renewal cycle.
• Not a fit, Left voicemail, Do not call.

What the AI summary captures

DialBreeze records and transcribes connected calls, then writes structured fields. For merchant calls the useful ones are the current processor, monthly volume, ticket average, equipment and lease situation, the fee complaint and the booked review. The side-by-side must match the owner’s actual statement, so verify volumes, processor names and any figures against the recording before the comparison is built, because a review that opens by misquoting the owner’s own volume ends the meeting’s trust. The summary is a briefing note, not the comparison itself.

Compliance lines that matter

The B2B exemption in 16 CFR 310.6(b)(7) covers most merchant calls, but the wireless rules in 47 CFR 64.1200 still reach owner cell phones, and the category’s real exposure is claims: savings promises must match the statement, termination and lease obligations must be stated accurately, and the Impersonation Rule at 16 CFR 461.3 bars falsely implying affiliation with a processor or card brand. Honor every stop request, use a recording disclosure in all-party consent states, and keep claims in writing. DialBreeze applies your internal DNC list, quiet hours and attempt caps. It does not decide whether a number may be called. This page is not legal advice.

Practice it before the real list

Run five sandbox calls where you never name a rate and never promise a percentage. Then run five where the owner defends their current processor. The second set teaches the walk-away promise, which is the line that converts guarded owners into booked reviews.