Navigation

Mandate Attachment Levels

Complete reference for scope, inheritance, and override rules

Every mandate is attached to a specific level of your business hierarchy. The attachment level determines where the mandate applies, what it inherits from, what it can override, and what can override it.

This reference covers all eight attachment levels with their properties, recommended mandate types, and practical guidance for when to use each.

Attachment Levels at a Glance

Level Scope Priority Inherits From Can Override
Brand Global — all wares, audiences, channels Foundational Nothing (root level) Nothing (base layer)
Ware One specific product or service Overlay Brand Audience Segment, Pipeline Phase
Product Category A group of related wares Overlay Brand Audience Segment, Pipeline Phase
Audience Segment One specific persona Overlay Brand Pipeline Phase
Pipeline Phase An entire phase (Find, Win, Keep, Grow) Overlay Brand Nothing at overlay level
Pipeline Stage One specific stage within a phase Execution-specific Brand, Pipeline Phase, Ware, Audience Pipeline Phase, Audience Segment
Communication Channel One channel (Email, SMS, Phone, Chat, Website, Social) Execution-specific Brand Audience Segment, Pipeline Phase
Contact Status Contacts in a specific status (DNC, Active, Churned, etc.) Safety Net Nothing (independent) ALL other attachment types

Brand Level

Scope string optional

Global — applies to all wares, audiences, channels, and pipeline stages

Priority string optional

Foundational — the base behavioral layer. Everything else builds on top.

Best for string optional

Global tone rules, company-wide prohibitions, universal hard facts, baseline cadence limits

Avoid using for string optional

Detailed step-by-step workflows, ware-specific objections, pipeline-stage playbooks, contact-status rules

Recommended types string optional

Cadence, Communication Flow, Hard Facts, Prohibitions, Comparatives

Ware Level

Scope string optional

Applies only when SI is discussing or promoting a specific product or service

Priority string optional

Overlay — layers on top of brand-level mandates

Best for string optional

Product-specific objection handling, ware-level competitive positioning, feature-specific hard facts, product-specific tone adjustments

Cannot override string optional

Contact Status prohibitions, brand-level legal/compliance hard facts

Recommended types string optional

Comparatives, Objection Handling, Communication Flow, Cadence, Hard Facts

Audience Segment Level

Scope string optional

Applies when SI is communicating with contacts in a specific persona or segment

Priority string optional

Overlay — adapts messaging for specific personas

Best for string optional

Persona-specific tone and language, audience-tailored objection responses, segment-specific cadence preferences

Cannot override string optional

Hard Facts, Prohibitions, Contact Status mandates

Recommended types string optional

Communication Flow, Objection Handling, Cadence, Comparatives

Pipeline Stage Level

Scope string optional

Applies to contacts at a specific stage (e.g., Demo Booked, Proposal Sent, Onboarding)

Priority string optional

Execution-specific — the most granular operational rules for a contact's journey position

Best for string optional

Stage-specific follow-up cadences, concrete action sequences, stage-specific objection handling

Inherits from string optional

Brand, Pipeline Phase, Ware, and Audience Segment mandates all feed into stage-level behavior

Recommended types string optional

Cadence, Objection Handling, Communication Flow

Contact Status Level

Scope string optional

Applies based on the contact's current status (DNC, Active, Unverified, Churned, etc.)

Priority string optional

Safety Net — highest precedence. Overrides ALL other mandate types when conflicts arise.

Best for string optional

Communication eligibility rules, DNC enforcement, opt-out compliance, status-specific channel restrictions

Overrides string optional

Everything. A Contact Status mandate always wins.

Recommended types string optional

Prohibitions, Hard Facts, Communication Flow

Communication Channel Level

Scope string optional

Applies to a specific channel: Email, SMS, Phone Calls, Live Chat, Website Pages, or Social Media

Priority string optional

Execution-specific — channel-appropriate formatting and behavior rules

Best for string optional

Channel-specific message length, formatting rules, latency expectations, channel-specific prohibitions

Cannot override string optional

Contact Status, Hard Facts, brand/contact-status Prohibitions

Recommended types string optional

Communication Flow, Cadence, Prohibitions

Tip: When in doubt about where to attach a mandate, ask yourself: "Does this rule apply to *everyone* or to a *specific context*?" If everyone, attach to Brand. If it depends on who you are talking to, attach to Audience Segment. If it depends on where they are in the pipeline, attach to Stage. If it depends on how you are communicating, attach to Channel.

Was this article helpful?

NotebookLM Overviews