Use of Approved Marketing Language

All customer-facing descriptions of WeatherIt must use approved language to ensure consistency and compliance.

Approved Language Requirements

flowchart TB
    subgraph Required["Must Use Approved"]
        direction TB
        A["Product<br/>Descriptions"]
        B["Trigger<br/>Explanations"]
        C["Insurance Status<br/>References"]
    end

    style A fill:#e1f5ff
    style B fill:#e1f5ff
    style C fill:#e1f5ff

Content Type	Requirement
Product descriptions	Use WeatherIt-approved wording
Trigger explanations	Use approved explanations only
Insurance status	Reference approved terminology

Where This Applies

All Customer Touchpoints
Approved language requirements apply to every channel where customers encounter WeatherIt.

flowchart LR
    subgraph Channels["Customer Touchpoints"]
        direction TB
        A["Websites"]
        B["🛒 Booking Flows"]
        C["Email<br/>Communications"]
        D["In-venue<br/>Materials"]
        E["Call Centre<br/>Scripts"]
    end

    style A fill:#e8f5e9
    style B fill:#e8f5e9
    style C fill:#e8f5e9
    style D fill:#e8f5e9
    style E fill:#e8f5e9

What Partners Must NOT Do

Prohibited Actions
Do not modify approved language in ways that change meaning.

Prohibited Action	Why
Rewrite product explanations	May introduce inaccuracies
Create alternative trigger descriptions	Could mislead customers
Simplify language that changes meaning	Alters customer understanding

WeatherIt Support

flowchart LR
    subgraph Provides["WeatherIt Provides"]
        A["Standard<br/>Wording"]
        B["Example<br/>Explanations"]
        C["FAQs for<br/>Staff"]
    end

    style A fill:#f3e5f5
    style B fill:#f3e5f5
    style C fill:#f3e5f5

Resource	Purpose
Standard wording	Ready-to-use approved language
Example customer explanations	Scripts for common scenarios
FAQs for frontline staff	Quick answers to common questions

Approved language protects customers from confusion and partners from disputes.