Cash office scripts for collecting overdue franchisee payments - day-3 reminder, day-15 triage, day-30 pre-suspension talk; the facts escalate, the tone does not

You are the cash office clerk of a central kitchen
serving a franchise chain. Franchisee payments are
overdue and I collect in three stages by aging.
Give me word-for-word lines for each stage,
responses to the standard stall lines, and a
written-confirmation template for after every
call.

Positions (every script builds on these):
- I am the cash clerk, not risk control: the goal
  is to collect the payment on the agreed date,
  not to judge how the owner runs his business.
  At the suspension line the account moves to the
  regional manager - I do not show up at the door
- One concession is mine to offer: a payment plan
  (split into two or three installments). Late-fee
  waivers and discounts always require
  headquarters; I do not agree to them verbally
- Within 30 minutes of every conversation I send
  written confirmation (message or email both
  work). Not sent means the conversation did not
  happen

Stage one - 3 days overdue (a reminder, not a
collection call):
- Opening line: assume they forgot; state the
  amount and due date, ask whether it lands today
  - the tone is a reconciliation, not an
  accusation
- If they say "it's already being paid": ask for
  the payment screenshot and agree on same-day
  arrival (one line)

Stage two - 15 days overdue (real collection):
- State the facts first (one line: amount, days
  overdue)
- Then one specific question (one line): is this
  a cash-flow problem, or a dispute over the
  statement
- Cash-flow: give an either/or (one line: settle
  in full today, or pay half now with the balance
  by [date] - pick one today)
- Dispute: ask which specific orders are disputed
  (one line). Disputes with order numbers get
  suspended; everything undisputed gets paid now -
  the payment obligation follows delivery, not
  the invoice, and that sentence is said
  politely but without wiggle room

Stage three - 30 days overdue (the last
conversation before suspension):
- State the aging, then the consequence and its
  date directly (one line: under clause [clause]
  of the agreement, supply pauses at [number]
  days overdue; that date is [date]. Settling in
  full or signing a payment plan before then both
  still work)
- Only consequences written in the contract get
  stated; I do not invent threats
- The close must be a yes/no question (one line)
  that forces a definite answer. "Let me look
  into it" does not end the call - follow with
  one line that puts the either/or back on the
  table

Standard stall lines and responses (one spoken
line each):
- "Business is slow this month": acknowledge the
  fact in one clause, then return to the either/
  or - listen to ten minutes of complaint and the
  balance does not grow by a cent
- "The invoice never arrived, so we didn't pay":
  ask for confirmation of goods received on the
  statement, undisputed portion paid first - the
  obligation to pay follows delivery, not the
  invoice
- "We'll definitely settle next week": accept the
  promise but put it in writing (one line: good -
  I'm sending a confirmation stating [amount]
  arrives by [date]; reply "confirmed")

Written-confirmation template fields: store /
amount / aging / the promised action and its
date / my corresponding action / time sent.
A reply of "okay" is not a confirmation; a
confirmation contains an amount and a date.

Constraints:
- Never say "pay up or we'll sue" - litigation is
  headquarters legal's decision; the threat is
  unenforceable from my mouth and it ends any
  chance this round settles
- No commentary on the owner's business ("running
  a store like this, no wonder" is banned) -
  there is a next month's payment after this one;
  keep the relationship long
- No verbal promise gets booked - a promise
  without writing does not exist at next month's
  reconciliation
- What escalates across the three stages is the
  facts (aging, clause, date), never the voice -
  raise the volume and the owner responds to the
  volume instead of the balance

Why it is written this way

The stages split by aging because the passage of time is itself information. At day 3 the case is almost always a forgotten transfer or a slow approval chain, and opening with collection-movie tone turns a good-natured owner stubborn. Day 15 is the moment to separate cash-flow from dispute - the two answers lead down different paths, and negotiating both at once loses both. Day 30 is no longer about persuading; it is stating the consequence and its date and extracting a definite answer. The clerk's classic error is using the same lines from day 3 to day 30: too harsh early, too soft late.

"Only a dispute with order numbers is a real dispute" is the most useful line in the set. Billing disputes are the standard costume that stalling wears - an owner with a genuine dispute names the orders and the amounts without hesitating, while a costume dispute cannot produce a number. Two sentences move the numberless version gently back onto the payment track. Suspending the named orders while the undisputed portion pays now honors the dispute process without letting it hold the whole balance hostage - and the sentence must be polite with no wiggle room in it, because the wiggle room reads as "pay everything after the dispute resolves," and disputes that convenient never resolve.

The single concession, offered as an either/or, follows the arithmetic of collection calls: fewer options, faster conclusions. "How would you like to handle it" invites "let me think about it," which is the same as no answer. An owner who refuses both options has told you the account belongs in stage three - and the scripts escalate to clause and date without emotion ever being needed.

The no-suing, no-commentary, and written-confirmation trio all protect next month. Franchisee payments recur monthly, and one unauthorized threat or one remark about how the business is run makes every future reconciliation harder. The confirmation template turns a verbal promise into an artifact with an amount and a date - and the rule that "okay" is not a confirmation is the line every clerk who has been burned on a promise will nod at.

Variables