Reactive customer service answers tickets that have already been sent. Proactive customer service prevents most of those tickets from being sent at all. For a marketplace seller, the difference is measurable: a buyer who receives a tracking update before they think to ask does not send a “where is my order?” message. A buyer who gets a delivery confirmation with a simple satisfaction question is far less likely to post a negative review without first trying to resolve the problem. This guide covers the four post-purchase touchpoints that reduce the most ticket volume, and how to automate all four.
At a Glance
- Proactive CS prevents tickets before they arrive, not just answers them faster.
- WISMO is the highest-volume reactive ticket type and the most avoidable.
- Four touchpoints: order confirmation, shipping alert, delivery confirmation, return window reminder.
- Ava sends each touchpoint automatically using live order data from Amazon, eBay, and Shopify.
- A proactive Ava WISMO alert costs $0.99. A reactive WISMO ticket costs agent time and feedback risk.
- The post-purchase sequence runs once per order and reduces inbound volume across the whole buyer lifetime.
The Difference Between Reactive and Proactive Customer Service
Reactive customer service is the baseline: a buyer has a problem, they contact you, you respond. The team is always catching up. The problem with reactive-only support is not the cost of answering tickets: it is the cost of the tickets you do not answer fast enough. A WISMO query that waits four hours becomes a second follow-up ticket. A complaint that goes unanswered becomes a negative review. On Amazon, a message that crosses the 24-hour window becomes a metric violation.
Proactive support intervenes at the moments when buyers typically send those tickets. Instead of waiting for the WISMO query to arrive, you send the tracking update before the buyer thinks to ask. Instead of answering a return eligibility question, you remind the buyer about the return window before it expires. Each proactive contact replaces multiple potential reactive ones.
The 4-Touchpoint Post-Purchase Sequence
The four touchpoints below are the post-purchase communications that generate the highest ticket-deflection impact per implementation effort. Together they cover the full journey from order to return window, addressing the moment when each common reactive ticket type would otherwise be sent.
| Timing | Touchpoint | What the message covers | Ticket type it prevents |
| Day 0 | Order confirmation | Confirms the order was received; states the estimated delivery window; links to order status page | “Did my order go through?” and “when will my order arrive?” |
| Day 1-2 | Shipping notification | Confirms dispatch; provides the tracking link; explains what to do if tracking does not update within 48 hours | WISMO queries (highest-volume reactive ticket type) |
| Day 3-5 | Delivery confirmation + satisfaction prompt | Confirms delivery; asks a single satisfaction question; provides a simple contact path if something is wrong | Complaints filed without first contacting seller; negative reviews posted without prior contact |
| Day 14 | Return window reminder | Reminds the buyer of the return window; links to the returns page; confirms the process if they need to return | “Can I still return this?” and “what is your return policy?” queries |
How to Build and Automate the Sequence in eDesk
- Audit your reactive ticket volume to establish a baseline. Before building the proactive sequence, pull a breakdown of your current ticket types from eDesk reporting. Identify the top five reactive categories by volume. For most ecommerce sellers, WISMO and return-policy queries dominate. The audit tells you which touchpoints will generate the biggest deflection impact and gives you a baseline to measure against once the sequence is live. If 35% of your current tickets are WISMO queries, a successful shipping notification touchpoint should reduce that proportion.
- Configure the Day 0 order confirmation in eDesk. The Day 0 message is the first contact after purchase. It confirms the order was received, gives the estimated delivery window based on the shipping method selected, and links to the order status page or tracking portal. This message prevents two types of reactive tickets: “did my order go through?” (which arrives when the buyer has not received any confirmation) and “when will my order arrive?” (which arrives when the confirmation email does not include a delivery estimate). Configure the message in eDesk with the delivery window pulled from your connected channel’s order data.
- Set up the Day 1-2 shipping notification with Ava. The shipping notification is the highest-deflection touchpoint in the sequence. It goes out when the order enters “in transit” status and includes the tracking link, the current tracking status, and a clear instruction: what to do if the tracking does not update within 48 hours. Ava sends this message automatically using live tracking data from your connected Amazon, eBay, or Shopify channel — no manual trigger required. A buyer who receives this message has no reason to send a WISMO query unless the delivery genuinely fails or delays, which becomes a P3 ticket rather than a routine contact.
See how Ava sends proactive shipping notifications using live order data. Explore eDesk Ava proactive messaging
- Configure the Day 3-5 delivery confirmation with a satisfaction prompt. The delivery confirmation closes the delivery loop and opens a feedback channel. It confirms delivery, asks a single satisfaction question (“Was everything as expected?”), and provides a direct contact route if something is wrong. The satisfaction prompt serves two purposes. First, it catches dissatisfied buyers before they go to Amazon or eBay to leave a review, giving you the chance to resolve any issue privately. Second, buyers who answer positively are more likely to leave a review if invited to, which is a separate benefit. In eDesk, trigger this message using the delivery confirmation from your connected channel, with a configurable delay of 24-48 hours after the confirmed delivery date.
- Add the Day 14 return window reminder. The Day 14 message addresses the most common post-delivery query: “can I still return this?” It reminds the buyer that the return window is open, explains how to initiate a return if they want to, and confirms the refund timeline. For sellers with a 30-day return window, this message works best at day 14 rather than day 28, close enough to the purchase that the buyer has had time to evaluate the product but early enough that they still have time to act. Configure the message in eDesk to include your specific return instructions and the deadline for initiating a return on each channel.
- Measure proactive-to-reactive contact ratio monthly. Once the sequence is live, pull a monthly report in eDesk comparing the volume of proactive messages sent versus reactive tickets received per order. A successful proactive sequence produces a downward trend in reactive contact rate: the same number of orders generates fewer tickets over time. Track WISMO tickets specifically as the primary deflection indicator. If WISMO tickets are not declining, the Day 1-2 shipping notification is either not sending, reaching buyers too late, or not including the specific information buyers need.
The Cost Comparison That Makes the Case Internally
Reactive WISMO ticket: agent time (estimated 3-5 minutes of read, research, and write time) + Amazon SLA risk if the reply is delayed + buyer frustration that may convert to negative feedback.Proactive Ava shipping notification: $0.99 per message via Ava + goodwill from a buyer who feels informed rather than ignored.At 500 WISMO tickets per month, the proactive approach costs approximately $495 in Ava messages. The same 500 reactive tickets, answered by an agent at 4 minutes each, consume approximately 33 hours of agent time per month at any staffing cost. The proactive sequence does not just reduce ticket volume. It converts a recurring agent cost into a fixed automation cost that scales with orders, not with headcount.
What This Looks Like in Practice
A two-person team running Amazon and Shopify was handling roughly 200 support tickets per week, with WISMO queries making up approximately 40% of that volume. After implementing the four-touchpoint sequence in eDesk, with Ava sending the Day 1-2 shipping notification automatically using live tracking data, the WISMO ticket volume dropped measurably within the first month. The Day 14 return window reminder also reduced return-policy queries. The team’s total weekly ticket volume fell, and the tickets that remained were the complaints, disputes, and return requests that required a human decision rather than a status update.
Key Takeaways
- Proactive CS prevents tickets from being sent rather than just answering them faster.
- The four-touchpoint post-purchase sequence (order confirmation, shipping notification, delivery confirmation, return window reminder) addresses the most common reactive ticket types.
- The Day 1-2 shipping notification is the highest-deflection touchpoint: Ava sends it automatically using live tracking data from connected channels.
- At scale, the cost of proactive Ava messages is lower than the agent time cost of equivalent reactive WISMO tickets.
- Measure proactive-to-reactive contact ratio monthly to track deflection impact and identify which touchpoints need improvement.
FAQs
What is proactive customer service?
Proactive customer service is the practice of contacting customers before they contact you, at the moments when they would typically send a support ticket. For ecommerce sellers, the most common proactive contacts are order confirmations, shipping notifications, delivery confirmations, and return window reminders. Each replaces a category of reactive ticket: the shipping notification prevents WISMO queries, the delivery confirmation prevents complaints filed without prior contact, and the return window reminder prevents return eligibility questions.
How do I send proactive updates without contacting customers manually?
In eDesk, configure Ava to send each touchpoint in the post-purchase sequence automatically using live order data from your connected channels. The Day 1-2 shipping notification sends when the order enters “in transit” status. The delivery confirmation sends after the confirmed delivery date. The return window reminder sends at day 14. Each message is triggered by a real order event and populated with the actual order data, so buyers receive accurate, personalised messages without any manual effort from your team.
Does proactive CS reduce ticket volume?
Yes, for the ticket types that proactive communication addresses. WISMO queries, return eligibility questions, and delivery status contacts all decline when buyers receive timely, accurate updates before they think to ask. The reduction varies by the quality and timing of the proactive messages, and by how well the messages match the information buyers are actually looking for. A shipping notification that includes the tracking link and explains what to do if tracking does not update deflects more WISMO tickets than one that simply says “your order has shipped.”
Related: proactive customer support guide | reduce cart abandonment with proactive support | how to automate ecommerce customer support
Ready to build a proactive CS sequence that runs automatically on every order? Start your free 14-day trial
