Complaints manual
The Complaints module centralizes the collection and resolution of complaints. It covers three registers — customers, sales reps and field sellers — each with its own nature, type, attachments and a status cycle from filing to closure.
Overview
A complaint is a grievance recorded by an actor in your sales network. Swifto distinguishes three registers based on who raises the complaint; each has its own list, but shares the same nature / type mechanism, the same attachments (photos) and the same status cycle.
Customers
Complaints raised on behalf of a customer (outlet, company). The most used register.
Sales reps
Complaints raised by/about a sales rep from the field team.
Field sellers
Complaints related to a field seller (route, delivery, parcel condition).
Business goal
Track every grievance, assign it, handle it and measure final satisfaction — turning a complaint into a loyalty opportunity and feeding the quality dashboards.
Access and navigation
Left-hand side menu: Complaints → choose the register (Customer complaints, Sales rep or Field seller). A count of unread complaints is displayed in the top bar.
Notification badge — the 71 pill in the top bar totals the pending customer, sales rep and field seller complaints.
Configuration — the Settings submenu gives access to complaint Types, Natures and Workflows (section 7).
Customer complaints
The page displays six statistic cards (smiley) at the top summarizing the breakdown by status, followed by the paginated list. Each row leads to the details and handling.
| Status⇅ | Type⇅ | Nature⇅ | Customer⇅ | Sales rep⇅ | Date⇅ | |||
|---|---|---|---|---|---|---|---|---|
| 😠 | New complaint... | Product quality | Defective product | SOCIÉTÉ EL MAZRAA | Mouadh BEN AZIZA | 08/06/2026 | ||
| 😐 | Handling in progress... | Delivery | Late delivery | ÉPICERIE DAR CHAÂBANE | Ayadi ORABI | 05/06/2026 | ||
| 🙂 | Handled & closed... | Invoicing | Price error | SUPÉRETTE LE BON COIN | Mouadh BEN AZIZA | 29/05/2026 | ||
| 😄 | Satisfied... | After-sales | Exchange request | CAFÉ DELICE SOUSSE | Ayadi ORABI | 22/05/2026 |
Statistic cards (status · color · smiley)
| Card | Smiley | Corresponding status | Color |
|---|---|---|---|
| Total | All complaints in the register | Indigo #7366fe | |
| New complaint | 😠 | Not yet handled (status 0) | Red #bf1e2e |
| Handling in progress | 😐 | Now being handled (status 1) | Orange #e3771f |
| Handled & closed | 🙂 | Resolution provided (status 2) | Apple green #9bbf00 |
| Satisfied | 😄 | Customer satisfied with the response (status 3) | Green #2e9b1f |
| Not satisfied | 😟 | Response deemed insufficient (status 4) | Blue #14418c |
Table columns
| Column | Description |
|---|---|
| Smiley | Status icon (instant read of the status). |
| Status | Status label (or workflow step if the nature uses one). |
| Complaint type | Family (Product quality, Delivery, Invoicing, After-sales…). |
| Complaint nature | Precise reason attached to the type. |
| Customer | Customer affected by the complaint. |
| Sales rep | User who entered / is following up the complaint. |
| Date | Date the complaint was filed. |
| Domain | Displayed only in multi-domain companies. |
Filter & search
Each column can be filtered directly, and the Search button lets you target by type, nature, customer and period (start date / end date).
Sales rep complaints
Register dedicated to complaints about a sales rep. Same smiley statistic cards and the same status cycle as the customer register; the Customer column is replaced by the targeted sales rep.
| Status | Type | Nature | Sales rep | Date | ||
|---|---|---|---|---|---|---|
| 😠 | New complaint... | Behavior | Route delay | Ayadi ORABI | 07/06/2026 | |
| 😐 | Handling in progress... | Reporting | Missing report | Mouadh BEN AZIZA | 03/06/2026 |
Useful for field management: track a sales rep's deviations in behavior, reporting or route compliance, and trace the follow-up to compliance.
Field seller complaints
Register dedicated to complaints about a field seller (route, parcel condition, punctuality). The actor column displays the field seller; the rest of the screen is identical to the other two registers.
| Status | Type | Nature | Field seller | Date | ||
|---|---|---|---|---|---|---|
| 😠 | New complaint... | Delivery | Damaged parcel | Hatem GHARBI | 06/06/2026 | |
| 🙂 | Handled & closed... | Punctuality | Delivery outside window | Slim JAZIRI | 31/05/2026 |
Three registers, one engine — customers, sales reps and field sellers share the same entry form, the same smiley cards and the same status cycle. Only the actor targeted by the complaint changes.
Create a complaint
Click New. Select the type then the nature (the nature dynamically filters the displayed fields), the actor (customer / sales rep / field seller), write the message and attach up to 5 photos.
Form fields
| Field | Role | Required |
|---|---|---|
| Complaint type | Complaint family; drives the list of natures. | ✅ |
| Complaint nature | Precise reason; triggers the display of the Item, Invoice, Photos fields depending on its configuration. | ✅ |
| Customer / Sales rep / Field seller | Actor concerned (depending on the register), searched by autocomplete. | ✅ |
| Item | Displayed if the nature is linked to an item. | Conditional |
| Invoice / Domain | Displayed if the nature is linked to an invoice (domain in multi-domain setups). | Conditional |
| Message | Description of the complaint (up to 500 characters). | ✅ |
| Photos (1 to 5) | Image attachments (gif / jpg / png), displayed if the nature allows it. | Optional |
Dynamic fields
The form adapts to the chosen nature: depending on its configuration, it shows or hides the Item, Invoice fields and the Photos block. No need to fill in everything — only the relevant fields appear.
Handle & status
From the details of a complaint View, the agent switches to Edit to move the status forward and enter a response to the customer. The photo gallery and the original message remain read-only.
Handling — Customer complaint
Possible values: — · Handling in progress · Handled & closed
The 5 standard statuses
| Code | Status | Meaning |
|---|---|---|
| 0 | New complaint | Filed, not yet taken in hand. |
| 1 | Handling in progress | Assigned and being resolved. |
| 2 | Handled & closed | Response provided, case closed. |
| 3 | Satisfied | The complainant confirms their satisfaction. |
| 4 | Not satisfied | The response did not satisfy the complainant. |
Custom workflow (advanced)
A nature can be linked to a dedicated workflow (configured under Complaints → Settings). The complaint then follows named steps specific to your organization, and the Status column shows the workflow step instead of the 5 standard statuses. Each step can be assigned to a specific responsible.
Workflow (diagram)
From filing to resolution: Filing → Assignment → Handling → Resolution / Closure, with a final satisfaction measurement.
flowchart LR A([Complaint filed]):::s --> B[New complaint]:::ko B -->|assignment| C[Handling in progress]:::w C -->|response| D[Handled & closed]:::p D --> E([Satisfied]):::ok D --> F([Not satisfied]):::ko F -.->|reopening| C classDef s fill:#F5F3FF,stroke:#8B5CF6,color:#5B21B6; classDef w fill:#FEF3C7,stroke:#F59E0B,color:#92400E; classDef p fill:#f3f1ff,stroke:#7366fe,color:#1f1c3d; classDef ok fill:#D1FAE5,stroke:#10B981,color:#065F46; classDef ko fill:#FEE2E2,stroke:#EF4444,color:#991B1B;
The Complaints dashboard aggregates these statuses (by month, by type, by nature, by customer, by sales rep) to steer service quality.
Business rules
Type → Nature — each complaint is classified by a type (family) then by a nature (precise reason); the nature drives the displayed fields (item, invoice, photos) and any workflow.
Controlled editing — a complaint already closed (status ≥ 2) can no longer be edited in standard mode; in workflow mode, only the responsible for the current step can move it forward.
Response to the complainant — the Response field keeps the solution provided and accompanies closure, in order to measure satisfaction (Satisfied / Not satisfied statuses).
Attachments — up to 5 photos (gif / jpg / png) per record, kept and viewable in the details gallery throughout handling.
Roles & permissions
| Action | Support agent | Sales rep | Manager | Admin |
|---|---|---|---|---|
| View | ✅ | ✅ | ✅ | ✅ |
| Create a complaint | ✅ | ✅ | ✅ | ✅ |
| Handle / change status | ✅ | — | ✅ | ✅ |
| Configure types / natures / workflow | — | — | ✅ | ✅ |
| Delete | — | — | — | ✅ |
Indicative matrix — depends on the GReclamation privileges (creation, modification, deletion) defined in your company's profiles.
FAQ & real scenario
The Item (or Invoice) field isn't showing?
It depends on the chosen nature. Select a nature configured to require an item or an invoice, and the field will appear.
Why can't I edit a complaint?
It is probably closed, or — in workflow mode — its current step is assigned to a different responsible than you.
Tip — standardized statuses
Reserve the Satisfied / Not satisfied statuses for a confirmed response from the complainant: they feed your service-quality indicators.
Real scenario — Defective product at a customer
- 1Filing — Sonia (support) creates a customer complaint: type Product quality, nature Defective product, customer SOCIÉTÉ EL MAZRAA, item Module Smart Supervisor, message + 2 photos. Status: New complaint 😠.
- 2Assignment — the manager opens the details and moves the status to Handling in progress 😐.
- 3Resolution — the after-sales team arranges the exchange, enters the response and closes it: Handled & closed 🙂.
- 4Satisfaction — the customer confirms receipt of the replacement product: final status Satisfied 😄. The complaint feeds that month's quality dashboard.