October 17, 2026 · askVela-Team

Ecommerce Customer Service Templates for EU Online Stores

A useful canned response saves typing without guessing at an order status or promising a return outcome. Use these editable replies with their fact checks and stop rules.

Good ecommerce customer service templates save you from rewriting the same answer. They should not supply facts you have not checked. For a Shopify or WooCommerce store selling in Europe, the useful unit is not just a pasteable paragraph: it is a reply, a list of facts to verify and a point at which an agent stops using the template.

How to use these templates without sending the wrong answer

Each template separates reply (customer-visible wording), check before sending (the source for each claim) and stop and review (when a person must handle the case). Bracketed text is an instruction to your team, not text to send. If a field cannot be verified, remove the dependent sentence or say what you will check.

Keep these checks in the internal template record, not in the message pasted to the customer. The wording below is not a determination of anyone’s legal rights; apply your reviewed procedures to the actual purchase and destination.

Order-status and delivery templates

Where is my order?

In Shopify, inspect fulfilment details separately from tracking. In WooCommerce, inspect the order status and whatever shipment information your store has recorded; do not assume the order status reflects a carrier event. If you describe a carrier update, open the tracking page first. A tracking number on its own does not establish an arrival date.

Parcel delayed after dispatch

If you have not checked the carrier page, omit the carrier sentence. Do not invent an intermediate scan or present an expected delivery window as a guaranteed date.

Marked delivered, but not received

An item is missing from an arrived parcel

Returns, withdrawals, refunds and damaged-item templates

Route these messages by what the customer wrote. A question about the return process, an explicit statement of withdrawal and a report of damage are not interchangeable. None of the replies below promises a universal outcome or refund deadline.

Routine return enquiry

Explicit withdrawal notice

Damaged item

Product, stock and pre-purchase templates

A product page can describe a different variant from the one your customer means. Name the variant and the current source before claiming availability, specifications or compatibility.

Variant availability

Compatibility question

Specification you cannot yet answer

Privacy requests and cross-border enquiries from EU customers

If someone asks to access or delete chat or order-related personal data, do not apply an order or returns macro. Record the request as received and route it through your privacy process. An acknowledgement is not a promise of immediate deletion or disclosure.

For the procedure behind that reply, see how to handle an access request for a chatbot conversation.

Turn replies into safe canned responses for your store

Keep the conditions for using a reply alongside its wording in your existing internal document or workflow. Here is a record you can copy:

Field	What to record	Delayed-parcel example
Trigger	The situation the reply covers	Dispatched order; customer asks about a delay
Approved wording	Customer-visible text with marked fields	“The carrier’s page currently says [checked update].”
Required data	Sources to inspect before sending	Correct order, shipment record, tracking page
Prohibited assumptions	Claims those sources do not establish	No invented arrival date or carrier scan
Owner	Person who handles exceptions	Delivery-support lead
Review event	Change that triggers a wording check	Delivery procedure or carrier options change

For an order-specific reply, match the customer to the correct order using your normal verification procedure. Check the relevant order and fulfilment details in Shopify, or the order status and any recorded shipment details in WooCommerce. Then verify each claim you plan to send: item or variant, payment status if relevant, shipping status, carrier, tracking link and applicable policy. If the shop has no shipment details, do not silently replace them with a guess.

In askVela, order and customer context can appear beside the conversation; order lookup is available for Shopify and WooCommerce. Check what the shop supplies before using a field in your reply. A conversation needing a person can be assigned, tagged and discussed with internal notes in the team inbox for agents. This does not mean a template sends itself or that the shop’s order status proves delivery.

Review and maintain your template library

Test each reply against its intended case and an exception: an order with no tracking link, an explicit withdrawal notice or a variant with a missing specification. If the reply still sounds certain without its source, narrow its trigger or remove the unsupported sentence.

Unverified dates: Search for “arrives”, “within” and “by”. Remove dates unsupported by tracking, a reviewed procedure or a follow-up commitment someone owns.
Blanket promises: Search for “always”, “never” and “eligible”. Replace general return or refund outcomes with a checked, order-specific next step.
Unnecessary data: Remove requests for passwords and full payment-card details. Keep identity checks within your separate approved procedure rather than requesting documents in a routine chat.
Unclear handoffs: For every “we’ll investigate”, record who takes over and which channel will carry the answer.
Changed sources: Recheck affected replies when delivery options, returns wording, product specifications or privacy procedures change.
Failed fits: If agents repeatedly rewrite a macro for the same exception, narrow its trigger or create a separate reply with its own stop rule.

Keep order-specific facts in agent replies. If customers repeatedly ask a generally applicable question, such as where to find tracking, put the stable answer in a public knowledge base and help centre and link to it from the reply. For that separate task, see how to build a knowledge base for an online store selling in Europe.

Before approving any template, ask whether an agent can identify the source for every factual sentence and see exactly when to stop using it. If not, shorten it to what you know and what you will check next.