Most ecommerce support volume is repeat questions: where is my order, how do I return this, do you ship to my country. Twelve workflows cover a large share of these. Each one below lists what it needs to work and when a person should take over. Start with the two or three that match your busiest question types, measure them, then add more. Which workflows pay off depends on your own conversation mix, so tag a sample of your recent tickets first.
How do you choose which workflows to automate first?
- Tag 100 recent conversations by topic.
- Rank topics by volume, then by how predictable the answer is.
- Pick workflows where the answer comes from your own data or policy and is the same for every customer in the same situation.
- Leave judgement calls to people: exceptions, complaints, damaged goods, anything involving money beyond your standard policy.
A workflow works best when it has three parts: a trigger (what starts it), the data or policy it uses, and a clear point to hand over to a human.
The 12 workflows
1. Order status and tracking ("Where is my order?")
- Trigger: a customer asks about an order, by chat, email or WhatsApp.
- Needs: a connection to your store and carrier tracking, plus a way to verify the customer (order number and email, for example).
- Hand-off: the parcel is lost, stuck or delayed past your threshold.
- Read more: how an order tracking chatbot reduces where-is-my-order tickets.
2. Shipping costs, times and destinations
- Trigger: "How much is delivery to X?" or "Do you ship to my country?"
- Needs: your shipping rules written clearly, including countries, carriers and typical times, with a last-reviewed date.
- Hand-off: unusual destinations, bulk orders or customs questions you have not documented.
3. Return and exchange requests
- Trigger: "I want to return this."
- Needs: your return policy, return window, condition rules and how to generate a return label or form.
- Hand-off: items outside the window, damaged goods or disputes.
4. Refund status
- Trigger: "Where is my refund?"
- Needs: read-only access to refund status or a written timeline for each payment method.
- Hand-off: refunds past the stated timeline. Let a person authorise any new refund.
5. Order changes and cancellations (before dispatch)
- Trigger: "Can I change my address or cancel?"
- Needs: the order's current status and a rule for what can still be changed.
- Hand-off: orders already packed or shipped, or any change you cannot make automatically.
6. Product questions and sizing help
- Trigger: "Does this fit?" or "What is it made of?"
- Needs: accurate product data and size guides. The bot should quote your data, not guess.
- Hand-off: questions about suitability for medical or safety needs, or anything the product page does not answer.
7. Stock and back-in-stock alerts
- Trigger: "Is this available?" or "Tell me when it is back."
- Needs: live stock data and a way to record the customer's request and notify them.
- Hand-off: pre-orders or special ordering that needs a person's decision.
8. Discount codes and promotion questions
- Trigger: "My code does not work."
- Needs: the rules for each active promotion and common reasons a code fails (expired, minimum spend, excluded items).
- Hand-off: apparent system errors or goodwill requests.
9. Payment and checkout problems
- Trigger: "My payment failed" or "I cannot check out."
- Needs: a short troubleshooting guide for common causes, such as card checks, address mismatch and browser issues.
- Hand-off: repeated failures or anything involving card details. Never ask a customer to type card numbers into chat.
10. Account and login help
- Trigger: "I forgot my password" or "How do I update my details?"
- Needs: links to your self-service flows.
- Hand-off: suspected account compromise or identity checks that need a person.
11. Order confirmation, shipping and delivery updates (outbound)
- Trigger: an order event such as paid, packed, shipped or delivered.
- Needs: message templates and the customer's contact consent. WhatsApp and SMS have their own template and opt-in rules, so check each platform's current policy.
- Hand-off: replies that need judgement. Route them to a person with the order attached.
12. Lead capture and after-hours handover
- Trigger: a visitor asks something outside opening hours, or wants a quote or wholesale terms.
- Needs: a short form or chat flow that collects the details and tells the customer when to expect a reply.
- Hand-off: every lead goes to a named person with the full conversation attached.
Summary table
| # | Workflow | Main data source | Risk if wrong | Start here? |
|---|---|---|---|---|
| 1 | Order status | Store and carrier data | Low | Yes |
| 2 | Shipping info | Policy document | Low | Yes |
| 3 | Returns | Policy and returns system | Medium | After 1 and 2 |
| 4 | Refund status | Payment system, read-only | Medium | After 3 |
| 5 | Order changes | Order management | Medium | Later |
| 6 | Product questions | Product catalogue | Medium | Yes, if content is clean |
| 7 | Stock alerts | Inventory | Low | Later |
| 8 | Promotions | Promotion rules | Low | Yes |
| 9 | Checkout issues | Troubleshooting guide | Medium | Later |
| 10 | Account help | Self-service links | Low | Yes |
| 11 | Proactive updates | Order events | Medium (consent) | Later |
| 12 | Lead capture | Form and routing | Low | Yes |
What should every workflow include?
- A clear identity check before sharing order or personal details.
- A written source of truth for each policy, with an owner and a review date.
- A friendly hand-off: the customer should never be stuck in a loop. Offer a person at any time.
- Disclosure: say plainly that the customer is talking to an AI assistant.
- Logging: keep conversations so you can find mistakes and improve.
- Privacy care: collect only what is needed and follow the privacy laws that apply to your customers.
How do you roll these out without annoying customers?
- Start with one channel and two or three workflows.
- Test with staff for a week using real past questions.
- Launch to a share of visitors and read the unresolved conversations daily.
- Fix the knowledge gaps and re-test.
- Add the next workflow only when the first performs well.
- Review the numbers monthly: share resolved without a person, hand-off rate, customer ratings and repeat contacts.
If you want a way to estimate the value, use the AI chatbot ROI worksheet.
Frequently asked questions
Which support tasks are safest to automate first?
Read-only questions with clear answers: order status, shipping information, store policies and stock. They carry little risk and usually make up a large share of volume.
Do I need a developer to set these up?
Many can be set up with a no-code chatbot connected to your store. Order lookups, returns and proactive messages usually need an integration. Ask your provider which workflows are built in.
Will automation make my store feel impersonal?
Not if the hand-off is easy, the tone matches your brand and the bot answers accurately. Customers mainly want a quick, correct answer.
Can the same workflows run on WhatsApp?
Yes, if your chatbot supports the WhatsApp Business Platform. Outbound messages need approved templates and customer opt-in, so check Meta's current rules. See our WhatsApp AI chatbot setup guide.
Can DivyaSoft set these up for our store?
Yes. See our website chatbots and store assistant features and our AI services, or contact us with your store platform and your busiest question types.
Need this done for you?
Talk to the DivyaSoft team
Software, AI, video ads and digital marketing from our team in Kathmandu. Tell us what you need and we reply by email with questions or a quote.
Get new guides by email

