Back to blog

· askVela-Team

How to Automate Repetitive Customer Support Questions in Shopify and WooCommerce

A shipping-policy question and a missing-order complaint may look equally repetitive, but they need different workflows. Here is how to tell them apart.

Updated:

To automate repetitive customer support questions in Shopify and WooCommerce, start with the information each answer requires. Your shipping policy can answer a question about destinations. A customer’s order status requires an order lookup. A disputed refund needs your team’s judgement. Put all three into the same FAQ workflow and the replies can sound certain without being reliable.

Classify repetitive questions before you automate them

Read recent conversations and note what an agent actually checked before replying. Classify by answer source, not by words such as “shipping” or “return”: either word could mean a general rule or a problem with a particular order.

Question typeCustomer wordingRequired sourceDecision rule
Published policy“Do you ship to Portugal?”Current, approved shipping termsAnswer only if the terms cover Portugal; otherwise clarify or hand over.
Live order lookup“Has my order shipped?”A matching order and the fields supplied by your shopReport the available status; do not infer dispatch from the shipping policy.
Human judgement“You refused my refund, but the item arrived damaged.”The customer’s account and a team decisionHand over. A returns article may provide context but cannot settle the dispute.

For each recurring question, record the source an agent uses today. If you cannot name one, fix the content, check the shop data or specify a handoff before writing an automated reply.

Write short answers from approved shop content

Use a current shipping page, returns instruction or product page as the source for each policy answer. Keep the reply narrower than the source: answer the customer’s situation and give an actionable next step. askVela’s knowledge base and help centre can hold searchable public articles that also provide source content for its AI answers.

For example, an article explaining where customers normally find tracking links is useful, but it does not establish whether a particular parcel has shipped. Ask the source owner to check affected answers whenever shipping destinations, return instructions or product conditions change; replace or remove obsolete pages so they cannot supply stale wording. If you need a source-article structure, see how to build a knowledge base for a shop selling in Europe.

Handle Shopify and WooCommerce order questions without guessing

“How do I find my tracking link?” can be answered from approved guidance. “Where is my parcel?” needs data about that customer’s order. askVela supports order lookup through its Shopify integration and its WooCommerce integration via a WordPress plugin. Depending on your settings, the chat requests an email address or an order number and email address. It can report order, payment and shipping details, including a tracking link, only insofar as your shop supplies them. A tracking link is not a parcel scan history.

Before relying on a lookup, inspect what your own shop returns for an order with tracking, one without tracking and a lookup that does not match. Write the reply around returned fields, not around what normally happens after fulfilment.

Do not reveal order details when the lookup fails, and do not replace a missing shipping status with a general dispatch estimate.

Set handoff rules for exceptions and customer requests

Write rules that you can test with actual customer wording:

  • “I want to speak to someone.” Hand over; do not keep offering articles.
  • “I withdraw from this purchase.” Hand over the formal request. Showing the returns policy is not the same as handling it.
  • “That fix didn’t work.” If troubleshooting still leaves the technical problem unresolved, stop repeating the guidance and hand over.
  • “What applies to my situation?” If approved knowledge is silent, ask a clarifying question when that could identify the right source. If it cannot, say the answer is unconfirmed and offer a handoff.
  • “My shipment is missing” or “I dispute this refund.” Treat any policy or tracking details as context, not as proof the complaint is resolved.

In askVela, a handoff reaches the team inbox. When the bot proposes a handoff itself, it waits for the customer’s agreement; if the customer’s email address is missing from the chat, the system asks for it first. In your tests, inspect the resulting conversation so the agent can see what the customer said, what answer was given and which order details still need checking. Do not assume every shop field accompanies the handoff.

Test the workflow before customers rely on it

Test against your own policies and shop records, and inspect both the customer reply and any resulting agent conversation. You can preview plain-text guidelines with askVela’s bot rules and test console without a real customer chat; test the connected order lookup separately.

If your shop sells in Europe, include a privacy review of which customer details the lookup requests, displays and passes to an agent. Hosting location alone does not replace your shop’s review or legal advice.

Review unanswered questions and maintain the answers

Review unanswered and escalated conversations on a recurring schedule. Keep the customer’s wording: “The chat says shipped, but there’s no tracking link” points to a different fix from “What does shipped mean?” Record the change you will make and retest the same wording.

Customer wordingCurrent answer and sourceFailure categoryOwner and changeRetest result
“Can I return an item shipped to Portugal?”Returns article does not cover the situationMissing contentPolicy owner: confirm the applicable instruction and edit the article, or require handoff[Repeat the question; record the reply]
“Your answer uses the old return address.”Obsolete returns pageStale sourceContent owner: update or remove the old page and check affected answers[Repeat the question; check the address]
“It says shipped, but there’s no tracking link.”Order status available; tracking field emptyUnavailable shop dataShop owner: check the order record; keep the handoff for missing links[Test an order without a link]
“I want to withdraw from my purchase.”Returns article shown; no handoffWrong handoffSupport lead: change the rule and inspect the resulting inbox conversation[Repeat the request; record the handoff]

askVela collects questions its bot could not answer and can turn resolved support chats into help articles. Treat both as editing inputs, not permission to publish a case-specific reply as a general rule. Have the source owner approve the article and retest the original question before using it as an answer.

Start with a policy question, an order lookup and a case requiring judgement. Expand only after each has a reliable source, a tested data path or a clear handoff.