Example business: a small shop handling a faulty product. The remedy example is illustrative; actual rights, terms, warranty obligations, and approvals must be respected.
1. What the process covers
A complaint describes a customer problem. A return records goods coming back. A replacement, credit, repair, or refund is a possible remedy. These can be connected, but opening a complaint does not mean that every later action has already happened.
Use a simple case record so the customer does not have to repeat the story to each staff member. Assign someone to own the next action and communicate the agreed process and expected update.
2. People and records to keep
On small screens, scroll the table sideways to see every column.
| Record | Who uses it | What to keep |
|---|---|---|
| Customer case | Support or shop staff | Contact, order reference, problem, dates, evidence, and assigned owner. |
| Agreed remedy | Authorized staff | Decision, reason, customer communication, and required approvals. |
| Goods return | Warehouse or shop staff | Product, quantity, condition, receipt, and inspection outcome. |
| Credit, refund, or replacement | Finance and fulfillment | References, amount or items, actual completion, and customer confirmation. |
3. The everyday workflow
- Listen and record. Capture the problem and check the relevant order or job.
- Review and agree the next step. Apply the applicable obligations and business process and explain it to the customer.
- Receive goods where required. Record identity, quantity, condition, and accessories.
- Complete the remedy. Connect the approved repair, replacement, credit, or refund to the original case.
- Confirm closure. Check that the promised action actually completed and tell the customer the outcome.
4. A small business example
A customer bought five units at 40 each and reports that one is faulty. In this illustrative case the business accepts the return and agrees a 40 credit and refund. The case records the returned unit, approved credit, and confirmed payment refund separately.
The returned unit waits for inspection rather than immediately becoming saleable stock. If a replacement is agreed instead, create the appropriate fulfillment record and keep the link to the original issue. Do not accidentally process both remedies when only one was approved.
5. Checks and common problems
- Keep a customer update date so a case does not sit indefinitely in “under review.”
- Record a duplicate contact against the existing case where appropriate, rather than issuing a second refund.
- Do not hide a failed refund by closing the complaint; keep the finance follow-up visible.
- Follow applicable customer rights and agreed warranty terms rather than assuming one return period applies everywhere.
- Review repeated fault, delivery, or description problems so the business can address their cause.
6. Start with a simple system
Start with a case number, an owner, an agreed next action, and linked return and finance records. A simple helpdesk can add status updates, attachments, queues, and a record of customer communications.
Review cases waiting for a decision, overdue promised actions, repeated issues, and refunds awaiting confirmation. Use those observations to improve service and product information, not just to close tickets faster.
7. Frequently asked questions
Does a returned product automatically go back into saleable stock?
No. Record receipt and inspect the item before deciding its next location or condition. It may need repair, supplier return, or other handling.
Can we close a case when the refund is requested?
Check that the promised action has actually completed, or keep its pending state visible with an owner. A requested refund can still fail or need finance review.
Should all complaints get the same remedy?
The appropriate remedy depends on the facts, applicable customer rights, agreed terms, and authorized business process. Explain the decision and record the action taken.
Get free business templates or discuss a system for your workflow.