Understanding Enquiries vs Complaints
Learn the critical distinction between customer enquiries and complaints, with clear examples to help identify each type of customer contact.
Understanding the difference between enquiries and complaints is fundamental to proper customer support. This distinction determines:
- Whether partners can respond directly
- Whether regulatory timelines apply
- How the issue should be handled
What Is an Enquiry?
An enquiry is a request for information or clarification. The customer is seeking to understand, not expressing dissatisfaction.
flowchart LR subgraph Enquiries["Common Enquiries"] direction TB A["How does the rain<br/>trigger work?"] B["When will the coverage<br/>period end?"] C["How do payouts<br/>happen?"] D["What rainfall amount<br/>triggers a payout?"] end style A fill:#e8f5e9 style B fill:#e8f5e9 style C fill:#e8f5e9 style D fill:#e8f5e9
Examples of Enquiries
| Customer Says | Type | Partner Can Respond? |
|---|---|---|
| "How does the rain trigger work?" | Enquiry | Yes |
| "When will my coverage period end?" | Enquiry | Yes |
| "How are payouts processed?" | Enquiry | Yes |
| "What's the rainfall threshold?" | Enquiry | Yes |
Responding to Enquiries
Partners may answer factual questions using:
- Approved explanations from this portal
- WeatherIt-provided FAQs
- Information in customer documentation
Safe to Answer
Factual questions about how WeatherIt works can be answered using approved materials. Stick to the information provided and avoid speculation.
What Is a Complaint?
A complaint is any expression of dissatisfaction about:
- The product itself
- The service received
- A payout outcome
- How the product was sold or explained
Important: Even if the customer does not use the word "complaint", their contact may still be treated as one if they express dissatisfaction.
Examples of Complaints
flowchart LR subgraph Complaints["Complaint Indicators"] direction TB A["'This isn't what<br/>I was told would happen'"] B["'I think this<br/>was misleading'"] C["'I want this<br/>reviewed'"] D["'Why didn't I<br/>get paid?'"] end style A fill:#ffebee style B fill:#ffebee style C fill:#ffebee style D fill:#ffebee
| Customer Says | Type | Partner Action |
|---|---|---|
| "This isn't what I was told would happen" | Complaint | Escalate |
| "I think this was misleading" | Complaint | Escalate |
| "I want this reviewed" | Complaint | Escalate |
| "I should have been paid" | Complaint | Escalate |
| "The system must be wrong" | Complaint | Escalate |
The Grey Area
Sometimes it's not immediately clear whether a contact is an enquiry or complaint. When in doubt:
flowchart TD
A[Customer Contact] --> B{Is the customer<br/>expressing dissatisfaction?}
B -->|No - just asking| C[Treat as Enquiry]
B -->|Yes - unhappy| D[Treat as Complaint]
B -->|Unsure| E[Treat as Complaint]
C --> F[Respond with<br/>approved information]
D --> G[Escalate to WeatherIt]
E --> G
style A fill:#e1f5ff
style B fill:#fff4e1
style C fill:#e8f5e9
style D fill:#ffebee
style E fill:#ffebee
style F fill:#e8f5e9
style G fill:#f3e5f5
Key signals that indicate a complaint:
- Tone of frustration or disappointment
- Questions that imply the outcome was wrong
- Requests for review or reconsideration
- Suggestions that the product was misrepresented
- Comparison between expectation and reality
When in doubt, escalate. It's always safer to treat an ambiguous contact as a complaint and let WeatherIt make the determination.
Updated 8 months ago
