Franchise email marketing questions nobody wants to ask out loud

Franchise teams tend to skip the same questions about email: who owns the list, whether consent exists, who handles opt-outs, and which domain sends. Each section below states one of those questions as its heading and answers it directly, naming the US and Canadian laws that apply.

Is this email commercial, or transactional?

Classify the message by its primary purpose and content before choosing an audience or sending method. That distinction helps determine whether the message is commercial or transactional or relationship-based under CAN-SPAM.

A label in a template or campaign system does not settle the question when the email combines more than one purpose.

The statutory commercial-email definitions and the related statutory terminology provide the terms to apply to the actual content. Where classification is mixed or jurisdiction-specific, seek qualified advice. Include this review in franchise email planning, before separate locations build their own lists and accounts.

Do we actually have permission to send this?

Match permission to the way an address was collected, the disclosure made at that point, and the message now proposed.

Express consent is an active choice; implied consent depends on an existing business relationship and expires according to the relevant jurisdiction. Neither a list source nor a campaign label substitutes for that assessment.

In Canada, the governing law is Canada's Anti-Spam Legislation (CASL), enforced by the CRTC. Under CASL, a purchase creates implied consent for 24 months, while an inquiry creates implied consent for 6 months. In the United States, the CAN-SPAM Act, enforced by the FTC, requires accurate headers and a clear, conspicuous opt-out, which the sender must honor within 10 business days. Check consent for lead inquiries against the rules that apply before a send goes out.

At collection, explain the sender identity, purpose, frequency range, and method for withdrawing permission. Buying an address list does not itself establish consent. Keep the consent record with the person's current status and later changes, and make the local marketing rules part of the collection and sending review for each location.

Who owns the unsubscribe list when locations send their own email?

Keep one accountable suppression layer across the network, even when locations create their own segments. Before each send, the system should make it possible to check how a person joined, what was disclosed, the relevant brand or location relationship, approved topics, current status, and any later changes.

The lead generation tools should support the preference system rather than create competing local records. Written brand management terms can specify access, use, transfer, exports, and deletion when a location or vendor changes. This makes it clearer who controls audience data and who must act on a withdrawal.

Local teams still need to follow the rules that govern their own marketing activity. Network-wide controls should not obscure who is responsible for a location send, who can change the audience, or how an opt-out is carried across the system. Treat the suppression layer as shared infrastructure, not as a replacement for local oversight.

Can a new location start sending from its own domain?

Approve the sending setup before a location begins using a new domain. A domain change can affect recognition, authentication, reputation, monitoring, recovery, and continuity, so it is an operating decision rather than a cosmetic adjustment. Set the owner and review the plan before sending volume begins.

Before sending, verify the From name, reply route, DNS, SPF, DKIM, DMARC, TLS, tracking, and provider requirements. Review sender authentication alongside the provider's current guidance on formatting, spam rates, alignment, one-click unsubscribe, and sending practices. Provider instructions can inform setup, but they do not guarantee delivery or state the complete law.

How often can a franchise email the same person?

Choose cadence in light of the message purpose, the customer's state, and negative signals. A common working ceiling, not a legal limit, is one promotional send per contact per week. Following a purchase or booking, wait seven days before another promotional send unless the customer chose a faster cadence.

Record the cadence decision and revisit it when customer behavior, provider requirements, or operating capacity changes. Track complaints against Gmail's threshold: stay below 0.10 percent and avoid 0.30 percent or higher. Unsubscribe rate, click-to-conversion rate, and revenue per thousand delivered can add context; opens should not be the sole measure of performance.

What should we write down before approving a send?

Write down enough to reconstruct why a send was approved and what it was meant to test. Name the owner, eligible population, evidence period, method, limits, and review trigger. Pair each evaluation question with its evidence, its method, and a stated limitation.

For scheduled sends, keep the local marketing questions, consent basis, and withdrawal route in the record. Assign privacy duties to named roles rather than leaving responsibility unclear. These fields make it easier to identify who can approve a send, who checks audience eligibility, and who handles a change in status.

Use a compact record that states the governing CAN-SPAM duty or provider rule, the accountable person, the audience included, and how the evidence was assessed. Note the action chosen, what was rejected, and what the result cannot establish. Set a review date or trigger in the program checklist.

Can we use a purchased list, a no-reply address, or open rates?

Treat a purchased list as a question for review, not as proof of permission. Check the applicable law, consent basis, source quality, provider rules, sending reputation, and customer expectations.

The purchase of addresses does not make the resulting messages wanted, so keep list provenance separate from evidence that a person may receive the planned email.

A no-reply address is not automatically appropriate. Provide a monitored reply route when replies are useful or expected, and make other support paths clear. Do not use open rate as the main KPI: privacy behavior in email clients can affect opens, and an open does not show that a valuable customer action was completed. Review the program when behavior or operating conditions change.

The blunt questions in one place