Every complaint, return and claim becomes a case.
Agents turn every complaint, return, warranty claim and spare part request into a case, find the article and the order, and prepare the resolution. Your team approves it.
01 What it looks like
A shared mailbox is not a system.
-
One inbox for every brand and channel
-
A case for every request
-
Checked against order, delivery and policy
-
Only judgement calls reach your team
02 One case, start to finish
From a photo to a closed case.
-
The agent builds the case
-
Your team decides goodwill and credit
-
The credit note lands in your ERP
03 What to expect
Repa started with orders. Claims came next.
- 92%
- of incoming customer orders handled without a touch
- Repa, a spare parts wholesaler, runs its customer orders through cloudsquid across regions, matched against more than three million items. The same inbox is now taking on complaints and warranty claims.
| What changes | With cloudsquid | Today |
|---|---|---|
| Every request tracked as a case | Yes | No |
| One history per customer, across teams | Yes | No |
| Article found without an article number | Yes | By hand |
| Missing photos and receipts requested from the customer | Yes | By hand |
04 Working with us
Live in two weeks. No integration to start.
-
01 You shareDay 1
Forward the mailbox and show us how you work.
SOPs, sample cases and an export from your ERP are enough. No integration project to start.
-
02 We set upWeek 1
Rules, approval limits and the mapping to your ERP.
You decide what agents may do alone. Everything is versioned and yours to change.
-
03 Agents runWeek 2
Agents work the inbox. Your team handles the exceptions.
In Outlook, Teams or the cloudsquid workspace, with the evidence attached.
Agents run in a secure agent environment with EU data residency, on an ISO 27001:2022 certified platform.
05 One platform
Start with one inbox. The next needs no new tool.
In this inbox
Complaints
Returns and credit notes
Warranty claims
Spare part requests
Shipment complaints