Fast food franchisee - asking the franchisor for support: data first, requests specific to action and deadline, close every conversation in writing - and emotions plus borrowed crowd pressure banned outright

You are a franchise-relations coach who knows how
franchisor support desks actually process franchisee
requests. Write me a set of scripts for asking the
franchisor for support, covering three scenarios,
as spoken drafts with cue notes for the franchisee.

Scenario one: trade area disrupted, requesting
marketing support
Background: two direct competitors (or a same-brand
infill store) opened within three kilometers; my
sales are down [X]% over [X] consecutive weeks.
- Open with data: "Here are our sales figures for
  [date range], and the trend since [competitor
  opening date]..." - all numbers from the POS and
  delivery back office, with a [data basis] blank
  for me to fill
- Make the request specific: never "we hope for
  support" - every request states action, size,
  deadline (e.g. "requesting geo-targeted online
  spend for this trade area / counter-launch combo
  materials / a three-month royalty deferral" -
  options listed, my pick to make)
- The face-saving frame: translate the ask into
  brand language - "this trade area is the brand's
  storefront in this city; holding its traffic is
  not only my problem"

Scenario two: platform mega-promo, negotiating
subsidy sharing
Background: the franchisor enrolls everyone in the
platform's coupon campaign, but the subsidy falls
mostly on store margin - join and lose money, sit
out and get deprioritized.
- Run the numbers before opening: subsidy per
  order, projected order volume, realized revenue
  per order - three figures, then the ask
- Request shape, three fixed options: franchisor
  marketing fund shares / the promo is restricted
  to margin-safe items / we enroll but are not a
  featured store - letting them pick an option
  beats an open-ended demand
- Banned: "other brands cover all of this" - an
  unverifiable comparison

Scenario three: equipment refresh window, asking
for terms
Background: core equipment is [X] years old with
rising failure rates, and the brand is rolling out
new units.
- Lead with data: repair ticket count and downtime
  impact (state plainly where the loss figure is
  an estimate)
- The ask: trade-in credit / installment / early
  entry into the new-equipment batch - still
  action, size, deadline
- The frame: dragging out replacement eventually
  hurts food safety and throughput - brand
  standards, not my convenience

Fixed closing move for every scenario:
- "Let me write up what we discussed today and
  send it to you (supervisor / franchise manager)
  to confirm - which items can land, which need
  escalation, and by when." - plus the cue: keep
  the sent message, and open the next conversation
  by quoting the last reply

Output format:
- One table per scenario: stage / spoken draft
  ([blanks] for the numbers) / one-line cue
- An appendix "banned phrases" table: emotional
  openings / citing other franchisees / threatening
  to switch brands / promising cooperation I cannot
  deliver - each with a counter-example and one
  line on why it kills the ask

Constraints:
- Invent no brand policies and do not assume any
  particular support exists - every "the franchisor
  might have" resource is a [blank] I fill from
  reality
- No "empowerment," "partnership journey," or
  "co-create" vocabulary nobody says out loud in
  either direction
- Do not have me promise "full cooperation with
  X" unless I filled that blank myself

Why it is written this way

"Data before request" leads every beat because the franchisor's support desk triages on arrival: requests with numbers enter the individual-handling lane, requests with only emotion enter the appeasement lane. The same sentence - "sales down thirty percent" - with a date range and a trend line forces escalation; without numbers it reliably returns "we'll look into it." The data blanks stay blanks for the franchisee to fill, never for the model to invent, for the same reason no SOP gets invented parameters: one wrong number caught by the franchisor discounts every true number after it.

Requests must decompose into action + size + deadline to cure the open-ended ask: open requests invite the most comfortable possible response, "we're looking into it" - which contains no action, no size, no deadline, and always has a sequel. The options-based ask (three choices, pick one) is reverse-engineered from how the desk actually works: what gets escalated and approved is a concrete option, not an open topic.

The banned-phrases appendix carries "citing other franchisees" and "threatening to switch" as full entries rather than footnotes because both are almost reflexive in the heat of the moment: the first upgrades a single-store issue into a group incident, and the handler's first instinct becomes containment rather than resolution; the second is worse - once a threat is on record, what gets filed is no longer the request but the risk, and every future conversation wears armor. The fixed written close is what makes "next time, quote the last reply" possible: verbal commitments are worth nothing against staff turnover; the confirmation message is the thread that survives.

Variables