An online store handles complaints and post-sale inquiries through the same inbox as orders, causing urgent matters to get lost among shipping notifications. The problem is simple: when an email arrives from a customer reporting non-conformity of goods with the contract, it lands in the same queue as dozens of automated notifications. The owner of a small store without a dedicated customer service department simply doesn't see which messages require immediate action.
On this page, you'll learn how one queue with priorities separates urgent matters from routine status inquiries, why the 14-day complaint response deadline is a legal guarantee, and how to analyze your own inquiries to see how much you're actually losing.
The legal deadline for complaint response — 14 days that decide everything
The seller must respond to a complaint (non-conformity of goods with the contract) within 14 days of receiving it. If they fail to do so, the complaint is considered accepted. This isn't a recommendation — it's consumer law under Article 7a and 43d of the Consumer Rights Act, which adopted principles from the European Directive. In practice, if a customer sends a complaint and you don't respond for 14 days, you automatically lose the dispute — even if the goods were actually in conformity with the contract.
Why this matters for a small store
In a single inbox with orders, the risk of missing such a message is enormous. Status notifications arrive daily in large numbers, while a complaint may come once every few days — easy to miss. Every missed day is a risk the customer will go to UOKiK or request a refund through court, costing you money and time on additional procedures.
That's why small store owners look for ways to organize customer communication — often query handling automation helps, creating one queue instead of five inboxes.
Source: UOKiK — Consumer Rights, complaint about non-conformity of goods.
Order statuses as signals — when complaints arrive
WooCommerce, the most popular e-commerce platform in Poland, defines several order statuses that help understand at which stage a customer might report an issue. The Processing status means payment has been received, stock reduced, and the order awaits fulfillment. The Completed status means the order is fulfilled — the product was shipped and delivered. The Refunded status means the order was fully refunded by the administrator.
When do complaints most often arrive
From store owners' experience: complaints most often arrive within the first days after status changes to Completed, when the customer unpacks the product and checks conformity with the description. Less often — with Processing status, when the order can still be cancelled or modified. Knowing these patterns lets you set automatic rules to boost priority of messages from customers with orders in these specific statuses.
Compare this with reporting automation in e-commerce, which shows what metrics really matter for a store owner.
One queue instead of one inbox — how to separate inquiry types
Traditionally, a small store has one email address. All messages arrive there — payment confirmations, product questions, complaints. The problem is that in this mass, it's easy to miss that one complaint that requires a response within 14 days.
How automatic categorization works
The solution isn't a new inbox, but one queue in CRM with automatic categorization. Instead of manually searching your inbox, the system analyzes each message's content and assigns it to the appropriate category: order status inquiry, product question, complaint (non-conformity), refund request, or other matter. Each category goes to a separate queue with its own handling rules.
This gives the store owner a clear view: how many urgent matters do I have, how many routine questions, how many complaints in progress. Instead of scrolling through hundreds of notifications, you only see what requires action.
Read more about how one queue replaces five inboxes in the article about query handling automation.
Priorities and SLA — why a complaint isn't the same as "where is my package"
Not all customer messages are equal. A complaint has a statutory 14-day deadline — missing it means automatic acceptance of the claim. The question "where is my package" has no such deadline. A request for additional product photos doesn't either.
How to set response times
A CRM system with priorities works like this: each category has an assigned response time (SLA). Complaints — 14 days, but it's best to respond within 3 days so the customer knows the matter is being handled. Order status inquiry — response within 24–48 hours. Product question — 24 hours. Refund request — 7 days.
Importantly: the system doesn't auto-reply. You set rules determining when each type of matter should be handled and get a reminder as the deadline approaches. A human still replies, but knows what's urgent and what can wait.
Priority can also be scored automatically by AI lead qualification, which evaluates a submission by its content before anyone reads it. Learn more about process automation in a company and what can realistically be handed over to a system.
What CRM won't solve — assessing complaint validity is always a human task
The system can detect that a complaint has arrived and set its priority. The system can remind you of an approaching deadline. The system can even prepare a response based on a template. But the system cannot assess whether the complaint is valid.
Who assesses validity
This depends on many factors: whether the defect existed before delivery, whether it occurred due to customer fault, whether the product was used according to instructions, whether the complaint was filed within the appropriate time limit (2 years from purchase for most products). These decisions require a human — the store owner or designated employee who knows the products and can evaluate the specific situation.
That's why CRM supports the process but doesn't replace judgment. The automation ensures you don't miss the deadline and don't lose the matter in the mass of other messages.
Also remember about GDPR in complaint handling — customer data must be processed according to regulations.
Receipt confirmation template — what to respond on the day of inquiry
The customer sends a complaint and doesn't know if you've seen it. For 14 days, every day counts, but the customer isn't certain their message even arrived. The standard practice used by professional stores is an automatic confirmation within hours of submission.
How to write a confirmation
The confirmation template is simple: "Thank you for your submission. Your complaint has been registered. We will process it within 14 days of receipt. If you have questions, we respond at this address." A few sentences that give the customer certainty their matter is in progress and start the transparent deadline countdown.
This type of confirmation can be set as an automatic response to messages containing keywords like "complaint", "non-conformity", "defect", "refund". Automatic messages sends it without human involvement, right when the submission arrives.
Do it yourself — how to analyze your monthly inquiries
Before spending money on a system, check how much you're actually losing. The method is simple: review messages from the last month and count three things.
What to count
First: how many complaints arrived (messages about non-conformity, defects, refund requests). Second: how many you responded to within 14 days. Third: how many you responded to after the deadline or didn't respond to at all.
This analysis takes 30–60 minutes and gives you a concrete number: how many matters you're risking by lacking a system.
Learn more about process automation costs and 2026 ranges.
How it looks with a system — from message to priority queue
The scenario works like this: the customer sends a message to the store address. The CRM system receives the message and analyzes its content — looks for keywords related to complaints or checks the order number and its status in WooCommerce.
If the system detects a complaint — it automatically creates a task in the priority queue with a 14-day timer. At the same time, it sends the customer a receipt confirmation. You as the owner see this complaint at the very top of the submissions list, with a clear countdown of days until the deadline.
If the system detects a routine status question — it goes to the standard queue with a 48-hour SLA. If it's a product inquiry — to the queue with a 24-hour SLA. Each queue has its own view, its own reminders, and its own statistics.
This way you focus on what's really urgent, while routine matters wait their turn — but you know they're waiting, and you know none of them will disappear without a response.
When a complaint requires a lawyer, not just support
Sometimes a complaint is obvious and you can accept it outright: you sent the wrong product, the customer has the right to a refund. But there are situations where the matter is ambiguous: the customer claims the defect existed at delivery, you believe it arose from user error.
In such cases, you don't have to make the decision yourself — you can consult a lawyer or expert. CRM won't replace such consultation, but can support you: it saves correspondence history, keeps all documents in one place, and reminds you of deadlines.
If you see a matter might end up at UOKiK or in court — start documenting from day one. CRM with complete history is essential if later you need to prove you responded on time. You can track the lawyer contact and next steps as Tasks with a deadline and a responsible person, so nothing stays stuck in someone's head.
Also see the Integrations service to connect the CRM with the store so order numbers don't have to be retyped by hand.
Frequently asked questions
Can I respond to a complaint after 14 days and not automatically accept it?
No. If you don't respond within 14 days of receiving a complaint, it's considered accepted. This is under the Consumer Rights Act (Article 7a and 43d), so even if you believe the complaint is unjustified, you must respond within the deadline — you can refuse to accept, but you must do so in writing.
Will a CRM system replace my complaint response?
No. The system can detect message type, set priority, and remind about deadlines, but assessing complaint validity and making a decision (acceptance, refusal, proposed solution) always requires a human. CRM supports the process but doesn't replace the owner's judgment.
How much does implementing CRM for complaint handling cost?
The cost depends on the chosen solution. In Aura CRM and automations handle one submissions queue from every channel, reminders and customer data without manual re-entry. Details and pricing — on the service page.
How quickly can I implement such a system?
It depends on the number of channels and on whether the store already has tidy order statuses. The sensible start is one queue and a confirmation template, tested on a dozen or so real submissions, with store integration, order statuses and reporting added as a second step.
Do I have to give up my current email inbox?
No. The CRM system works as an additional layer — receives messages from your inbox (via IMAP or API integration), analyzes them, and sorts into queues. Your inbox still works, but you work in CRM that shows only what requires action.
What if the customer sends a complaint through a contact form, not email?
The system can handle multiple channels: email, website form, Facebook message, Instagram DM. All arrive in one queue in CRM, regardless of source. The customer doesn't need to remember where to write — one channel is enough, the rest the system recognizes and sorts.