Is there software that makes sure I meet the SLA for customer messages on Mirakl marketplaces in the UK?
No software can guarantee an SLA; a person still writes the reply. What software can do is make the deadline impossible to miss: each marketplace's own clock, a list sorted by time left, an alarm before the breach, and a measured reply rate. What that takes, and where one seller actually missed.
No software can guarantee an SLA, because a person still has to write the reply. What software can do is make the deadline impossible to miss: compute each marketplace's own clock, sort the inbox by time left, alarm before a breach, and record every reply time so you know your real rate. Growstall does those four things for Mirakl marketplaces and Amazon; helpdesks built on e-mail forwarding do not, because the deadline never reaches them.
What is the SLA on UK Mirakl marketplaces?
B&Q, Argos, Debenhams, The Range and Tesco Marketplace each give a seller 24 business hours to reply, counted Monday to Friday 9 to 5 UK time with public holidays excluded. Amazon counts 24 hours wall clock, weekends included. A Friday 16:00 message on Argos is due Monday 16:00; the same message on Amazon is due Saturday 16:00. An inbox that shows only “received 3 hours ago” hides both facts. How the clocks differ, with the bank-holiday case.
Why do sellers miss it?
For one UK furniture seller over 90 days, 37% of customer conversations started outside 9 to 5 and 12% at the weekend. The clock was paused for those, so the risk was not the evening message; it was Monday morning, when the paused messages, the weekend's operator notices and the new arrivals landed together. On Argos, where 698 operator notices arrived against 139 customer conversations, the customer messages were the minority of the list.
The difference between the two marketplaces was not effort. It was what the list looked like at 9 o'clock: on B&Q the inbox is almost all customers; on Argos the customers are buried.
What does SLA software actually have to do?
- 1Compute the clock per marketplaceBusiness hours, the operator's holiday calendar, and Amazon's wall clock, from the customer's last message rather than from when you opened it.
- 2Sort by time leftThe thread with 40 business minutes left goes to the top, whoever it is from. Arrival order hides it.
- 3Separate operator noticesThey have their own deadline and they hide the customers. Two lists.
- 4Alarm before the breachAn e-mail or a Telegram message when a thread has less than a set number of minutes left (default 60), once per thread, to a place someone reads.
- 5Record every reply timeSo the weekly number is measured, and the breaches have names and reasons.
What does Growstall do, and what does it not do?
Growstall computes the clock per marketplace with England and Wales public holidays, sorts the needs-reply list by time left, shows a coloured chip per thread (on time, under an hour, late, paused), separates operator notices into their own list, sends an alert by e-mail or Telegram at a threshold you set, and sends a weekly summary with the median first reply in business hours and the share inside the SLA. A marketplace whose calendar is misconfigured is flagged red and gets no clock rather than a wrong one.
It does not write the reply for you unless you press a button, it does not cover eBay or Shopify, and it cannot stop a person from being away. The out-of-hours acknowledgement buys the customer's patience; the deadline still belongs to a person.
How do I know it is working?
Read two numbers weekly: the share of first replies inside the marketplace's window, and the median first reply in business hours. Then read the list of threads that breached and why. On the seller above, almost every late reply in 90 days was a Friday evening or Saturday message answered on Monday: inside the Argos rule and outside the customer's expectation. That is a rota question. Software shows it; a Saturday hour on the rota fixes it.
- Nothing guarantees an SLA; software makes the deadline visible, sorted, alarmed and measured.
- UK Mirakl marketplaces: 24 business hours with holidays; Amazon: 24 hours wall clock.
- The risk is Monday 9:00, when paused messages, notices and new arrivals land together.
- Measure weekly: share inside the window, median in business hours, and who breached and why.
Questions people ask
Does the SLA clock pause on UK bank holidays?
On Mirakl marketplaces with a business-hours rule, yes: a message on the Friday before a bank holiday Monday is due on Tuesday. The software needs the England and Wales holiday calendar for that; a generic UK list gets Scottish and Northern Irish dates wrong.
Does an automatic acknowledgement count as meeting the SLA?
No. Operators measure the first human reply. The acknowledgement tells the customer when that reply is coming.
Can a helpdesk like Zendesk track a Mirakl SLA?
Only if you forward the marketplace notification e-mails into it and rebuild the marketplace's clock yourself. The e-mail arrives without the operator's deadline, holiday calendar or order, so the helpdesk measures its own clock rather than the marketplace's.