Partner Role in Customer Support

As a WeatherIt distribution partner, you have an important but carefully defined role in customer support. This page clarifies exactly what you should and shouldn't do.

What Partners Should Do

flowchart LR
 subgraph Do["Partner Should"]
 direction TB
 A["Provide basic<br/>factual explanations"]
 B["Clarify how WeatherIt<br/>generally works"]
 C["Identify emerging<br/>dissatisfaction"]
 D["Escalate complaints<br/>promptly"]
 end

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

Appropriate Partner Actions

Action	Example
Provide factual explanations	"WeatherIt uses objective rainfall data from weather stations to determine payouts"
Clarify how coverage works	"Your coverage period runs from your event start to end time"
Direct to documentation	"You can find the full Product Disclosure Statement on WeatherIt's website"
Acknowledge concerns	"I understand you have concerns about the outcome"
Escalate promptly	"I'll connect you with WeatherIt's support team who can review this"

What Partners Must Not Do

Critical: These actions must be avoided to protect customers, maintain regulatory compliance, and preserve your partnership.

flowchart LR
 subgraph Dont["Partner Must Not"]
 direction TB
 A["Reassess trigger<br/>outcomes"]
 B["Interpret<br/>weather data"]
 C["Promise reviews<br/>or reversals"]
 D["Offer refunds or<br/>compensation"]
 E["Attempt to 'fix'<br/>insurance outcomes"]
 end

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

Actions to Avoid

Action	Why It's Problematic
Reassessing triggers	Only WeatherIt can assess trigger outcomes using authoritative data
Interpreting weather data	Customer perception of "bad weather" doesn't determine outcomes
Promising reviews	Creates expectations that may not be fulfilled
Offering compensation	Insurance outcomes are governed by product terms, not discretion
Fixing outcomes	Insurance decisions are objective and rules-based

Why This Separation Matters

The clear separation between partner and WeatherIt responsibilities exists for important reasons:

Regulatory Compliance

Australian insurance regulations require complaints be handled by the product issuer
Formal timelines apply once a complaint is identified
Improper handling can create regulatory risk for both parties

Customer Protection

Customers deserve consistent, accurate information
Complaint handling requires access to authoritative data
Resolution must follow established procedures

Partnership Protection

Clear boundaries reduce partner liability
Defined responsibilities simplify operations
Proper escalation maintains trust

The Moment Dissatisfaction Appears

Once a customer expresses dissatisfaction—regardless of how minor it seems—escalation is required.

flowchart TD
 A[Customer Contact] --> B{Dissatisfaction<br/>Expressed?}
 B -->|No| C[Continue with<br/>factual support]
 B -->|Yes| D[Stop providing<br/>explanations]
 D --> E[Acknowledge<br/>the concern]
 E --> F[Escalate to<br/>WeatherIt]

 style A fill:#e1f5ff
 style B fill:#fff4e1
 style C fill:#e8f5e9
 style D fill:#ffebee
 style E fill:#fff4e1
 style F fill:#f3e5f5

Signs to watch for:

Frustration in tone
Questions implying the outcome was wrong
Comparison between expectation and reality
Requests for explanation of "why not"
Any suggestion of misrepresentation

Your role is recognition, not resolution. Identify dissatisfaction early, acknowledge it professionally, and escalate promptly. WeatherIt handles everything from there.