One inbox
Unify email, chat, and follow-up in one workflow. Agents see what is open and who owns it.
Webshop support
Ecommerce Help Desk Software Built Around Orders
Webshops get repeat questions about shipping, returns, refunds, and orders. SamDesk combines inbox, tickets, customer data, and order context so support teams reply faster without switching between screens.
Daily webshop questions
- WISMO: where is my order?
- Return instructions and refund status
- Shipping delays and proactive updates
- Exchanges, complaints, and escalations
Order context
Connect questions to order, customer, and history. WISMO, return, and refund questions move faster.
Templates
Use consistent replies for common situations and improve them with human review.
Why a normal mailbox is not enough
A mailbox can receive questions, but it misses status, ownership, and operational context. Once multiple agents work together, duplicate replies, missed follow-ups, and unclear priorities appear.
SamDesk adds that layer with tickets, workflows, snippets, and KPI tools. Also see our WISMO calculator, the page on customer service automation, and the tool that helps you calculate support handling time.
What ecommerce help desk software must do that generic helpdesks do not
A generic helpdesk stores conversations. An ecommerce help desk stores conversations next to the order they are about, and that single difference decides how long a reply takes. Most support minutes in a webshop go into looking up which order a message refers to and what was promised earlier, not into writing the answer itself.
- Order, shipment and refund status visible in the thread, not in another tab
- Return stage attached to the conversation so follow-ups do not restart the case
- Customer history across channels, so email and chat about one order stay one case
- Saved replies that pull real order data instead of leaving blanks to fill by hand
Your platform decides half your shortlist
Before comparing helpdesks, be honest about which store platform you run and how deep the integration needs to go. Every vendor claims support for the major platforms; the difference is whether that means reading order data or actually acting on it.
- Shopify: the most crowded integration space. Check whether the help desk can only read orders or also edit, cancel and refund them.
- WooCommerce: integrations are often built second. Check how it authenticates and what happens when you update plugins.
- Adobe Commerce (Magento): heavier, usually API-driven, and worth confirming who maintains that connector.
- BigCommerce en Lightspeed: smaller integration ecosystems, so verify before you shortlist rather than after.
- Multiple storefronts or marketplaces: check whether one inbox can hold them all, because two inboxes rebuild the problem you are solving.
What that order context looks like in SamDesk is on the Shopify and WooCommerce order context page.
What a shortlist should survive: vendors, pricing, and a pilot
There is no single best ticketing system, and every list claiming otherwise is ranking by something that is not your situation. What does transfer between companies is the shape of the decision: match the tool to your volume, your team size and who will administer it.
- Zendesk en Freshdesk: broad platforms that scale, at the cost of needing someone to own the configuration.
- Gorgias en Richpanel: ecommerce-native, strongest on storefront workflows, narrower outside them.
- Intercom: messaging- and AI-led, best when in-app conversation matters more than ticket structure.
- Open source zoals Zammad of FreeScout: free licence, real hosting and maintenance cost. Budget the person, not the software.
Compare the pricing model before the number. Per-agent pricing is predictable until you want seasonal help; per-ticket pricing scales with your busiest month rather than your team; per-AI-resolution pricing grows as the AI gets better at its job. Price your peak month, not your average one, and count onboarding, integrations billed separately, and the admin hours the platform needs. Build a twelve-month view per candidate with migration as a genuine cost line.
And judge candidates with a pilot on real traffic, not a demo. Move one queue first and keep the old system running behind it, rebuild only the macros the pilot needs, validate order context before cutover, then compare first response time, resolution time, reopen rate and how often managers override routing.
The scenario book: delivery questions every webshop gets
Carriers publish pages about lost and swapped parcels, but they are written for the recipient. As a webshop you sit on the other side: the customer contacts you, not the carrier. These five situations make up most of your delivery tickets. Fix per situation what the first reply is, which evidence you need and when you absorb the cost yourself — so nobody on your team has to reinvent it case by case.
Parcel delayed or lost
As long as tracking still moves it is a delay; once the status has been frozen for days you treat it as lost. Fix that boundary in days, otherwise one agent waits while another opens an investigation straight away.
- Contact the customer before they contact you the moment you spot a stalled shipment
- Promise a follow-up moment, not a delivery date you do not control
- Keep the carrier investigation and the customer thread on the same ticket
Delivered, but not received
The most expensive argument in ecommerce, because the scan says it went fine and the customer says it did not. The outcome rarely depends on who is right, but on how much you are willing to lose to keep the customer.
- Always ask about neighbours, the porch and any delivery photo
- Agree an order value below which you simply reship without discussion
- Track how often this happens per carrier — that figure belongs in your next carrier negotiation
Parcels swapped
Two customers have each other's order. That means one problem with two tickets, and it is only solved when both sides are right. Link the two conversations immediately.
- Ask for a photo of the received label: it points straight to the second order
- Send the return label yourself; never let customers arrange it between themselves
- Repeat swaps point at your packing station, not at the carrier
No pickup code for the parcel locker
Almost always a mail that landed in spam or went to an old address. Annoying for the customer, because the locker's holding period keeps running. This ticket is urgent even though it looks small.
- Check the email address on the order before you approach the carrier
- State how long the parcel stays there and what happens afterwards
- If the deadline passes, handle the return proactively instead of waiting
Return sent, refund not visible
The gap between "parcel handed over" and "money on the statement" is the biggest source of follow-up questions on a single order. Every message you send inside that gap saves a ticket.
- Confirm arrival at your warehouse, not just the processed refund
- Separate how long you need from how long the bank or payment provider takes
- Measure how much contact one return generates with the return contact rate calculator
What these five share
In every case your agent only knows the answer once they can see the order, the shipment status and that customer's earlier messages together. Spread across three systems, the lookup takes longer than the answer.
- Order context beside the conversation saves the most time on exactly these tickets
- Saved replies work well here, provided somebody updates them after each peak season
- Tag by scenario, not by channel — that shows which of the five costs you most
Returns: where your support pressure comes from
A return is not a moment but a chain: request, ship, receive, inspect, refund. The customer only sees the start and the end. Every step in between where you stay silent turns into a message in your inbox. Return tickets rarely mean your return policy is unclear — usually it is your return communication that goes quiet.
In the Netherlands and the rest of the EU, consumers buying online have a statutory cooling-off period to withdraw without giving a reason, followed by a refund deadline. Put those periods literally in your returns page and in your saved reply, including the date they expire for that specific order. It removes the argument about whether something is still in time. This is not legal advice; have your return and warranty terms reviewed by a lawyer before you publish them.
The operational win sits in segmentation. Split return reasons into at least "wrong size or taste", "arrived damaged" and "different from expected". The first group is normal and comes with your category. The second is a packaging or carrier problem. The third is a product page promising too much — and you fix that group in your content, not in your helpdesk. Without that split you only see a return rate and have no idea which lever to pull.
Ready-made wording to close this chain sits in the return and refund template guide.
Handle it yourself or outsource to an ecommerce call centre
At some point the question comes up whether support should be outsourced to a BPO or ecommerce call centre. The honest version of the answer: outsourcing solves a capacity problem, not a process problem. If your process is messy, you simply buy that mess from somebody else — plus onboarding, quality control and the translation into your brand voice.
Outsourcing gets interesting once three things are true at the same time: your volume is predictable enough to staff a team against, your scenarios are documented well enough for an outsider to follow, and you can measure quality without reading along on every conversation. A brand or multibrand store shipping into several countries and time zones reaches that point sooner than a shop with one peak month a year. For the latter, outsourcing is often the most expensive answer to a problem that does not exist eleven months of the year.
The middle road most smaller webshops skip: keep the conversation in-house, but take the searching out of it. Most of the time per ticket goes into working out which order it belongs to and what was promised earlier, not into typing. Fix that first and the volume that looked "too much" often turns out to be perfectly manageable in-house. And if you do outsource later, you hand over a documented process instead of a mailbox — which is what decides whether the partnership works.
Webshop helpdesk questions
What is an ecommerce helpdesk?
An ecommerce helpdesk turns email and chat questions into tickets with an owner, status, and customer and order context.
What makes a help desk for your webshop different from a generic help desk?
A webshop question is almost never answerable without the order: where is the parcel, does that size still exist, when is the money back. A help desk for your webshop shows order and shipping data beside the conversation, so an agent does not switch between your store admin, the carrier and the mailbox. The difference shows up in peak-week response times and in how many questions are resolved in a single reply.
Which webshop platforms connect to a helpdesk?
SamDesk connects to Shopify and WooCommerce, so agents can see webshop and order context next to the conversation.
How much does a helpdesk for a webshop cost?
SamDesk uses a software plan with BYOK, so AI usage is billed by your own AI provider. See the pricing page for the current free trial route, lifetime deal, and monthly price.
See current SamDesk pricingWhat should I do when a customer reports a lost parcel?
First decide whether the shipment is delayed or genuinely lost: if tracking still moves it is a delay. Once the status has been frozen for days, open the carrier investigation yourself instead of sending the customer to call — the carrier contract is yours, not theirs. Keep the investigation and the customer thread on one ticket so everyone can see what was already promised.
What is DHL eCommerce, and should my customer call the carrier themselves?
DHL eCommerce is the parcel arm of DHL aimed at webshop-to-consumer shipments, alongside the express and freight divisions of the same group. It is a carrier service, not customer service software; the two blur in search results because "ecommerce" sits in both names. For your support process the rule matters more than the name: never send your customer to the carrier. The shipping contract is in your name, so only you can open an investigation, and a customer who calls will be told to contact the sender. That costs you the conversation twice. Open the case yourself, attach it to the same ticket, and keep the customer updated.
Should I outsource ecommerce support to a call centre or BPO?
Outsourcing solves a capacity problem, not a process problem. It pays off once volume is predictable, your scenarios are documented and you can measure quality without reading along. With a single peak month a year it is usually cheaper to take the lookup work out of your own process than to onboard an external team.
Do we need ecommerce-specific help desk software, or is a generic one fine?
Price it against your own tickets: how many minutes per conversation go into working out which order a message is about and what was already promised. One person answering a handful of messages a day is fine on a generic tool or a well-run shared mailbox. Once that lookup repeats across several conversations a day, order context beside the thread saves more time than anything else on a feature list.
