The Franchises pack

Everything in the pack,
and everything it will not do.

The CRM fields and stages that follow every call, what it connects to, and what it never says. Why any of it matters is on the Franchises page.

Franchises — this pack was built for the calls that reach this kind of business. Illustrative photograph.

Fields that are filled when the call ends

This trade pack is built to order. Below is the design we switch on for you: the fields, stages and never-say list are drafted, so with your price list and hours it can be switched on within days.

Call type (franchise, complaint, other)Region and budgetDisclosure document sentStore and date of the incidentRegional manager assignedWhen the candidate wants the call

The stages an inquiry moves through

How many inquiries sit at each stage, on one line — in the order work actually flows in a Franchises.

Lead received→Sorted: lead or complaint→Manager assigned→Consultation or resolution→Signed or closed
PipelinePipelineLead rece4Sorted: l3Manager a2Consultat1Signed or1

What it will not do

Not a setting you switch on and off. These are blocked when the Franchises answering is built; anything that touches them goes to a person instead of being answered.

  • It never states expected revenue.Franchise law bars a revenue projection without a basis. “What would a store in Dunsan-dong make” goes to the regional manager, who answers from the disclosure document.
  • It never rates a location.Whether a neighbourhood will work is not answered. The site survey is done by a person.
  • It never discounts the franchise terms.It quotes the published schedule and nothing off it.
  • It never admits fault for a franchisee.A complaint is logged as facts and routed to the right department. No apology binds a store.

This page is the list; the argument is on the other one. What kind of call comes in at night, what a missed one costs, and why a machine must not say certain things are written on the page this pack came from.