Merchant services calling playbook: territory blocks and review cadence

The call block, by category and shift

Merchant calling is a timing business. The same list contains three different answering patterns, and the block structure turns that into an advantage.

Morning, prospecting block. Retail at opening, salons between clients, gatekeeper hunts for restaurant groups. The deliverable is booked reviews and named owners with their hours.

Afternoon, review block. Booked statement reviews, comparison follow-ups, and contract-end callbacks 60 to 90 days before the end month. This block converts at multiples of prospecting and gets skipped first. Treat it as an appointment with the calendar.

Restaurant windows, 2:00 to 4:00 PM. The dead zone between lunch and dinner prep is the highest-answer window in the category, and it is its own block, not an afterthought.

List hygiene

Load the territory as a CSV with business, phone, category tag, owner name where known and equipment notes. Deduplicate by phone and address, because the same shop appears on directory lists, permit records and a purchased file at once, and calling one owner twice in a week from two lists is how territories earn complaints.

Screen the internal do-not-call list before the block. Business-to-business calls sit mostly outside the FTC Telemarketing Sales Rule under 16 CFR 310.6(b)(7), but the exemption is narrow and not a wireless-number exemption, and owner cell phones are where these calls get answered under 47 CFR 64.1200. A stop request is honored and logged the same day.

Attempt cadence

Five touches over four weeks, then park for a quarter.

• Day 1: fee-complaint opener by category block.
• Day 4: named-owner attempt at the hour the gatekeeper gave.
• Day 10: review offer with the lease question answered.
• Day 18: follow-up with the two-statements ask.
• Day 28: close-out, and park.
• Contract-end trigger: any “in contract” disposition resurfaces 60 to 90 days before the end month.

Solicitation calls stay within the legal calling window in the called party’s local time. Voicemails stay short: name, firm, the review offer, a number.

Dispositions in ISO terms

• Statement review booked: day, time, statements requested.
• Send comparison: in writing, after the review.
• Gatekeeper, call back: owner name and best hour.
• In contract: end month on the record.
• Uses competitor happily: with why, for the renewal cycle.
• Not a fit: with the reason.
• Left voicemail and Do not call.

Working three lines on a merchant list

DialBreeze rings up to three numbers per rep and the rep takes the live answer, with a recorded voicemail dropping on the rest, where enabled on your workspace. Merchant lists are main-line heavy, so three lines buys conversations per hour rather than raw dials, and two owners occasionally answer at once, so pick a line count the rep can serve without rushing a fee explanation. DialBreeze applies your internal lists, quiet hours and attempt caps; it does not decide whether a number may be called.

Verify volumes and figures against the recording before the side-by-side is built, because a comparison that misquotes the owner’s own numbers destroys the trust the whole approach depends on. The lifecycle blocks run on the same fields: the 90-day onboarding check, the one-year rate review, the equipment upgrade near lease end, each with the account’s history attached so the merchant never re-explains their setup.

The handoff between the call and the review deserves as much design as either. A confirmation call the day before, naming the two statements to bring, doubles as show-rate insurance and as the moment the lease question gets answered calmly. Desks that deliver the not-interested verdict in writing get referred at the highest rate in the category, because an owner who watched a rep walk away from easy money trusts the next number that rep shows.

KPI targets as ranges

Reference points from the team’s own daily use (last 90 days to 2026-09-26, one line, one operator): about 85 dials in a typical active hour, about 600 on a typical day, and a 17.8 percent person-connect rate. Aggregate measured values, not a promise.

For an ISO desk:

• Dials per rep day: about 600 dials on a typical day, single line, one operator.
• Person-connect rate: 17.8 percent measured over the last 30 days in the team’s own daily use; your list mix will move it.
• Statement reviews booked per rep-week: track it weekly and set the target from your own first two weeks of data.; count it on a clean territory.
• Review show rate: track it weekly and set the target from your own first two weeks of data.; the lever is a confirmation call and the statements named.
• Comparison-to-account rate: track it weekly and set the target from your own first two weeks of data. When the side-by-side matched the statement.
• Reviews booked per hundred dials by list source: the number that decides next quarter’s list budget.

Compliance, disclosure and the parts that belong to counsel

The category’s exposure is claims and identity: savings promises matched to statements, lease and termination terms stated accurately, and no implication of affiliation with any processor or card brand under the Impersonation Rule at 16 CFR 461.3. Keep suppression current, honor stop requests, use a recording disclosure, hold the calling window, and route anything about telemarketing registration or fee-disclosure requirements to counsel before the campaign scales. This playbook is an operating guide, not legal advice.