Customer Support FAQs
Frequently asked questions about handling customer disputes, complaints, and support enquiries related to WeatherIt.
What should staff do if a customer disputes a payout?
This is a complaint and must be escalated to WeatherIt immediately.
flowchart LR A[Customer<br/>Disputes Payout] --> B[Acknowledge<br/>Concern] B --> C[Avoid Debating<br/>Triggers] C --> D[Escalate to<br/>WeatherIt] D --> E[Within 1<br/>Business Day] style A fill:#ffebee style B fill:#fff4e1 style C fill:#fff4e1 style D fill:#f3e5f5 style E fill:#e8f5e9
Staff Should
| Do | Don't |
|---|---|
| Acknowledge the customer's concern | Debate trigger details |
| Explain WeatherIt will review | Justify or defend the outcome |
| Escalate within 1 business day | Promise reviews or compensation |
| Collect booking/policy reference | Reassess weather outcomes |
What if staff think the system might be wrong?
Do not speculate with customers.
If staff believe there may be an issue with a trigger assessment:
flowchart TB
A[Staff Concern] --> B[Do Not Share<br/>with Customer]
B --> C[Escalate to WeatherIt]
C --> D{Include}
D --> E[Booking Reference]
D --> F[Policy Reference]
D --> G[Description of Concern]
style A fill:#e1f5ff
style B fill:#ffebee
style C fill:#f3e5f5
style D fill:#fff4e1
style E fill:#e8f5e9
style F fill:#e8f5e9
style G fill:#e8f5e9
Never Speculate
Suggesting the system "might be wrong" undermines customer confidence and creates expectations that may not be met. Escalate concerns internally—don't share them with customers.
Escalation Information
| Information | Purpose |
|---|---|
| Booking reference | Links to the transaction |
| Policy reference | Identifies the insurance policy |
| Description of concern | Explains what seems inconsistent |
WeatherIt will investigate using authoritative weather data.
How should staff respond to frustrated customers?
When a customer is upset about an outcome:
Recommended Approach
flowchart LR A[Frustrated<br/>Customer] --> B[Listen<br/>Fully] B --> C[Acknowledge<br/>Feelings] C --> D[Explain<br/>Next Steps] D --> E[Escalate<br/>Promptly] style A fill:#ffebee style B fill:#fff4e1 style C fill:#fff4e1 style D fill:#e1f5ff style E fill:#e8f5e9
Sample Responses
| Situation | Response |
|---|---|
| Customer is disappointed | "I understand you're disappointed with the outcome. Let me connect you with WeatherIt's team who can review your case directly." |
| Customer is confused | "I can see this is confusing. WeatherIt can explain exactly how the assessment worked for your specific coverage." |
| Customer is angry | "I understand your frustration. WeatherIt takes these concerns seriously and will review this thoroughly." |
What if the customer asks detailed trigger questions?
For detailed questions about specific trigger assessments:
| Question Type | Response |
|---|---|
| "Why exactly wasn't I paid?" | Escalate to WeatherIt for detailed explanation |
| "What was the rainfall reading?" | WeatherIt can provide this information |
| "How was my window calculated?" | WeatherIt can explain the specifics |
Partner Limitations
Partners don't have access to the detailed weather data used for individual trigger assessments. Only WeatherIt can provide this information.
What if multiple customers have similar complaints?
If you notice patterns in customer complaints:
flowchart TB
A[Pattern<br/>Observed] --> B[Continue Normal<br/>Escalations]
B --> C[Also Report<br/>Pattern to WeatherIt]
C --> D{Potential Outcomes}
D --> E[Product Improvements]
D --> F[Messaging Updates]
D --> G[Training Refinements]
style A fill:#e1f5ff
style B fill:#fff4e1
style C fill:#f3e5f5
style D fill:#fff4e1
style E fill:#e8f5e9
style F fill:#e8f5e9
style G fill:#e8f5e9
Report patterns even if:
- Individual complaints have been resolved
- Issues appear minor
- You're not sure if it's significant
This feedback supports continuous improvement.
Your role is recognition and escalation—not resolution. WeatherIt handles all complaint investigation and resolution.
Updated 8 months ago
