Customer self-service for online stores
Give customers order tracking and returns they can finish themselves, with customer authentication for private details and a clear staff handover.
- Published
- Last updated
Customer self-service lets shoppers finish routine tasks themselves, from choosing a product to checking an order or requesting a return. Design each task around a clear result, with customer authentication before private order details and a direct route to staff when help is needed.
A customer who opens five help articles and still needs to ask about delivery has an unfinished task. Start with the questions your customers bring, then connect each answer to the action they need to take.
Choose tasks customers can finish themselves
Choose self-service tasks with a result you can observe, such as a customer finding a suitable product or submitting a return request. Article views show that someone opened help. Completion shows whether that help worked.
Separate tasks by the information and authority they need:
| Task | Information the customer needs | Completion result | When staff take over |
|---|---|---|---|
| Compare products | Current specifications, price and availability | Customer can choose between suitable items | A required specification is missing or conflicting |
| Understand a policy | The relevant delivery or return rule | Customer knows the applicable condition and next step | Policy wording leaves their case unresolved |
| Check an order | Access to the customer’s own order and shipment records | Customer understands the status and what happens next | Identity cannot be confirmed or the record conflicts with events |
| Start a return | Verified order access and permitted return actions | Request is recorded and its next step is explained | A dispute or exception needs a staff decision |
A customer portal is an authenticated area where customers see their own orders, status and supported return actions. Customer authentication checks who is asking. The store must also check which records and actions that person can access.
For example, Shopify’s customer accounts documentation describes signing in with an email address and a one-time six-digit code. Customers can then view the orders attached to their profile.
Use this hypothetical acceptance check when designing your portal:
- Sign in as customer A through the store’s identity check. Confirm that the portal shows customer A’s orders.
- Open one of those orders. Confirm that its permitted actions match the order’s state and the store’s rules.
- Try to open customer B’s order using its order number or copied address. The portal must withhold customer B’s private details and actions.
- Try a failed identity check. Keep private information hidden and provide a staff contact route that carries the failed task forward.
A familiar name or a typed order number alone must not grant access to another customer’s records. Staff need a separate verification process for customers who cannot access their account.
Make product and policy answers usable
Put product facts and applicable store rules beside the customer’s question, with a way to continue shopping from the answer. Use the current catalogue for specifications and stock. Delivery and return answers need the retailer’s actual policy, including the conditions that change the result.
Consider a hypothetical customer choosing a backpack for a laptop. The customer needs to compare internal dimensions with their laptop’s dimensions, then see whether the preferred colour is available. If delivery matters, the answer needs the relevant destination and delivery conditions. Keep those requirements together as the customer changes products.
The comparison can show which backpack has enough internal space and explain the trade-off in weight or capacity. The customer can then choose the available variant and continue to checkout. Asking them to repeat the laptop dimensions in a separate support form loses the context that made the answer useful.
An AI shopping agent can connect those steps. shoppa helps customers discover, compare and buy products in the chat, using the retailer’s own catalogue and documents. Customers can pay in the chat, check orders and start or track returns there too. A conversation can pass to the retailer’s staff when the customer needs a person.
Keep source information consistent wherever customers ask. If a product page and a delivery document disagree, assign someone to resolve the source conflict before the answer is used again.
Give customers control after purchase
Let customers reach their own order, understand its status and take the return actions available to them. Put the entry point in the order confirmation and somewhere customers can find on the store.
An order lookup needs a safe way to match the customer with the order. Shopify’s order-status access guidance describes account sign-in and, when prompted, verification using the order number with the checkout email address or phone number. Apply your platform’s access rules before showing private details.
Explain what a status means for the customer. In Shopify, a fulfilled order can remain Confirmed until the carrier reports that the shipment is in transit. A status answer must distinguish the store’s processing state from a carrier update. For the information to put on the page, use the order tracking page guide.
For returns, show which items the customer can select and how to submit the reason for returning them. Display confirmation that the request was received, then explain where to follow its progress. Keep Request received and Return approved as separate outcomes.
Shopify requires retailers to activate self-serve returns and give customers account access. Customers sign in to request a return, and approval is a separate step. Describe only the actions your store has enabled.
If lookup fails, ask the customer to check the order confirmation and the contact details used at checkout. Give them a route to staff if the order still cannot be matched. Keep private records hidden during the failed lookup, and never ask for a password or payment-card details in a support message.
Keep a clear handover to staff
Hand a task to staff when the customer asks for a person or the available information and permissions cannot resolve it. Give customers the contact route where the failure occurs, with an explanation of what happens next.
Escalate a delivery dispute, a conflicting policy answer or a requested action beyond the system’s permissions. For example, a customer reporting a missing parcel after a Delivered update needs investigation. Repeating the same carrier status leaves the dispute unresolved.
Carry enough context into the handover for staff to continue:
- The customer’s question and the result they want.
- The order reference and whether identity has been verified.
- The answer or error already shown, with the steps the customer tried.
- The reason for escalation and the staff team responsible for the next action.
Use your support system’s permitted fields for private information. If identity is unverified, label it that way and keep private order details out of the customer-visible conversation. Tell the customer where the reply will arrive and give a response expectation your team can meet.
Set the routing and ownership rules through your ticket escalation process. A handover is complete when a staff owner receives the context and the customer knows how to continue.
Measure completion and failed attempts
Measure whether customers finish each task, then examine repeat contacts and the reasons tasks reach staff. Keep the denominator tied to people attempting that task. A visit to a help page does not prove an attempt to track an order.
For a hypothetical measurement example, suppose customers start 100 order lookups and 82 reach their verified order status. The lookup completion rate is 82%. Review the other 18 attempts separately, including identity failures and orders that could not be matched. Track whether customers who reached a status still contacted staff about the same unresolved problem.
For returns, count a successfully submitted request separately from approval or a completed refund. For product questions, inspect whether the answer resolved the requirement and let the customer continue. A purchase can be another recorded outcome without being the only measure of useful assistance.
Use failed attempts to choose the next repair. If customers cannot find orders placed with a different email address, improve the lookup instructions and the contact route. Preserve the identity checks. If the confirmation lacks the order reference customers need, fix the confirmation too.
If customers repeatedly ask whether a sale item can be returned, inspect the policy they received. Replace ambiguous wording with the applicable rule and its exceptions, then update every answer that uses that policy. Assign an owner to each repair and retry the failed task. Close it when the customer can reach the expected result or a staff member receives a complete handover.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.