What is aftersales service?
Aftersales service is the set of support activities a business provides after a customer has bought a product or service. It starts the moment the order is confirmed and continues for as long as the customer owns or uses what they bought.
In practice it covers order and delivery updates, setup and product help, returns and exchanges, refunds, warranty claims, repairs, spare parts and the follow-up that turns a first purchase into a second one. The terms "after-sales service", "post-purchase support" and "aftermarket service" are used for the same idea. Manufacturers tend to say aftersales. Ecommerce brands tend to say post-purchase.
A useful way to think about it: pre-sales support helps someone decide to buy. Aftersales service makes sure they are glad they did.
Aftersales service vs customer service
Customer service is the wider function. It includes pre-sales questions ("does this come in blue?"), account and billing help, and aftersales work. Aftersales service is the slice that begins after payment. For most online retailers it is also the largest slice, because every order creates a chance for a delivery question, a return or a fault.
How is aftersales service different from customer success?
Aftersales service, customer support and customer success overlap but have different jobs. Customer support answers questions and fixes problems whenever they arise. Aftersales service is the post-purchase part of that work, plus related services such as installation, repair and parts. Customer success is proactive work to help customers reach their goals, most common in software and B2B, where renewals depend on it.
| Function | Starts | Main goal | Typical measure |
|---|---|---|---|
| Customer support | Any time a customer asks | Resolve the question or problem | Resolution rate, CSAT, response time |
| Aftersales service | After payment | Deliver, fix and keep the customer happy with the purchase | Contact rate, refund time, claim rate, repeat purchase |
| Customer success | After onboarding, ongoing | Help the customer get value so they renew and expand | Retention, expansion, product adoption |
In a direct-to-consumer brand, aftersales and support are usually the same team. In a software company, support handles tickets and customer success manages accounts. In durable goods and B2B, aftersales often includes field service and parts, which may sit in operations rather than support. Whatever the structure, share one view of the customer so hand-offs do not lose context.
Why does aftersales service matter?
Aftersales service matters because it decides whether a customer buys again, and because the costs it deals with are large.
- Returns are a big line item. The NRF and Happy Returns 2024 returns report estimated that US consumers would return $890 billion of merchandise in 2024, about 16.9% of annual retail sales. Every one of those returns is an aftersales interaction.
- Retention is cheaper than acquisition. Harvard Business Review notes that, depending on the study and industry, acquiring a new customer is five to 25 times more expensive than keeping an existing one.
- Small retention gains compound. In their "Zero Defections" research, Reichheld and Sasser in Harvard Business Review (1990) found that reducing customer defections by 5% raised profits by 25% to 85% across the service businesses they studied.
- Customers are anxious after they buy. The Narvar State of Post-Purchase report found that about two-thirds of online shoppers feel anxious after they click buy. Clear updates are a support job, not just a logistics job.
The short version: a good product wins the first order, and aftersales service wins the next one.
How does aftersales service affect customer lifetime value?
Aftersales service raises customer lifetime value by increasing the chance of a second order and reducing the revenue lost to refunds and cancellations. A simple lifetime value formula shows how much a small change in repeat rate is worth.
Customer lifetime value = average order value x orders per customer x gross margin
Worked example
- Average order value: $80. Gross margin: 50%. Average orders per customer: 1.8.
- Lifetime value today: $80 x 1.8 x 0.5 = $72 of gross profit.
- Better aftersales lifts orders per customer to 2.0.
- New lifetime value: $80 x 2.0 x 0.5 = $80.
- Across 10,000 new customers a year, that is 10,000 x $8 = $80,000 more gross profit.
To see whether aftersales drives the change, compare repeat purchase rates for customers who contacted support and had a good outcome, customers who had a poor outcome, and customers who never contacted support. The gap between the first two groups is the value at stake.
What are the main types of aftersales service?
Most aftersales work falls into five groups. Mapping your conversations to these groups is the first step in any aftersales strategy.
| Type | What it covers | Typical question | Deep-dive guide |
|---|---|---|---|
| Delivery and order status | Tracking, delays, address changes, lost parcels | “Where is my order?” | WISMO guide |
| Setup and product help | Installation, onboarding, how-to, compatibility | “How do I pair this?” | This guide |
| Returns, exchanges and refunds | Eligibility, labels, exchanges, refund status | “Can I send this back?” | Returns customer service |
| Warranty and repair | Fault diagnosis, claims, replacements, repairs, parts | “It stopped working after 3 months.” | Warranty claims process |
| Loyalty and feedback | Reviews, surveys, replenishment, upgrades | “When is the refill back in stock?” | Post-purchase CX metrics |
What are the stages of the aftersales lifecycle?
The aftersales lifecycle has six stages: confirmation, fulfillment, first use, the return window, the warranty period and the loyalty phase. Each stage produces its own questions, its own risks and its own chance to earn a repeat purchase. Mapping your support work to these stages tells you where to staff, where to automate and where to send proactive messages before customers have to ask.
Stage 1: Order confirmation (minute 0 to day 1)
The customer has just paid. Their questions are about certainty: did the payment go through, is the address right, can I add an item, can I cancel. This is the cheapest stage to fix mistakes. An address corrected before the label prints costs nothing. The same correction after dispatch can mean a carrier intercept fee or a lost parcel.
- Typical contacts: order edits, cancellations, duplicate charges, missing confirmation emails, discount codes that did not apply.
- What good looks like: a confirmation email that states the delivery estimate and the cut-off time for changes, plus a self-service way to edit the address before fulfillment.
- What to automate: cancellations and address edits for unfulfilled orders, and resending confirmation emails.
Stage 2: Fulfillment and delivery (day 1 to delivery)
This is the WISMO stage, short for "where is my order". For most online retailers it is the single largest source of contacts. The questions are simple but they need live data: the tracking number, the carrier status and the promised date. Customers who get a proactive delay notice contact support far less than customers who discover the delay themselves.
- Typical contacts: tracking requests, delayed parcels, delivered-but-not-received claims, damaged boxes, split shipments.
- What good looks like: tracking links in every shipping email, a branded tracking page, and a delay message sent before the promised date passes.
- What to automate: order lookups, tracking replies, and the first step of a lost-parcel claim.
Stage 3: First use and onboarding (delivery to day 14)
The product has arrived. Now the customer has to set it up, size it, assemble it, install it or learn it. Contacts at this stage are the most product-specific, and the quality of your help content decides how many of them reach a person. A missing screw or a confusing app pairing step can generate hundreds of identical tickets in a week.
- Typical contacts: setup and installation help, sizing and fit, missing parts, "is this normal?" questions, account activation.
- What good looks like: a short getting-started email sent on delivery, product-specific help articles, and a fast path to a person for anything that looks like a fault.
- What to automate: answers from the knowledge base, missing-part replacements under a set value, and follow-up check-ins.
Stage 4: The return window (usually day 1 to day 30)
Returns and exchanges overlap with stages 2 and 3, but they deserve their own stage because they carry the most direct cost. Each return has a shipping cost, a handling cost and often a markdown when the item is resold. Exchanges keep revenue; refunds do not. A good returns process nudges toward exchanges and store credit without making refunds hard to get.
- Typical contacts: return requests, return label problems, refund status, exchange sizing, final-sale disputes.
- What good looks like: a clear policy, a self-service portal, refunds issued within a stated number of days of the item arriving back, and an exchange offer at the start of every return.
- What to automate: eligibility checks, label generation, refund status replies and refunds under a set value.
Stage 5: The warranty period (day 30 to the end of coverage)
Warranty contacts are fewer but slower and more expensive. They need evidence (photos, serial numbers, proof of purchase), a diagnosis, and a decision between repair, replacement or refund. Durable goods brands, electronics sellers and furniture makers spend a large share of their aftersales budget here.
- Typical contacts: faults, breakages, repair requests, spare parts, extended warranty questions.
- What good looks like: a claims form that collects everything needed the first time, a published decision time, and status updates at each step.
- What to automate: evidence collection, eligibility checks against the order date, and status updates. Keep a person on the approval for high-value claims.
Stage 6: Loyalty and repeat purchase (ongoing)
The final stage is where aftersales service pays for itself. A customer whose problem was solved quickly is a candidate for a review, a referral or a second order. This stage includes replenishment reminders, care and maintenance tips, accessory suggestions, subscription management and win-back outreach.
- Typical contacts: reorders, subscription changes, loyalty points, care questions, upgrade questions.
- What good looks like: follow-ups timed to real product usage, and a support team that can see the full order history in one place.
- What to automate: subscription skips and pauses, points balance lookups, reorder links.
| Stage | Share of contacts (typical ecommerce pattern) | Cost per contact | Automation fit |
|---|---|---|---|
| Confirmation | Low to medium | Low | High |
| Fulfillment and delivery | Highest | Low | Very high |
| First use | Medium | Medium | Medium to high |
| Return window | High | Medium | High for policy checks, medium for exceptions |
| Warranty period | Low | High | Medium, with human approval |
| Loyalty | Low to medium | Low | High |
Shares are a general pattern, not a benchmark. Tag a month of your own conversations by stage to get your real mix.
How should you handle "where is my order" requests?
WISMO ("where is my order") is handled best by answering before the customer asks, then answering instantly when they do. The process has four parts: proactive notifications, a self-service tracking page, an automated lookup for anyone who still writes in, and a clear exception path for delays, lost parcels and delivered-but-missing claims. Our WISMO guide goes deeper on each part.
Step-by-step WISMO process
- Send the tracking number the moment the label is created. Include the carrier name, the tracking link and the delivery estimate in plain words ("arrives Thursday or Friday").
- Send a notice when the parcel is out for delivery. This is the message customers read most closely.
- Send a delay notice before the promised date passes. Say what happened if you know, give a new estimate, and say what you will do if the new date is missed.
- Answer inbound questions with live data. The reply should include the current carrier status, the last scan location and date, and the expected delivery date. A reply that only pastes a tracking link sends the customer back to do the work themselves.
- Define the lost-parcel threshold. For example, no scan for five business days on a domestic shipment. Past that point, the conversation moves from "wait" to "we will make this right".
- Offer a remedy. Reship or refund, based on stock and the customer's preference. Record the carrier claim separately so the customer does not wait on it.
- Close the loop. When the replacement ships, send the new tracking number in the same thread.
Delivered but not received
These claims need a short, fair script. Ask the customer to check with neighbors, around the property and with anyone else at the address, and to wait 24 hours, since carriers sometimes mark parcels delivered early. If the parcel does not appear, check the proof of delivery (photo or GPS if the carrier provides it), then reship or refund according to your policy. Track repeat claims per customer so you can spot abuse without treating every customer as a suspect.
WISMO reply template
"Hi {first name}, your order {order number} left our warehouse on {ship date} with {carrier}. The latest update is: {status} in {location} on {date}. It is expected to arrive {delivery estimate}. You can follow it here: {tracking link}. If it has not arrived by {date plus buffer}, reply to this message and we will send a replacement or a refund, whichever you prefer."
The final sentence matters. It tells the customer what happens next, which removes the reason to write in again.
Where automation fits
WISMO is the easiest aftersales job to hand to an AI agent, because the answer is always in the order system and the carrier feed. Aftersales Agent can verify the customer, look up the Shopify order and reply with the real status in any of 31 languages. When a parcel crosses your lost threshold, a plain-language procedure can tell the Agent to offer a replacement under a set value, or hand the conversation to a person with the order already summarized.
What does a good returns and exchanges process look like?
A good returns process is fast for the customer, cheap for the business and steers toward exchanges. It has six steps: request, eligibility check, resolution choice, label, inspection and refund or exchange. Speed matters most at the refund step, because customers judge the whole experience by how long the money takes to come back. Our returns customer service guide has a full policy checklist and macros.
The six steps
- Request. The customer starts a return through a portal, email or chat. Collect the order number, the item, the reason (from a fixed list) and photos for damage or defects.
- Eligibility check. Compare the order date with the return window, check final-sale flags, and check the item condition rules. This step should be automatic.
- Resolution choice. Offer an exchange first, then store credit, then a refund. Some brands add a small bonus to store credit. Never hide the refund option; customers notice and it shows up in reviews.
- Label. Send a prepaid label or a QR code for drop-off, or explain who pays shipping. State the deadline to send the item back.
- Inspection. When the item arrives, check it against the condition rules. Decide on restock, refurbish or dispose.
- Refund or exchange. Issue the refund to the original payment method or ship the exchange. Tell the customer the day it happens and how long their bank usually takes.
Return reason codes worth tracking
Use a short fixed list so you can report on it: wrong size, not as described, arrived damaged, defective, changed mind, arrived late, received wrong item. Each reason points to a different fix. Wrong size points to the size guide. Not as described points to product photos and copy. Arrived damaged points to packaging or the carrier. Received wrong item points to the warehouse.
Refund before return or after?
Refunding when the carrier scans the return (rather than when it reaches the warehouse) makes customers happier and cuts "where is my refund" contacts. The risk is paying out for items that never arrive or arrive used. A common middle path: refund on first scan for customers with a clean history and orders under a set value, and refund on inspection for everyone else.
Exchange-first scripts
"Sorry the {item} did not fit. I can send the {next size} today at no cost, and you can send the original back with the prepaid label within 30 days. If you would rather have a refund, just say so and I will set that up instead."
This keeps the refund in plain view while making the exchange the easy option.
Where automation fits
Eligibility checks, label creation, refund status replies and low-value refunds are rule-based and repetitive. Aftersales Agent can check the Shopify order, apply your written return policy, create replacements, and issue Stripe refunds within the spend guardrails you set. Exceptions, such as a customer outside the window with a good reason, can escalate to a person with the policy and history already attached.
How do you run a warranty claims process?
A warranty claims process should collect all the evidence in the first contact, decide within a published number of days, and keep the customer updated at every step. The standard flow is intake, eligibility, diagnosis, decision, fulfillment and close. The biggest source of delay is going back to the customer for information you could have asked for up front. Our warranty claims process guide covers forms, policies and fraud checks in more detail.
The six-step warranty workflow
- Intake. Collect the order number or proof of purchase, the serial number if the product has one, a description of the fault, photos or a short video, and the preferred remedy. A structured form beats a free-text email every time.
- Eligibility. Check the purchase date against the warranty length, check that the product and fault type are covered, and check for exclusions such as accidental damage or misuse.
- Diagnosis. For simple products, photos are enough. For electronics or machinery, a guided troubleshooting script often solves the problem without a claim at all. Record which troubleshooting steps were tried.
- Decision. Approve a repair, a replacement, a partial refund, a full refund, or deny with a clear reason. Publish your target decision time, such as two business days.
- Fulfillment. Ship the replacement, book the repair, send the part or issue the refund. Share tracking in the same conversation.
- Close. Confirm the fix worked, record the fault code, and ask for a quick rating.
What to put in a warranty policy
- How long coverage lasts and when it starts (purchase date or delivery date).
- What is covered (manufacturing defects) and what is not (wear and tear, accidental damage, unauthorized repairs).
- What evidence the customer must provide.
- The remedies you offer and who decides between them.
- Who pays shipping for returns and replacements.
- How long decisions and repairs usually take.
- How the warranty relates to statutory rights. In the UK and EU, consumers have legal rights on faulty goods that a voluntary warranty cannot remove, so say so plainly.
Warranty reply templates
Acknowledgment: "Thanks, {first name}. I have opened warranty claim {claim number} for your {product}. Your purchase on {date} is within the {length} warranty. We will review the photos and reply with a decision by {date}."
Approval: "Good news: claim {claim number} is approved. We are sending a replacement {product} today and you will get tracking within 24 hours. You do not need to send the old one back."
Denial: "I have reviewed claim {claim number}. The photos show {observed issue}, which our warranty does not cover because {reason}. I know that is not the answer you wanted. Here is what I can offer instead: {repair option, discount on replacement, or parts}."
A denial with an alternative keeps far more goodwill than a flat no.
Where automation fits
Intake, eligibility checks and status updates are good jobs for an AI agent. The Agent can ask for photos and serial numbers in the same conversation, check the order date in Shopify, and confirm coverage from your written policy. Escalation rules can send high-value claims, legal language or angry customers to a person. The decision on expensive claims should usually stay with a human.
How should repairs and spare parts be handled?
Repairs and spare parts are the aftersales services that matter most for durable goods: appliances, electronics, bikes, furniture, tools and vehicles. The goal is to keep the product working for as long as the customer expects it to, at a lower cost than a replacement. The process splits into three paths: send-in repair, on-site repair and customer self-repair with parts.
Choosing the repair path
| Path | Best for | Customer effort | Your cost |
|---|---|---|---|
| Self-repair with a part | Simple, safe fixes (a strap, a filter, a battery, a hinge) | Medium | Lowest: the part plus postage |
| Send-in repair | Small electronics, watches, tools | Medium: packing and shipping | Medium: two-way shipping plus labor |
| On-site repair | Large appliances, installed equipment, furniture | Low | Highest: technician travel and time |
| Replacement | Low-value items, or when repair costs more than the item | Low | The unit cost plus shipping |
Running a send-in repair
- Confirm the fault with troubleshooting first. Many "broken" items are settings or setup issues.
- Issue a repair authorization number and a prepaid label. Tell the customer what to include and what to keep (chargers, cases, accessories).
- Log the arrival and send a notice the same day.
- Diagnose and quote if the repair is out of warranty. Get approval before starting.
- Repair, test and ship back with tracking.
- Follow up a week later to confirm the fix held.
Spare parts: the overlooked revenue line
Spare parts sit between service and sales. Customers who can buy a replacement part easily keep the product longer, recommend the brand and often buy accessories at the same time. The support team is usually the first to hear which parts people need, so that knowledge should flow into what you stock and sell.
- Publish a parts catalog with diagrams and part numbers, linked from product pages and help articles.
- Tag parts requests so you can see which parts fail most often. A spike in hinge requests is a product quality signal.
- Decide which parts are free under warranty and which are paid, and write it down so every agent gives the same answer.
- Stock the top ten parts that drive most requests. Long lead times on common parts create angry repeat contacts.
Right to repair
Repair rules are tightening in several markets. The EU adopted a right-to-repair directive in 2024 that requires manufacturers of certain products to offer repair beyond the legal guarantee, and several US states have passed repair laws for electronics and other goods. If you sell durable products in these markets, check with legal counsel on what parts, tools and information you must make available, and plan your aftersales operation around it.
Where automation fits
Troubleshooting from your knowledge base, part identification from a product and order lookup, repair status updates and shipping labels are all repetitive. An AI agent can guide customers through troubleshooting steps written in plain language and hand over to a technician or a person when the steps fail. Insights can flag a rise in a particular fault before it becomes a recall-sized problem.
What does good installation and onboarding support look like?
Installation and onboarding are the aftersales services that decide whether the customer ever gets the value they paid for. For physical products this means delivery, assembly and setup. For software and connected devices it means account setup, first configuration and early habits. The measure of success is time to first value: how long until the customer uses the product the way they intended.
Installation for physical products
- Book it at checkout. Let customers choose an installation slot when they buy, not after delivery. It reduces missed appointments and "when is my installer coming" contacts.
- Send a preparation checklist. Space needed, power or water connections, access for delivery, what to remove first.
- Confirm the day before. Include the time window and a way to reschedule.
- Close with a walkthrough. The installer shows the basics and leaves a quick-start card with the support contact.
- Follow up in 48 hours. Ask whether everything works. Early problems caught here avoid returns later.
Onboarding for software and connected products
- Welcome message on day 0 with one clear first step, not ten.
- Setup help on day 1 to 3 through short articles, videos and chat.
- Check-in on day 7 based on what the customer has or has not done.
- Feature introduction on day 14 to 30 for the second most useful feature.
- Health review on day 60 to 90 for higher-value accounts, often by a customer success manager.
Onboarding scripts that work
"Hi {first name}, your {product} arrived today. Most people are set up in about ten minutes. Start here: {link to the first step}. If anything looks different from the guide, reply to this message and we will help."
"Hi {first name}, it has been a week since you set up {product}. Is it working the way you hoped? If you have not tried {key feature} yet, here is a two-minute guide: {link}."
Common onboarding mistakes
- Sending the full manual on day one instead of the single next step.
- Leaving the first check-in until the customer is already frustrated.
- Treating setup questions as low priority. A setup blocker is an early return risk.
- Writing help content for experts. Write for someone opening the box for the first time.
Where automation fits
Setup questions are well suited to an AI agent trained on your help center, because the answers are documented and the customer wants them right now. Copilot helps human agents with the harder cases by drafting replies and summarizing long threads. Proactive messages, part of the Proactive add-on, can reach customers at set points in onboarding.
What should an aftersales email sequence include?
An aftersales email sequence is a set of automatic messages sent at key points after purchase. It prevents questions, sets expectations and invites the next purchase. A basic sequence has six messages; add more only if each answers a real question.
| Message | Timing | Content |
|---|---|---|
| 1. Order confirmation | Immediately | Items, total, delivery estimate, how to change the order before it ships |
| 2. Shipped | When the label is created | Tracking link, carrier, delivery estimate |
| 3. Delivered | On delivery scan | Getting-started tips, care guide, how to get help |
| 4. Check-in | 5 to 10 days after delivery | "Is everything working?" with a direct reply path |
| 5. Review request | 2 to 3 weeks after delivery | Short review ask, only if there is no open issue |
| 6. Replenish or accessory | Based on typical usage | Reorder link or a relevant accessory |
Tips
- Suppress review requests for customers with an open support conversation.
- Make every email replyable, and route replies to the support inbox, not a no-reply address.
- Write the delivered email for a first-time user, with one clear first step.
- Test the check-in email: it often surfaces problems customers would otherwise solve with a return.
Which frameworks help structure aftersales service?
Four frameworks help structure aftersales service: the service blueprint, the effort-reduction model, tiered support, and the prevent-deflect-resolve ladder. You do not need all four. Most teams get the most value from the prevent-deflect-resolve ladder, because it forces a decision on every contact type: can we stop this question from happening, can the customer answer it themselves, and if not, who resolves it fastest?
1. The prevent, deflect, resolve ladder
Take each contact reason and ask three questions in order.
- Prevent: can we remove the cause? A clearer size guide prevents fit returns. A delay email prevents WISMO. Better packaging prevents damage claims.
- Deflect to self-service: can the customer get the answer without a conversation? Tracking pages, returns portals and help articles belong here.
- Resolve: if a conversation is needed, who resolves it at the lowest cost with the best outcome? For routine, data-driven requests that is often an AI agent. For judgment calls, it is a trained person.
Run the ladder once a quarter using your top 20 contact reasons. The list changes as products, carriers and policies change.
2. The service blueprint
A service blueprint maps what the customer sees (front stage), what your team does (back stage) and the systems that support it, for one journey such as a return. Draw it on a single page with five rows: customer actions, front-stage touchpoints, back-stage actions, support systems, and evidence (emails, labels, receipts). Blueprints show hand-offs where things get lost, such as the gap between the warehouse receiving a return and finance issuing the refund.
3. Effort reduction
The idea behind customer effort is simple: customers are more loyal when getting help is easy. Research published in Harvard Business Review ("Stop Trying to Delight Your Customers", Dixon, Freeman and Toman, 2010) argued that reducing effort does more for loyalty than exceeding expectations. In aftersales terms, effort comes from repeating information, switching channels, waiting, and being transferred. Audit each journey for those four things.
- Repeating information: pass order details and conversation history with every hand-off.
- Switching channels: resolve in the channel the customer chose where possible.
- Waiting: set and publish response targets per channel.
- Transfers: give the first responder enough authority to finish most requests.
4. Tiered support
Traditional tiers split work by complexity. In a modern aftersales team the tiers look like this:
| Tier | Who | Handles |
|---|---|---|
| Tier 0 | Self-service and AI agent | Order status, policy questions, eligible returns, simple refunds, setup answers |
| Tier 1 | Generalist agents | Exceptions, emotional conversations, multi-order issues |
| Tier 2 | Specialists | Warranty decisions, technical faults, fraud reviews, carrier claims |
| Tier 3 | Product, operations, engineering | Root causes, recalls, system bugs |
The key design choice is what the AI agent in tier 0 is allowed to do. If it can only answer questions, most requests still reach tier 1. If it can take actions such as order edits, replacements and refunds within limits, far more requests end at tier 0.
Choosing a framework
Small teams should start with the ladder and a simple policy document. Teams above ten agents benefit from blueprints for their top three journeys. Tiering matters once you have specialists. Effort reduction is a lens to apply across all of them, not a separate project.
What does an aftersales escalation matrix look like?
An escalation matrix tells everyone, including the AI agent, who handles what and how fast. Keep it on one page and review it quarterly.
| Situation | Handled by | Target response |
|---|---|---|
| Order status, policy question, eligible return | AI agent | Instant |
| Refund or replacement under the spend limit | AI agent | Instant |
| Refund or replacement over the limit | Tier 1 agent approval | Same business day |
| Strong negative sentiment or repeat contact | Tier 1 agent | Within 2 hours |
| Warranty decision above a set value | Claims specialist | 2 business days |
| Safety, injury or health concern | Support lead, same day | Within 1 hour |
| Legal language, regulator, formal complaint | Complaints owner | Same business day |
| Suspected fraud pattern | Claims specialist | 1 business day |
| VIP or contract account | Named account team | Per contract |
In Aftersales, most of this matrix maps directly to escalation rules (sentiment, keywords, tier and legal language) and spend guardrails, so the AI agent follows the same routing as the team.
What are examples of good aftersales service?
Good aftersales service is specific, fast and does the task rather than describing it. Here are common examples by business type.
Ecommerce and DTC brands
- A shipping notification with a live tracking link, plus a proactive message when the carrier reports a delay.
- A self-serve returns portal that shows eligibility, issues a label and states when the refund will land.
- An exchange offered before a refund, so the customer keeps the product they wanted in the right size.
- A support reply that already contains the order number, items and tracking status, so the customer does not repeat themselves.
Consumer electronics and appliances
- Setup guides and short troubleshooting flows that solve common faults before a claim is raised.
- A warranty claim form that asks for serial number and proof of purchase once, then tracks the claim to a replacement or repair.
- Spare parts and accessories that are easy to find and order.
Automotive and equipment
- Service reminders, booking and status updates while the item is in the workshop.
- Clear quotes for out-of-warranty work before it starts.
SaaS and subscriptions
- Onboarding help in the first weeks, when most cancellations are decided.
- Billing changes, refunds and plan downgrades handled in the conversation rather than through a form.
The common thread is that the customer gets an outcome, not a policy link. See our ecommerce and SaaS pages for how Aftersales handles these flows.
What does great aftersales service look like in practice?
The clearest way to see good aftersales service is to follow a single request from start to finish. The five scenarios below are composites of common situations, not specific companies. Each shows the weak version most customers have experienced and the strong version that resolves the request in one contact.
Scenario 1: a late parcel
Weak: The customer waits past the estimate, emails, and gets a reply two days later with a tracking link they already had. They email again. A different agent asks for the order number.
Strong: The brand detects the carrier delay and sends a message before the promised date with a new estimate. The customer still asks on chat; the AI agent verifies them, reads the live status, confirms the new date and states the remedy if it slips again. One contact, under two minutes.
Scenario 2: a shoe that does not fit
Weak: The customer has to find the returns page, print a label, post the shoes, wait for inspection, get a refund ten days later, then buy again and hope the new size is in stock.
Strong: The customer tells chat the shoes are too small. The agent checks the order, confirms it is within the window, offers the next size and ships it today, with a prepaid label for the original. The sale is kept and the customer has the right size within days.
Scenario 3: a coffee machine that will not heat
Weak: The customer describes the problem and is told to return it for inspection. They are without coffee for three weeks.
Strong: The agent walks through two troubleshooting steps from the knowledge base. The second step, a descaling cycle, fixes it. If it had not, the agent would collect the serial number and a video, confirm the warranty from the order date and ship a replacement the same week.
Scenario 4: a sofa delivered with a torn seam
Weak: The customer is asked to keep the sofa wrapped until a collection can be arranged in two weeks, then waits six weeks for a new one.
Strong: The customer sends two photos. The team offers a choice: a repair visit this week, a partial refund to keep it as is, or a replacement with collection. The customer picks the partial refund. The damage photo is tagged to the carrier and flagged to operations for a packaging review.
Scenario 5: a subscription renewal the customer forgot
Weak: The customer is charged, disputes the charge with their bank, and the brand loses the fee and the customer.
Strong: A reminder goes out three days before renewal with a skip link. The customer writes back that they still have stock. The AI agent moves the next delivery by a month. The subscription survives.
In each strong version the same pattern appears: the right data in front of whoever responds, a written policy, authority to act, and a clear statement of what happens next.
How do you build an aftersales service strategy?
Build it in five steps: map demand, set policies, choose the channel for each job, automate what is repetitive and measure outcomes. We call this the MAP-SAM framework.
1. Map demand
Export three months of conversations and tag each one with a type from the table above. Most teams find that a handful of intents (order status, return request, damaged item, refund status, how-to) make up the majority of volume. That list becomes your automation backlog.
2. Adopt clear policies
Write down the rules an agent (human or AI) must follow: return window, who pays shipping, when to refund vs replace, warranty length, evidence required for damage claims. If two agents would answer the same question differently, the policy is not written yet.
3. Pick the channel for each job
Not every job belongs in the same place. Order updates work best as proactive email or SMS. Returns work best in a portal or chat that can issue a label. Warranty diagnosis often needs photos, so chat, email or WhatsApp works better than phone.
4. Streamline and automate
For each high-volume intent, decide: can it be prevented (a better shipping email), self-served (a portal) or resolved by an AI agent that can read and act on the order? Keep humans for judgment calls, upset customers and exceptions.
5. Analyze and measure
Track resolution rate, first contact resolution, CSAT, time to resolution, return rate and repeat purchase rate. Review the reasons behind contacts every month and feed them back to product, operations and logistics.
See which aftersales questions Agent can resolve. Start on the Free plan with 50 Agent resolutions included.
How should aftersales strategy change as a company grows?
The right aftersales strategy depends on company size. Early-stage brands need simple policies and one inbox. Scaling brands need automation and reporting. Large brands need governance, specialist teams and real-time issue detection.
| Stage | Focus | Typical Aftersales setup |
|---|---|---|
| Early (under 1,000 orders a month) | Clear policies, fast replies, founder-level care | Free or Starter, AI Agent on chat and email |
| Scaling (1,000 to 20,000 orders) | Automation of WISMO and returns, templates, basic reporting | Growth with Agent across channels, Copilot for agents |
| Established (20,000+ orders) | Specialist teams, QA, forecasting, root-cause fixes | Growth or Scale, Insights Pro, Proactive |
| Enterprise and regulated | Security, compliance, SSO, data residency | Scale, or Agent inside an existing Zendesk, Salesforce or Freshdesk setup |
What should an aftersales service policy include?
An aftersales policy should state, in plain language, what the customer can expect after buying and what they need to do. Use this template as a starting point.
- Delivery: dispatch times, carriers, how tracking is shared, what happens if an order is late or lost.
- Returns: window in days, condition of items, non-returnable items, who pays return shipping, how refunds are issued and how long they take.
- Exchanges: whether exchanges ship before the return arrives, and any size or color limits.
- Warranty: length, what is covered and excluded, proof required, repair vs replace rules.
- Damaged or wrong items: how to report, evidence needed (photos), time limit to report.
- Support hours and channels: where to get help and expected response times.
- Escalation: how a customer reaches a senior person if they disagree with an outcome.
Publish it in your help center and feed the same text to your AI agent, so customers get the same answer everywhere.
How do you write shipping and warranty policies?
Beyond the returns policy, most businesses need two more aftersales documents: a shipping policy and a warranty policy. Keep each on one page, in plain words, with the key numbers at the top. Below are outlines you can adapt. Have them reviewed by counsel for your markets.
Shipping policy outline
- Processing time: "Orders placed before 2pm on business days ship the same day."
- Delivery times and costs by region, in a small table.
- Tracking: when and how the customer gets it.
- Delays: what you will do if a parcel is late, and after how long a parcel counts as lost.
- Delivered but not received: the steps and your remedy.
- Address changes: the cut-off and how to request one.
- International orders: duties, taxes and who pays them.
Warranty policy outline
- Coverage length and when it starts.
- What is covered and what is not, with examples.
- How to claim: the form or channel and the evidence needed.
- Remedies: repair, replacement or refund, and how you choose.
- Timelines: decision time and typical repair or replacement time.
- Shipping costs for claims.
- Legal rights statement for each market you sell in.
Keeping policies in sync
Every policy lives in four places: the public page, the help center, the agent templates and the AI procedures. When one changes, all four must change on the same day. Keep a simple change log with the date, the change and who updated each place.
What are good aftersales reply templates?
Good aftersales replies confirm the facts, state the outcome and give the next step. Three reusable macros:
Order delayed
Hi {first_name}, thanks for checking in. Your order {order_number} left our warehouse on {ship_date} and the carrier now expects delivery on {new_eta}. Here is your tracking link: {tracking_url}. If it has not arrived by {eta_plus_2}, reply here and we will send a replacement or refund, whichever you prefer.
Damaged item
Hi {first_name}, I am sorry your {item} arrived damaged. Thanks for the photo. I have sent a replacement today (order {replacement_number}) and you do not need to return the damaged one. You will get tracking by email within 24 hours.
Warranty claim received
Hi {first_name}, we have logged warranty claim {claim_id} for your {product} (serial {serial}). Next step: {next_step}. We will update you by {date}. Nothing else is needed from you right now.
More templates live in the WISMO, returns and warranty guides.
What aftersales scripts and templates should every team have?
A good aftersales template library covers the ten situations that produce most conversations, and each template states what happened, what you are doing and what happens next. Below are ready-to-edit scripts for email and chat. Replace the braces with your data, keep sentences short, and give agents (and your AI agent) permission to adjust tone to the customer.
1. Order delayed (proactive)
"Hi {first name}, a quick update on order {number}. It is running {x} days behind because {reason}. The new estimate is {date}. You do not need to do anything. If it has not arrived by {date}, we will send a replacement or a refund, your choice."
2. Address change request
"Done. I have updated the address on order {number} to {address}. It has not shipped yet, so it will go straight there. You will get tracking when it leaves." If the order has shipped: "It left our warehouse this morning, so I cannot change it here. I have asked {carrier} to redirect it, which usually works. If it does not, I will reship to the new address at no cost."
3. Damaged on arrival
"I am sorry it arrived like that. Could you send one photo of the item and one of the box? As soon as I have them I will send a replacement. You do not need to return the damaged one."
4. Wrong item received
"That is our mistake, sorry. I am sending the correct {item} today with express shipping. Here is a prepaid label for the wrong one, and there is no rush on sending it back."
5. Refund status
"Your refund of {amount} was issued on {date} to your {payment method}. Banks usually take 3 to 5 business days to show it. If it is not there by {date}, reply here and I will send you the transaction reference to share with your bank."
6. Outside the return window
"Your order is {x} days past our {window}-day return window, so I cannot offer a standard refund. What I can do is {store credit, exchange, or partial refund}. Would that help?"
7. Missing part
"Sorry about that. I am sending the missing {part} today, and it should arrive by {date}. Here is the tracking: {link}. In the meantime, {workaround if any}."
8. Product not working (first contact)
"Let us get this working. Could you try {step 1} and {step 2}? That fixes most cases. If it still does not work, send me a short video and the serial number from {location} and I will start a warranty claim right away."
9. Subscription change
"All set. Your next delivery has moved from {date} to {new date}. You will get a reminder three days before it ships, and you can change it again anytime from {link}."
10. Angry customer, repeat contact
"You should not have had to write to us three times about this, and I am sorry. I have read the full thread. Here is what I have done: {action}. Here is what happens next: {next step and date}. I will personally check this on {date}."
Rules for writing aftersales templates
- Lead with the answer or the action, not an apology paragraph.
- Use real data (dates, amounts, tracking) rather than generic lines.
- Always say what happens next and when.
- Give one option or two, not five.
- Avoid policy jargon such as "RMA" unless customers already use it.
- Review templates every quarter against CSAT comments.
Phone scripts
Phone calls need the same structure spoken aloud. Open with a name and an offer to help, verify the customer with the order number and email, restate the problem in one sentence, act, then summarize and confirm the next step. Aftersales supports phone with transfers and recording on Growth and Scale plans, so calls land in the same Inbox as email and chat.
How do you handle difficult aftersales conversations?
Difficult aftersales conversations, such as a third contact about the same problem, a denied claim or a customer threatening a chargeback, go best when the agent acknowledges the history, takes ownership, acts and commits to a specific next step. Defending the policy first almost always makes things worse.
A five-step approach
- Read the whole history before replying, so the customer does not have to repeat anything.
- Acknowledge specifically. "You have contacted us three times about this refund" works better than a general apology.
- Act first, explain second. Do whatever you can do right now, then explain what remains.
- Give a date and a name. "I will check on {date} and update you." Then do it.
- Record the root cause so the same failure does not hit the next customer.
When the answer is no
Say no clearly, give the reason in one sentence, and offer the best alternative you can. Customers accept a fair no more readily than a vague maybe followed by silence. If a customer mentions legal action or a regulator, pass the conversation to the person responsible for complaints and do not argue the point in the thread.
How do you measure aftersales service?
Measure outcomes for the customer and costs for the business. The core set:
| Metric | What it tells you | Formula |
|---|---|---|
| Resolution rate | Share of conversations fully solved | Resolved conversations ÷ total conversations × 100 |
| First contact resolution (FCR) | Solved without a follow-up | Resolved on first contact ÷ total resolved × 100 |
| CSAT | Satisfaction with the interaction | Positive ratings ÷ total ratings × 100 |
| Contact rate | Support demand per order | Conversations ÷ orders × 100 |
| Return rate | Share of orders or units sent back | Units returned ÷ units sold × 100 |
| Repeat purchase rate | Loyalty after the first order | Customers with 2+ orders ÷ total customers × 100 |
The full list with benchmarks-by-method and pitfalls is in our post-purchase CX metrics guide. For how we count AI outcomes, see resolution rate explained.
Which aftersales KPIs should you track, and how are they calculated?
The KPIs that matter most in aftersales service are resolution rate, first contact resolution, time to resolution, CSAT, cost per conversation, contact rate per order, return rate and repeat purchase rate. Each has a simple formula. Track them weekly by contact reason, not just in total, because a single average hides where the problems are. Our post-purchase CX metrics guide goes deeper on benchmarks and dashboards.
Core formulas
| KPI | Formula | What it tells you |
|---|---|---|
| Contact rate | Conversations / orders x 100 | How many orders create work. The best single measure of aftersales health. |
| Resolution rate (AI) | Conversations resolved by the AI agent without a person / all conversations the agent handled x 100 | How much work automation actually finishes. |
| First contact resolution | Conversations resolved in one reply or session / all resolved conversations x 100 | Whether customers have to come back. |
| First response time | Median time from customer message to first reply | Speed perception. Use median, not mean. |
| Time to resolution | Median time from first message to resolved | The number customers actually feel. |
| CSAT | Positive ratings / all ratings x 100 | Satisfaction per conversation. |
| Cost per conversation | (Labor + software + AI usage) / conversations | Efficiency. Compare before and after changes. |
| Cost per order | Total support cost / orders | Support cost in the terms finance uses. |
| Return rate | Items returned / items sold x 100 | Product, sizing and description quality. |
| Exchange share | Exchanges / (exchanges + refunds) x 100 | How much return revenue you keep. |
| Refund time | Median days from return received to refund issued | A leading cause of repeat contacts. |
| Warranty claim rate | Claims / units sold in the period x 100 | Product reliability. |
| Reopen rate | Reopened conversations / resolved conversations x 100 | Whether resolutions were real. |
| Repeat purchase rate | Customers with 2+ orders / all customers in the cohort x 100 | Whether aftersales is earning the next order. |
Worked example: contact rate and cost per order
A store ships 20,000 orders a month and receives 3,000 conversations. Its contact rate is 3,000 / 20,000 = 15%. If it spends $18,000 a month on support labor and tools, its cost per conversation is $18,000 / 3,000 = $6.00 and its cost per order is $18,000 / 20,000 = $0.90.
Now suppose proactive delay emails cut WISMO contacts by 600 a month. Contact rate falls to 2,400 / 20,000 = 12%. Even if cost per conversation stays at $6.00, the store saves 600 x $6.00 = $3,600 a month. Prevention often beats efficiency.
Worked example: resolution rate
An AI agent handles 2,000 conversations in a month. It resolves 1,300 without a person and hands 700 to the team. Its resolution rate is 1,300 / 2,000 = 65%. Across Aftersales customers, the median resolution rate after 90 days is 71%, and it usually rises over the first three months as procedures and knowledge improve. See our resolution rate guide for how to measure it fairly.
How to avoid misleading metrics
- Report by contact reason. A great average CSAT can hide a terrible returns experience.
- Use medians for time metrics. One stuck ticket can wreck an average.
- Pair speed with quality. Fast first responses that do not resolve anything raise contact volume.
- Count reopens. A resolution that comes back in two days was not a resolution.
- Define "resolved" for AI carefully. A conversation where the customer gave up is not resolved. Look for confirmation or no reply after a real answer, and check a sample by hand.
A weekly aftersales dashboard
Keep it to one screen: contact rate, conversations by stage, AI resolution rate, median time to resolution, CSAT by reason, refund time, and the top five rising topics. Aftersales Insights covers real-time issue detection, quality monitors and forecasting, so a spike in "damaged" conversations after a packaging change shows up the same day.
How should you survey customers after an aftersales contact?
Post-resolution surveys should be short, sent right after the conversation closes, and tied to the contact reason so the results are actionable. One rating question and one optional comment box is enough for most teams.
- Ask one main question. "How satisfied are you with the help you received?" on a 1 to 5 scale, or a simple good or bad rating.
- Add an optional "what could we do better?" The comments are more useful than the score.
- Send in the same channel as the conversation, within minutes.
- Tag results by reason and by who resolved it (AI or person) so you can compare fairly.
- Separate service from policy. A customer refused a refund outside the window may rate low even if the agent was excellent. Read the comments before judging the agent.
- Close the loop on low scores. A follow-up from a team lead on a bad rating often recovers the customer.
For effort, add a customer effort question on key journeys: "How easy was it to get your issue resolved?" Effort scores tend to point straight at process problems such as repeated information and transfers.
How do you calculate the ROI of aftersales improvements?
The return on an aftersales improvement is the cost saved plus the revenue kept, minus what the change costs. Calculate it per change, not only for the whole program, so you know which changes to repeat.
ROI = (cost saved + revenue protected - cost of change) / cost of change x 100
Worked ROI example: adding an AI agent
- Conversations: 3,000 a month. Current cost per conversation: $5.00, so $15,000 a month.
- The AI agent resolves 60%, or 1,800 conversations, at $0.99 each: $1,782 a month.
- Human workload falls by 1,800 conversations. At $5.00 each that is $9,000 of labor capacity freed, which can be redeployed or not backfilled as the team grows.
- Net monthly saving: $9,000 - $1,782 = $7,218.
- If setup takes 40 hours of staff time at $50 an hour, the one-off cost is $2,000. First-month ROI: ($7,218 - $2,000) / $2,000 x 100 = 261%.
Add revenue effects where you can measure them, such as more exchanges or fewer subscription cancellations after a support contact. Keep the assumptions visible so finance can check them.
What does a monthly aftersales review look like?
A monthly aftersales review turns the dashboard into decisions. Here is what one looks like for a fictional mid-size store, to show how the numbers connect. The figures are illustrative, not benchmarks.
| Metric | Last month | This month | Read |
|---|---|---|---|
| Orders | 25,000 | 27,000 | Growth of 8% |
| Conversations | 3,500 | 3,510 | Flat despite growth |
| Contact rate | 14.0% | 13.0% | Proactive delay emails working |
| AI resolution rate | 58% | 64% | New returns procedure live |
| Median time to resolution | 6 hours | 3 hours | More instant AI resolutions |
| CSAT | 86% | 88% | Up on returns, down on damage |
| Refund time | 6 days | 4 days | Refund-on-scan pilot |
| Damage contacts | 210 | 340 | Spike after new packaging supplier |
What the team decides
- Damage spike: operations reviews the new packaging this week; support sends a proactive note to customers with open orders from the affected batch.
- Returns procedure: results are good, so the refund limit for the AI agent rises from $50 to $75.
- Next automation: warranty claim intake is the largest remaining manual reason, so the team writes a procedure for evidence collection and eligibility checks.
- Staffing: with volume flat and AI resolution rising, the team does not backfill a departing agent and moves budget to a part-time QA role.
This is the value of reviewing by reason: the headline CSAT went up while one journey got worse, and only the breakdown shows it.
Who should own aftersales service?
Customer support should own the conversation, but aftersales outcomes depend on several teams. The most common failure is a support team that sees every problem and controls none of the fixes.
| Aftersales job | Support owns | Partner team owns |
|---|---|---|
| Delivery updates | Answering and escalating delivery questions | Operations and logistics: notifications, carrier performance |
| Returns and exchanges | Applying the policy, handling exceptions | Finance and merchandising: policy, refund rules, return reasons |
| Warranty and repair | Intake, troubleshooting, status updates | Product and quality: coverage, fault analysis, suppliers |
| Product help | Answers and how-to content | Product and marketing: documentation, packaging inserts |
| Loyalty | Service recovery, feedback capture | Marketing and retention: reviews, replenishment, offers |
How to run it week to week
- Weekly: support shares the top contact reasons, with volume and examples, in a short note to operations and product.
- Monthly: each partner team picks one reason to reduce, and support tracks whether contacts for it fall.
- Quarterly: review the policies (returns window, warranty remedies, delay compensation) against what customers actually ask for.
Staffing for aftersales
Aftersales volume follows orders, with a lag. Contacts about delivery peak a few days after a sale, returns a week or two later and warranty claims months later. Plan staffing around order forecasts, not last week's queue, and let an AI agent absorb the repetitive peaks so people stay on the exceptions.
If you sell in regulated industries, such as fintech or healthcare, involve compliance early: refund rules, identity checks and data handling all touch aftersales conversations. Aftersales is SOC 2 Type II and GDPR compliant, and HIPAA-ready with a BAA on the Scale plan.
How do you staff and budget an aftersales team?
Aftersales staffing starts from volume: forecast conversations, subtract what automation resolves, divide by what one agent handles, then add cover for breaks, training and absences. Cost follows from three parts: people, software seats and usage-based AI fees. Most teams find the AI share of the cost is small compared with labor, which is why automation changes the budget so much.
Step 1: forecast conversations
Conversations = orders x contact rate. Add seasonal peaks. Many retailers see two to three times normal volume in the weeks after Black Friday and the holidays, driven by WISMO and returns.
Step 2: subtract automated resolutions
Human conversations = conversations x (1 - AI resolution rate x share of conversations the AI handles). If the AI agent sees every conversation and resolves 60%, humans handle 40%.
Step 3: divide by productivity
A full-time agent handling email and chat typically closes somewhere in the range of 40 to 80 conversations a day, depending on complexity and tools. Use your own history. Agents needed = human conversations per day / conversations per agent per day.
Step 4: add shrinkage
Shrinkage covers time agents are paid but not handling conversations: meetings, training, breaks, leave and sickness. It is often 25% to 35%. Staffed agents = agents needed / (1 - shrinkage).
Worked staffing example
- Orders: 30,000 a month, contact rate 12%, so 3,600 conversations a month, about 164 per working day (22 days).
- Without AI: 164 / 50 per agent = 3.3 agents, divided by 0.7 for shrinkage = 4.7, so 5 agents.
- With an AI agent resolving 60% of all conversations: 66 human conversations a day / 50 = 1.3 agents, divided by 0.7 = 1.9, so 2 agents.
The 3 agents saved can move to higher-value work: warranty decisions, VIP customers, quality reviews and improving the knowledge the AI uses.
Cost model: what an aftersales team really costs
Here is the same store priced out. Assume a fully loaded agent cost of $4,000 a month (adjust for your market).
| Line | Without AI | With Aftersales Agent |
|---|---|---|
| Agents | 5 x $4,000 = $20,000 | 2 x $4,000 = $8,000 |
| Software seats (Aftersales Growth, $69/seat annual) | 5 x $69 = $345 | 2 x $69 = $138 |
| AI resolutions (60% of 3,600 = 2,160 x $0.99) | $0 | $2,138 |
| Monthly total | $20,345 | $10,276 |
| Cost per conversation | $5.65 | $2.85 |
Illustrative. Your agent cost, productivity and resolution rate will differ. Aftersales prices from our pricing page; conversations the Agent cannot help with are not charged.
That is in line with the direction of real results: Northwind Outdoors cut its cost per conversation by 41% with Aftersales. Savings depend on your mix of contacts, so model it with your own numbers.
In-house, outsourced or hybrid?
| Model | Strengths | Weaknesses | Best for |
|---|---|---|---|
| In-house | Product knowledge, brand voice, fast feedback to product teams | Hard to flex for peaks, higher fixed cost | Brands where the product is complex or premium |
| Outsourced (BPO) | Flexible capacity, 24/7 cover, lower hourly rates in many markets | Less product depth, quality control takes effort, per-contact fees add up | High-volume, simple contacts |
| Hybrid with AI | AI covers routine volume 24/7, a small in-house team covers judgment calls | Needs good policies and knowledge to work well | Most growing ecommerce and DTC brands |
Planning for peaks
- Forecast peak weeks from last year's volume by day, adjusted for order growth.
- Move proactive messages earlier so questions never arrive.
- Use Lite seats for staff from other teams who help during peaks. Aftersales includes 20 free Lite seats on Growth and 50 on Scale.
- Let the AI agent absorb the routine surge so people can focus on exceptions.
How do you hire and train aftersales agents?
Aftersales agents need three skills above all: clear writing, calm judgment and comfort with systems. Product knowledge can be taught; tone and judgment are harder to train. As AI takes more routine work, the human role shifts toward exceptions, emotional conversations, quality review and improving procedures, so hire for those.
A two-week onboarding plan for new agents
- Days 1 to 2: products, policies and the customer lifecycle stages.
- Days 3 to 4: tools, the inbox, order systems, and how the AI agent hands over.
- Days 5 to 7: shadow experienced agents, then answer with review before sending.
- Days 8 to 10: handle live conversations on one channel with daily feedback.
- Days 11 to 14: full queue, first QA review, and one improvement suggestion to the knowledge base.
Roles in a growing aftersales team
- Support agents: exceptions and complex conversations.
- Claims specialist: warranty, damage and carrier claims.
- Support operations or AI lead: procedures, knowledge, guardrails and reporting.
- QA lead: reviews and coaching, often part-time in smaller teams.
- Support lead: policy, budget and the link to product and operations.
Which channels should aftersales service cover?
The right aftersales channels are the ones your customers already use, backed by a single inbox so the context follows the customer. For most online brands that means email and live chat as the core, WhatsApp and SMS for delivery updates and quick questions, social messages for public-facing brands, and phone for high-value or urgent cases. Each channel has a natural job.
| Channel | Best aftersales use | Response target to aim for | Watch out for |
|---|---|---|---|
| Returns, warranty claims with photos, anything needing a record | Same business day | Long threads and slow back-and-forth | |
| Live chat | Order status, quick policy questions, setup help | Under 2 minutes | Customers leaving if queues are long |
| Delivery updates, photo-based damage claims, markets where it is the default | Within an hour | Messaging template rules for outbound messages | |
| SMS | Delivery alerts, appointment reminders, short replies | Within an hour | Character limits and opt-in rules |
| Social messages | Customers who reach out publicly | Within a few hours | Moving private data out of public comments |
| Phone | Urgent, high-value, complex or emotional cases | Under 3 minutes to answer | Highest cost per contact |
| Self-service | Tracking pages, returns portals, help center | Instant | Dead ends with no route to a person |
One inbox, many channels
The biggest channel mistake is running each channel in a separate tool. The customer who emailed yesterday and chats today should not have to explain again. The Aftersales Inbox brings email, live chat, WhatsApp, SMS and social into one place, with phone including transfers and recording on Growth and Scale. The AI Agent works across the same channels, so a customer gets the same answer and the same actions wherever they write in.
Should you offer phone support?
Offer it if your average order value is high, if your customers are older or less comfortable with chat, or if problems are urgent (a broken fridge, a failed installation). Otherwise, many brands keep phone for callbacks booked through chat. Whatever you choose, state it clearly on the contact page so customers are not hunting for a number.
What is proactive aftersales service?
Proactive aftersales service means contacting customers before they have to contact you: shipping updates, delay warnings, setup tips on delivery, refund confirmations, recall notices and renewal reminders. It is the most effective way to lower contact rate, because every message that answers a question in advance removes a conversation. It also changes how the brand feels: customers notice when a company tells them bad news first.
The proactive message calendar
| Trigger | Message | Contacts it prevents |
|---|---|---|
| Order placed | Confirmation with delivery estimate and change cut-off | "Did my order go through?", edit requests |
| Label created | Tracking link and carrier | WISMO |
| Carrier delay detected | Delay notice with new estimate and remedy | WISMO, complaints |
| Out for delivery | Delivery day notice | Missed deliveries |
| Delivered | Getting-started tips and support link | Setup questions, early returns |
| Return received | Confirmation and refund date | "Where is my refund?" |
| Refund issued | Amount, method, bank timing | Refund status questions |
| Known product issue | Explanation and fix or offer | Fault reports, returns |
| Before renewal or reorder | Reminder with skip or change link | Unwanted charges, refund requests |
Rules for proactive messages
- Send only what is useful. Every message should answer a real question.
- Deliver bad news early with a remedy attached.
- Let customers reply to any message and reach support in the same thread.
- Respect channel rules and opt-ins, especially for SMS and WhatsApp.
- Measure the effect: compare contact rate for customers who got the message with those who did not.
The Aftersales Proactive add-on ($99 a month) sends targeted outbound messages, and because replies land in the same Inbox, the AI agent or a person can pick up the conversation with full context.
How do you build an aftersales knowledge base?
An aftersales knowledge base should answer the top 20 post-purchase questions in plain language, with one article per question and the answer in the first sentence. It serves three audiences: customers who self-serve, human agents who need consistent answers, and the AI agent, which can only be as accurate as the content it draws on. A strong knowledge base is the cheapest way to raise AI resolution rates.
Articles every aftersales help center needs
- How to track my order
- What to do if my order is late or lost
- How to change my address or cancel an order
- How to start a return or exchange
- When will I get my refund
- What to do if my item arrived damaged or wrong
- How the warranty works and how to make a claim
- How to get a spare part
- Setup and care guides for your top products
- How to manage or pause a subscription
- Shipping costs, times and countries
- How to contact us and when we reply
How to write an article that works for people and AI
- Title as a question the customer would type.
- Answer in the first sentence. "Refunds are issued within 3 business days of your return arriving at our warehouse."
- Add conditions next. Exceptions, time limits, regional differences.
- Give steps as a numbered list when there is an action.
- Keep one topic per article so it can be found and quoted cleanly.
- Date and own every article. Someone should review it when the policy changes.
Knowledge versus procedures
Knowledge tells the customer what is true ("our return window is 30 days"). Procedures tell the AI agent what to do ("if the order is within 30 days, create a return label"). Keep both, and keep them consistent. When a policy changes, update the article and the procedure on the same day. Aftersales keeps Knowledge and Workflows in the same platform, which makes that easier to manage.
Finding gaps
Every conversation a person handles is a hint about what the knowledge base or procedures are missing. Review escalated conversations weekly, group them by reason, and write or fix the article or procedure that would have resolved them.
How do you run quality assurance on aftersales conversations?
Quality assurance in aftersales service means reviewing a sample of conversations against a short scorecard, coaching on patterns rather than single mistakes, and applying the same standard to human agents and the AI agent. A team that reviews even 2% to 5% of conversations every week catches policy drift, tone problems and wrong answers long before they show up in reviews or chargebacks.
A simple aftersales QA scorecard
| Criterion | Question the reviewer asks | Weight |
|---|---|---|
| Correct resolution | Was the outcome right under the policy? | 30% |
| Completeness | Were all the customer's questions answered in one go? | 20% |
| Next step clarity | Did the customer know what happens next and when? | 15% |
| Verification and data | Was the customer verified and were order details accurate? | 15% |
| Tone | Was it clear, human and on brand? | 10% |
| Process | Were tags, notes and escalations done correctly? | 10% |
How to choose which conversations to review
- A random sample for a fair picture.
- Every conversation rated poorly by the customer.
- Every conversation that was reopened.
- A targeted sample from any new procedure or policy change.
- A weekly sample of AI agent conversations, split between resolved and escalated.
Coaching that changes behavior
Share two or three examples a week in a short team session: one great conversation, one that went wrong, and what the better version looks like. Focus on patterns ("we are not stating refund dates") rather than blame. Update the template or procedure that caused the problem, so the fix lasts beyond the meeting.
QA for AI conversations
AI conversations need the same scorecard, plus two extra checks: did the agent hand over when it should have, and did it stay inside the spend guardrails? Aftersales Insights includes quality monitors that flag conversations for review, so the sample is not only random but aimed at likely problems.
How do you turn aftersales conversations into product and operations fixes?
Aftersales conversations are the richest source of product and operations feedback most companies have. Turning them into action takes three things: consistent tagging by reason, a monthly report to the teams that can fix causes, and a named owner for each fix. Without that loop, support keeps answering the same question forever.
Who needs what from aftersales data
| Team | Signal from aftersales | Typical fix |
|---|---|---|
| Product | Faults, confusing setup, missing features | Design changes, better instructions |
| Merchandising and marketing | "Not as described" returns, sizing complaints | New photos, fit notes, clearer copy |
| Operations and warehouse | Wrong items, damage, missing parts | Pick and pack checks, packaging changes |
| Logistics | Delays and losses by carrier or region | Carrier changes, realistic delivery estimates |
| Finance | Refund volume, chargebacks, warranty cost | Policy adjustments, fraud rules |
| Leadership | Contact rate, cost per order, CSAT | Budget and priority decisions |
The monthly root-cause report
- Top ten contact reasons, with volume and change from last month.
- The three biggest rises, with example conversations.
- Estimated cost of each top reason (volume x cost per conversation, plus refunds and replacements).
- Fixes in progress, with owners and dates.
- Fixes completed last month and their measured effect.
Spot problems in days, not months
Monthly reports are too slow for some problems. A bad batch of product, a warehouse mistake or a carrier failure can produce hundreds of contacts in a day. Real-time issue detection, such as Aftersales Insights, alerts the team to a spike in a topic as it happens, so the fix, and a proactive message to affected customers, can start the same day.
How can aftersales service generate revenue?
Aftersales service makes money in three ways: it protects revenue (exchanges instead of refunds, saves on cancellations), it creates revenue (spare parts, extended warranties, service contracts, accessories, repeat orders) and it cuts cost (fewer contacts, faster resolutions). Treating aftersales as a revenue line, not only a cost center, changes what you measure and what you invest in.
Protecting revenue
- Exchanges and store credit: every exchange keeps the sale. Track exchange share monthly.
- Cancellation saves: offering a delay, a pause or a swap keeps subscriptions that would otherwise end.
- Fast fixes: a replacement part shipped the same day often prevents a full return.
Creating revenue
- Spare parts and accessories: customers ask support first. Make parts easy to buy.
- Extended warranties and protection plans: common in electronics and appliances. Make sure support can explain them clearly and handle claims well, or they create resentment.
- Service contracts: in B2B and durable goods, maintenance agreements provide recurring income and keep equipment running.
- Repeat purchase: a well-handled problem is a strong moment to earn trust. Avoid hard selling in the same message; a follow-up a few days later works better.
Worked example: value of a better exchange flow
A fashion brand processes 2,000 returns a month with an average item value of $60. Today 25% become exchanges. After adding an exchange-first flow, 35% become exchanges. That keeps 200 more sales a month, or 200 x $60 = $12,000 in monthly revenue that would have been refunded. Even after extra shipping for exchanges, the gain is large compared with the cost of the change.
Cutting cost without cutting quality
The cost side comes from prevention and automation. Aftersales Agent is charged at $0.99 per resolution, only when it resolves the conversation. Compare that with your current cost per conversation (often several dollars once labor is included) to see the gap. Northwind Outdoors cut cost per conversation by 41% with Aftersales.
How does aftersales service differ by industry?
Aftersales service looks different in every industry because the product, the price and the risk differ. Fashion is dominated by returns and sizing. Electronics is dominated by setup and faults. Furniture is dominated by delivery and damage. Software is dominated by onboarding and renewals. The playbooks below show the top contact reasons, the process that matters most and the metrics to watch for each.
Fashion and apparel
- Top contacts: order status, sizing and fit, returns and exchanges, refund status, discount problems.
- The process that matters most: exchange-first returns. Every exchange keeps revenue that a refund loses.
- Prevention levers: size guides with body measurements, fit notes from reviews ("runs small"), model height and size in photos.
- Metrics: return rate by product, exchange share, refund time, WISMO contact rate.
- Automation fit: very high. Most contacts are order lookups and policy checks, which suits an AI agent with Shopify actions.
Consumer electronics and gadgets
- Top contacts: setup and pairing, "not working" reports, warranty claims, firmware questions, accessories.
- The process that matters most: guided troubleshooting before a warranty claim. Many faults are setup issues.
- Prevention levers: quick-start cards in the box, a setup video, a day-one onboarding email.
- Metrics: warranty claim rate by SKU, no-fault-found rate on returned units, first contact resolution.
- Automation fit: high for troubleshooting and claim intake, medium for decisions.
Furniture and home goods
- Top contacts: delivery scheduling, long lead times, damage on arrival, missing hardware, assembly help.
- The process that matters most: damage handling. Decide in advance when to send a part, when to send a replacement and when to offer a partial refund to keep a lightly damaged item.
- Prevention levers: accurate lead times at checkout, delivery confirmation calls, packaging tests, hardware packs taped to the right panel.
- Metrics: damage rate by carrier, delivery reschedule rate, parts request rate.
- Automation fit: high for scheduling updates and parts requests, medium for damage claims.
Outdoor, sports and equipment
- Top contacts: sizing, product care, warranty claims on wear items, spare parts, seasonal order spikes.
- The process that matters most: clear warranty rules on what counts as wear and tear versus a defect.
- Prevention levers: care guides, repair programs, published parts lists.
- Metrics: claim rate, repair turnaround, peak-season response time.
- Automation fit: high. Northwind Outdoors, an Aftersales customer, cut its cost per conversation by 41%.
Beauty, health and consumables
- Top contacts: subscription changes, reactions and ingredient questions, shipping, reorders.
- The process that matters most: subscription self-management and a careful escalation path for any mention of a reaction or health concern.
- Prevention levers: clear ingredient lists, patch-test guidance, reminders before a subscription renews.
- Metrics: subscription churn after a support contact, reorder rate, escalations for safety topics.
- Automation fit: high for subscriptions and orders. Use escalation rules on keywords so health and safety questions always reach a trained person.
Automotive and vehicles
- Top contacts: service bookings, parts availability, warranty and recall questions, finance and documents.
- The process that matters most: service booking and reminders, since service revenue often outlasts the vehicle sale margin.
- Prevention levers: automated service reminders by mileage or date, parts availability shown before booking.
- Metrics: service retention rate, parts fill rate, booking lead time.
- Automation fit: medium to high for bookings and status updates. Confirm dealer management system integrations on a call.
B2B equipment and manufacturing
- Top contacts: service contracts, field service visits, spare parts orders, technical support, uptime issues.
- The process that matters most: service level agreements with clear response and repair times, tracked per account.
- Prevention levers: preventive maintenance schedules, operator training at installation, parts kits for common wear items.
- Metrics: mean time to repair, first-time fix rate for field visits, contract renewal rate, parts revenue.
- Automation fit: medium. AI helps with parts identification, triage and status updates. Complex diagnosis stays with engineers.
Software and SaaS
- Top contacts: onboarding, how-to questions, billing, bugs, account access.
- The process that matters most: onboarding to first value, and a clean bug escalation path to engineering.
- Prevention levers: in-app guides, a strong help center, status page for incidents.
- Metrics: time to first value, ticket rate per active account, net revenue retention.
- Automation fit: high for how-to questions from documentation. See our SaaS page.
Financial services and fintech
- Top contacts: card and account issues, transaction disputes, verification, fees.
- The process that matters most: secure identity verification and compliant handling of complaints and disputes.
- Metrics: complaint resolution time, dispute outcomes, repeat contact rate.
- Automation fit: medium, with strict escalation for legal language and vulnerable customers. Aftersales is SOC 2 Type II and GDPR compliant. See our fintech page.
Healthcare products and services
- Top contacts: device setup, supply reorders, appointment and delivery questions, insurance paperwork.
- The process that matters most: privacy-safe handling of health information and fast escalation for clinical questions.
- Automation fit: medium, with human review on anything clinical. Aftersales is HIPAA-ready with a BAA available on the Scale plan. See our healthcare page.
| Industry | Biggest aftersales cost | First thing to fix |
|---|---|---|
| Fashion | Returns | Size guidance and exchange-first flow |
| Electronics | Faults and no-fault-found returns | Guided troubleshooting |
| Furniture | Damage and delivery | Packaging and damage rules |
| Consumables | Subscription churn | Self-service subscription changes |
| Automotive | Lost service revenue | Service reminders |
| B2B equipment | Downtime | Preventive maintenance and SLAs |
| SaaS | Early churn | Onboarding to first value |
How is B2B aftersales service different from B2C?
B2C and B2B aftersales service share the same stages but differ in who the customer is, how much each relationship is worth and how formal the commitments are. B2C aftersales is high-volume, low-value per contact and driven by policy. B2B aftersales is lower-volume, higher-value per account and driven by contracts and service level agreements.
| Dimension | B2C | B2B |
|---|---|---|
| Volume | Thousands of similar requests | Fewer, more varied requests |
| Commitments | Published policies | Contracts and SLAs |
| Contacts per account | One buyer | Several users, a buyer and a finance contact |
| Main revenue link | Repeat purchase and reviews | Renewals, service contracts, parts |
| Channels | Chat, email, social, WhatsApp, SMS | Email, phone, portal, account manager |
| Automation fit | Very high | Medium, strongest on triage and status |
Many brands now do both, for example a furniture maker that sells to homes and to offices. Keep separate procedures and escalation rules for each, while using one inbox so nobody loses the account history. In Aftersales, escalation rules can route by customer tier, so a contract account goes straight to its named team.
How does aftersales service work for subscription businesses?
Subscription businesses have a distinct aftersales pattern: fewer delivery questions per order, but many account changes, and each cancellation loses future revenue rather than one sale. The aim is to make changes easy, so customers adjust instead of cancelling.
- Self-service controls: skip, pause, swap product, change frequency and update address without contacting support.
- Pre-renewal reminders: three days before each charge, with links to change it.
- Save offers: when a customer asks to cancel, offer a pause or a frequency change first, and cancel promptly if they still want to. Making cancellation hard creates chargebacks and complaints, and in some markets breaks the rules.
- Failed payment handling: friendly retry messages with an easy card update link.
- Measure churn after contact: compare cancellation rates for customers who contacted support with those who did not.
An AI agent with order actions can make most subscription changes in the conversation, which is faster for the customer than finding the right setting in an account page.
What consumer laws affect aftersales service?
Consumer law sets the floor for aftersales service, and your policies can be more generous but not less. The rules differ by country, so treat this section as orientation and check specifics with a lawyer. The areas that matter most are statutory rights on faulty goods, cooling-off periods for online purchases, warranty disclosure, and data protection.
Key rules by region (orientation only)
- European Union: online buyers generally have a 14-day right of withdrawal under the Consumer Rights Directive, and a legal guarantee of conformity of at least two years for goods. A commercial warranty adds to these rights and cannot replace them.
- United Kingdom: the Consumer Contracts Regulations give a 14-day cancellation period for most online purchases, and the Consumer Rights Act 2015 gives remedies for faulty goods, including a 30-day short-term right to reject.
- United States: there is no general federal right to return online purchases, so the store policy governs. Written warranties on consumer products are regulated by the Magnuson-Moss Warranty Act, and the FTC enforces rules on shipping timelines (the Mail, Internet, or Telephone Order Merchandise Rule).
- Australia: the Australian Consumer Law provides consumer guarantees for goods and services that stores cannot exclude.
What this means for your aftersales operation
- Write policies that state legal rights plainly alongside your own terms.
- Train agents, and write procedures for the AI agent, so that a legally entitled customer is never refused.
- Set escalation rules on legal language so formal complaints reach a trained person.
- Keep records: conversation history, decisions and dates.
- Protect personal data. Choose tools with strong credentials. Aftersales is SOC 2 Type II and GDPR compliant, with data residency on Scale.
How do you prevent returns and warranty abuse?
Returns and claims abuse is real, but most customers are honest, so the goal is to catch patterns without making every customer prove innocence. Common forms include wardrobing (wearing and returning), false "not received" claims, returning a different or used item, and serial damage claims. The fix is rules based on history and value, applied quietly, with human review for edge cases.
Practical controls
- History thresholds: route customers with repeated claims in a set period to manual review.
- Value thresholds: require photos or returns for high-value items, and approve low-value claims instantly.
- Evidence at intake: photos, serial numbers and packaging images reduce both fraud and back-and-forth.
- Carrier proof: check delivery scans and photos before reshipping on "not received" claims.
- Consistent decisions: written procedures stop agents from being talked into exceptions case by case.
Using AI safely here
An AI agent can apply these rules the same way every time. Aftersales spend guardrails cap what the Agent can refund or replace, and escalation rules can send any customer over a claims threshold to a person. That keeps honest customers fast and gives your team time to look properly at the unusual cases.
How should you prepare aftersales service for peak season?
A peak season aftersales plan prepares for two waves: a WISMO wave during shipping and a returns wave after the holidays. The playbook is to forecast volume by day, send proactive messages early, extend self-service, let the AI agent absorb routine volume and keep people for exceptions. Start planning at least eight weeks ahead.
Eight weeks out
- Forecast daily volume from last year, adjusted for order growth and new channels.
- Set holiday shipping cut-off dates and publish them.
- Decide on extended holiday return windows and update all policies and procedures.
Four weeks out
- Update help articles and templates for holiday topics: gift returns, gift receipts, cut-offs.
- Load holiday procedures into the AI agent and test them.
- Recruit and train temporary help. Use free Lite seats for colleagues from other teams.
During peak
- Check the top rising topics every day and send proactive messages for any new issue.
- Hold a 15-minute daily stand-up to review backlog, escalations and any policy exceptions.
- Protect first response time on chat; move complex cases to email with a clear promise.
After peak
- Handle the returns wave with exchange-first flows and fast refunds.
- Run a review: what drove volume, what worked, what to change next year.
How do you deliver aftersales service internationally?
Selling across borders adds three aftersales problems: language, local rules and logistics. Customers expect support in their language, local return rights differ, and cross-border returns are slow and expensive. The practical answers are multilingual AI support, local return addresses or returnless refunds for low-value items, and policies written per region.
- Language: hiring native speakers for every market is costly. An AI agent that works in the customer's language covers routine questions in all markets. Aftersales Agent supports 31 languages, and Copilot translates for human agents on the harder cases.
- Time zones: AI covers nights and weekends; set clear hours for human support and state them.
- Returns: offer local drop-off where volumes justify it. For low-value items, a refund without return can be cheaper than international shipping.
- Duties and taxes: explain who pays and how refunds of duties work. It is a common source of confusion.
- Policies: keep one policy page per region that reflects local rules, and make sure procedures pick the right one by the customer's country.
How do you handle aftersales for marketplace orders?
If you sell on marketplaces as well as your own store, aftersales gets more complex because each marketplace has its own rules, messaging system and deadlines. Keep your own policies consistent where marketplace rules allow, and track marketplace response deadlines closely, since late replies can affect seller ratings. Route marketplace messages into your main inbox where the platform allows it, and confirm specific marketplace integrations with any vendor before you buy. For Aftersales, confirm niche integrations on a call.
How does aftersales service support repair, resale and recycling?
Aftersales service is also where a business decides what happens to products after the first owner is done with them. Repair, refurbishment, resale and recycling can cut waste and recover value, and customers increasingly ask about them.
- Repair first: a spare part or a repair often costs less than a replacement and keeps the product in use.
- Refurbish returns: grade returned items and resell as open-box or refurbished where possible.
- Returnless refunds with care: for low-value items, letting the customer keep or donate the item can be cheaper and produce less transport waste than shipping it back.
- Take-back and trade-in: offer credit for old products to encourage the next purchase and responsible disposal.
- Tell customers: put repair and recycling options in the help center so support can point to them.
What does a mature aftersales operation look like?
Aftersales maturity runs from reactive to predictive across five levels. Knowing your level helps you pick the next step instead of trying to do everything at once.
| Level | What it looks like | Next step |
|---|---|---|
| 1. Reactive | Shared email inbox, no tags, answers vary by agent | One helpdesk, basic tags, written policies |
| 2. Organized | Helpdesk, templates, response targets | Self-service tracking and returns, help center |
| 3. Self-service | Portals and articles deflect simple questions | AI agent with order actions and procedures |
| 4. Automated | AI resolves most routine conversations, people handle exceptions | Proactive messages and root-cause reporting |
| 5. Predictive | Issues detected early, volume forecast, fixes flow to product and operations | Continuous improvement each quarter |
Most growing ecommerce brands are at level 2 or 3. The jump from 3 to 4 usually delivers the largest cost change, because it moves routine volume from people to an AI agent that can act.
Where does AI fit in aftersales service?
AI fits aftersales service best where the answer depends on data you already hold and a policy you have already written: order status, returns eligibility, refunds within limits, subscription changes, setup questions and claim intake. It fits least where the outcome is a judgment call, a legal matter or an emotional situation. The practical question is not whether to use AI but what it is allowed to do, and when it must hand over.
Three kinds of AI in aftersales
| Type | What it does | Example in Aftersales |
|---|---|---|
| AI agent | Talks to the customer and resolves the conversation end to end, including actions | Agent: verifies the order in Shopify, creates a replacement, issues a Stripe refund |
| AI copilot | Helps a human agent write, summarize and translate | Copilot: drafts replies, summarizes long threads, translates |
| AI analytics | Finds patterns and problems across conversations | Insights: real-time issue detection, quality monitors, forecasting |
Answering versus acting
Older chatbots answered questions from a script or a help center. That handles "what is your return policy?" but not "please return my order". Most aftersales requests are the second kind. An agent that can take actions, within limits you set, resolves far more conversations. The limits matter: spend guardrails cap refunds and replacements, and escalation rules decide when a person steps in.
Writing procedures an AI agent can follow
Aftersales Agent uses plain-language procedures, written the way you would brief a new hire. A good procedure has a trigger, the checks to run, the actions allowed and the escalation points.
Example procedure: damaged item.
- When a customer reports a damaged item, verify the order and the item.
- Ask for one photo of the item and one of the packaging.
- If the order is within 30 days and the item value is under $80, create a free replacement and tell the customer they can keep the damaged item.
- If the item value is $80 or more, or the customer has had more than two damage claims this year, hand over to the claims team with a summary.
- If the customer mentions injury, a safety issue or a lawyer, hand over immediately.
Escalation rules to set on day one
- Sentiment: strongly negative messages go to a person.
- Keywords: words like "chargeback", "lawyer", "injury", "fire", "allergic".
- Customer tier: VIP or B2B accounts go to their named team.
- Legal language: formal complaints and regulatory terms.
- Spend limits: anything above the guardrail needs approval.
What results to expect
Across Aftersales customers, the median resolution rate after 90 days is 71%. Rates start lower in the first weeks and rise as you fill knowledge gaps and add procedures. The fastest gains usually come from connecting order actions early, because WISMO and returns are such a large share of aftersales volume.
Risks and how to manage them
- Wrong answers: keep the knowledge base current and review a sample of AI conversations weekly.
- Over-generous actions: start with low spend limits and raise them as you see results.
- Customers who want a person: always honor a clear request for a human.
- Language coverage: test your top languages. Aftersales supports 31.
- Data protection: check security credentials. Aftersales is SOC 2 Type II and GDPR compliant, HIPAA-ready with a BAA on Scale, and offers SSO, SAML, SCIM and data residency on Scale.
How Aftersales handles it
- Agent resolves conversations end to end and takes actions: it can verify orders, run order actions and send replacements in Shopify, issue refunds in Stripe and work with Salesforce. It follows plain-language procedures, escalation rules (sentiment, keywords, tier, legal language) and spend guardrails, in 31 languages.
- Copilot drafts replies, summarizes long threads and translates for human agents.
- Inbox brings email, live chat, WhatsApp, SMS and social into one shared helpdesk, with phone on Growth and above.
- Insights spots new issues in real time, such as a spike in damaged-item reports from one warehouse.
Agent is priced at $0.99 per resolution, counted once per conversation, and conversations it cannot help with are free. Aftersales customers see a median 71% resolution rate after 90 days, and Northwind Outdoors cut cost per conversation by 41%. If you already use Zendesk, Salesforce Service Cloud or Freshdesk, Agent can run inside it with no seats or migration.
What is the best aftersales service software, and how do prices compare?
Aftersales service software falls into four groups: helpdesks (shared inbox, tickets, macros), AI agents (automated resolution), post-purchase tools (tracking pages, returns portals) and analytics. Most teams need a helpdesk and an AI agent at minimum. Aftersales combines both in one platform with Agent, Copilot, Inbox, Insights, Workflows and Knowledge, priced per seat plus $0.99 per AI resolution. The table below compares it with the tools aftersales teams most often shortlist.
Aftersales plans and pricing
| Plan | Price (annual) | Key inclusions |
|---|---|---|
| Free | $0 | 1 seat, live chat and email inbox, first 50 Agent resolutions free, help center |
| Starter | $24 per seat/month | Shared inbox, AI Agent at $0.99 per resolution |
| Growth (most popular) | $69 per seat/month | Phone with transfers and recording, 20 free Lite seats |
| Scale | $109 per seat/month | 50 free Lite seats, SSO/SAML/SCIM, data residency, HIPAA BAA |
| AI Agent | $0.99 per resolution | Every plan, counted once per conversation. Conversations it cannot help with are free. |
| Add-ons | Copilot $29/rep/mo, Proactive $99/mo, Insights Pro $99/mo | Copilot is $35 billed monthly |
Monthly billing is 20% more than annual. 14-day free trial. Full details on the pricing page.
Feature comparison
| Capability | Aftersales | Intercom | Zendesk | Gorgias | Freshdesk |
|---|---|---|---|---|---|
| Pricing model | Per seat from $24 + $0.99 per AI resolution; free plan | Per seat $29 to $132 + $0.99 per Fin outcome | Per agent $19 to $115+ plus AI automated resolutions | By ticket volume, $10 to $750/mo, plus AI Agent fees | Per agent $19 to $89, AI sessions beyond included allowance |
| AI agent that takes actions | Yes: Shopify order actions, replacements, Stripe refunds, Salesforce | Yes (Fin) | Yes (AI agents) | Yes (AI Agent, Shopify-focused) | Yes (Freddy AI Agent) |
| AI charged only when it resolves | Yes, unhelped conversations are free | Per outcome | Per automated resolution | Per automated interaction | Per session |
| Copilot for human agents | $29/rep/mo | $29/agent/mo add-on | $50/agent/mo add-on | Check vendor | $29/agent/mo add-on |
| Channels | Email, chat, WhatsApp, SMS, social; phone on Growth+ | Broad | Broad | Broad, ecommerce-focused | Broad |
| Free collaborator seats | 20 Lite (Growth), 50 (Scale) | Check vendor | Check vendor | Unlimited users on all plans | Check vendor |
| Run AI inside your current helpdesk | Yes: inside Zendesk, Salesforce Service Cloud or Freshdesk | Yes (Fin standalone) | n/a | No | n/a |
| Issue detection and forecasting | Insights included, Insights Pro $99/mo | Reporting on higher plans | Analytics on higher plans | Revenue statistics on Pro+ | Analytics on higher plans |
| Languages for AI | 31 | Check vendor | Check vendor | Check vendor | Check vendor |
| Security | SOC 2 Type II, GDPR, HIPAA-ready (BAA on Scale) | Check vendor | Check vendor | Check vendor | Check vendor |
Competitor plan prices checked October 2026 on vendor pricing pages and public pricing summaries: Intercom Essential $29, Advanced $85, Expert $132 per seat; Zendesk Support Team $19, Suite Team $55, Suite Professional $115 per agent; Gorgias Starter $10, Basic $50, Pro $300, Advanced $750 per month; Freshdesk Growth $19, Pro $55, Enterprise $89 per agent, all billed annually. AI usage rates change often; confirm current prices on each vendor's site.
Worked cost example: 5 agents, 2,000 conversations a month
Assume the AI resolves 60% of conversations (1,200) and the team wants a mid-tier plan with phone or advanced features.
| Tool and plan | Seats or base | AI usage | Monthly total |
|---|---|---|---|
| Aftersales Growth | 5 x $69 = $345 | 1,200 x $0.99 = $1,188 | $1,533 |
| Aftersales Starter | 5 x $24 = $120 | 1,200 x $0.99 = $1,188 | $1,308 |
| Intercom Advanced | 5 x $85 = $425 | 1,200 x $0.99 = $1,188 | $1,613 |
| Intercom Expert | 5 x $132 = $660 | 1,200 x $0.99 = $1,188 | $1,848 |
| Zendesk Suite Professional | 5 x $115 = $575 | Automated resolution rate not published on main page | $575 + AI usage |
| Gorgias Pro | $300 (2,000 tickets) | AI Agent billed per automated interaction on top | $300 + AI usage |
| Freshdesk Pro | 5 x $55 = $275 | Sessions beyond the included allowance at $49 per 100 | $275 + sessions |
Annual billing. Excludes Copilot and other add-ons. Illustrative; model your own volume.
What the numbers show
- Against Intercom, Aftersales costs less at every comparable tier: $80 a month less at Growth versus Advanced in this example, and $315 less against Expert, with the same $0.99 AI rate and the same Copilot price.
- Against Zendesk, Aftersales Growth seats cost $46 less per agent than Suite Professional, and Copilot is $29 instead of $50 per agent. With 5 agents on Copilot, that is another $105 a month saved.
- Against Gorgias and Freshdesk, the helpdesk base can be cheaper on paper. Gorgias Pro covers 2,000 tickets for $300 with unlimited users, and Freshdesk Pro seats are $55. If you mostly need a helpdesk with light AI, those can be the better value. The difference shows up when AI does most of the work: Aftersales only charges when the Agent resolves the conversation, counts it once, and charges nothing for conversations it cannot help with.
- If you want to keep your helpdesk, Aftersales Agent runs inside Zendesk, Salesforce Service Cloud or Freshdesk with no seats or migration, at $0.99 per resolution with a minimum monthly commitment.
When another tool is the better pick
- Gorgias if you are a small Shopify store that wants unlimited users on a ticket-based plan and low AI volume.
- Zendesk if you run a very large, complex operation with years of Zendesk configuration and a big marketplace of apps you rely on. You can still add Aftersales Agent inside it.
- Freshdesk if you want the lowest per-agent helpdesk price and have modest AI needs.
- Intercom if your aftersales is mainly in-product messaging for software users and you already use Intercom for onboarding campaigns.
For deeper comparisons, see Aftersales alternatives, best ecommerce helpdesk, best post-purchase support tools and our pricing breakdowns for Intercom, Zendesk, Gorgias and Freshdesk.
Other tools in the aftersales stack
- Tracking pages and shipping notifications for proactive WISMO prevention. See best WISMO automation tools.
- Returns portals for self-service labels and exchanges. See best returns management software.
- Review and survey tools for post-resolution feedback.
- Field service tools for on-site repairs and installations in durable goods and B2B.
Price your own aftersales stack.Start on the Free plan with 50 Agent resolutions, or run a 14-day trial of Growth. See pricing.
What should you look for in aftersales service software?
When choosing aftersales service software, test it against your real conversations, not a demo script. Use this checklist in trials.
- Actions, not just answers. Can the AI verify orders, edit or cancel, create replacements and issue refunds in your systems?
- Controls. Can you set spend limits, escalation rules by sentiment, keywords, tier and legal language?
- Procedures in plain language. Can a support lead change a policy without an engineer?
- Channels. Does it cover the channels your customers use, in one inbox?
- Languages. Does the AI handle your top markets?
- Pricing clarity. What exactly triggers an AI charge? Is it per resolution, per outcome, per session or per interaction, and are failed conversations charged?
- Total cost at your volume. Price seats, AI usage and add-ons for your real numbers, including peak months.
- Migration. Can you keep your current helpdesk and add AI inside it, or does it need a full move?
- Reporting. Can you see resolution rate, contact reasons and issue spikes without exporting data?
- Security. SOC 2, GDPR, and if relevant HIPAA, SSO and data residency.
Aftersales answers each point directly: Shopify, Stripe and Salesforce actions; spend guardrails and escalation rules; plain-language procedures; email, chat, WhatsApp, SMS, social and phone in one Inbox; 31 languages; $0.99 per resolution with unhelped conversations free; seats from $24; Agent inside Zendesk, Salesforce Service Cloud or Freshdesk; Insights; and SOC 2 Type II, GDPR and HIPAA-ready security. For niche integrations, confirm on a call.
How do you switch aftersales software without disruption?
Moving to new aftersales software takes two to six weeks for most teams, and you can reduce risk by running old and new tools side by side for a short period. If a full move is not worth it, adding an AI agent inside your existing helpdesk is the lower-risk option.
- Inventory: list channels, macros, tags, automations, integrations and reports you use today.
- Clean up: retire macros nobody uses and merge duplicate tags before moving anything.
- Connect systems: order platform, payments, CRM, shipping.
- Rebuild: templates, routing and procedures in the new tool.
- Import history if you need it for context.
- Pilot: move one channel or one team first.
- Switch: move remaining channels, update contact pages and email forwarding.
- Review: compare KPIs with your baseline after 30 days.
Aftersales Agent can also run inside Zendesk, Salesforce Service Cloud or Freshdesk with no seats and no migration, at $0.99 per resolution with a minimum monthly commitment. Many teams start there and decide on a full move later.
How can a small business offer strong aftersales service?
A small business can run strong aftersales service with one person and the right setup. The priority order is: written policies, proactive shipping emails, a short help center, one inbox for every channel, and an AI agent to cover nights, weekends and routine questions.
- Start free. The Aftersales Free plan includes one seat, live chat and an email inbox, the first 50 Agent resolutions and a help center.
- Write five procedures for your most common requests before anything else.
- Set response hours and state them. Customers accept waiting when they know how long.
- Batch the rest. Handle escalated conversations in two blocks a day rather than all day.
- Grow into Starter at $24 per seat per month when you add a second person.
How do you implement a better aftersales service in 90 days?
A realistic aftersales improvement plan takes about 90 days in four phases: measure (weeks 1 to 2), fix the basics (weeks 3 to 6), automate (weeks 5 to 10) and optimize (weeks 10 to 13 and beyond). The phases overlap on purpose. You can start automating WISMO while you are still rewriting the returns policy, as long as each automated flow rests on a written procedure.
Phase 1: Measure (weeks 1 to 2)
- Export the last 90 days of conversations and tag a sample of at least 300 by contact reason and lifecycle stage.
- Calculate your baseline: contact rate, first response time, time to resolution, CSAT, cost per conversation and refund time.
- List your top 20 contact reasons by volume and by cost.
- Read 50 low-rated conversations end to end. Write down every point where the customer had to repeat themselves, wait or chase.
- Map where your data lives: orders, payments, shipping, returns, warranty records. Note which systems your team has to open for a typical request.
Phase 2: Fix the basics (weeks 3 to 6)
- Rewrite your shipping, returns and warranty policies in plain language, using the policy template in this guide.
- Add proactive shipping and delay notifications if they are missing.
- Update the help center for the top 20 contact reasons. One article per question, answer in the first sentence.
- Build or refresh the ten core templates from the script library.
- Consolidate channels into one shared inbox so every conversation has order context.
Phase 3: Automate (weeks 5 to 10)
- Connect your order, payment and CRM systems. In Aftersales that means Shopify, Stripe and Salesforce actions.
- Write procedures for the top five automatable reasons, usually order status, address changes, returns eligibility, refund status and damaged items.
- Set spend guardrails and escalation rules before going live.
- Launch the AI agent on one channel first, often chat, then extend to email, WhatsApp and SMS.
- Review 50 AI conversations a week. Fix wrong answers in the knowledge base, not by patching one reply.
Phase 4: Optimize (weeks 10 to 13 and ongoing)
- Compare every KPI with the Phase 1 baseline.
- Raise AI spend limits where results are good, and add procedures for the next five contact reasons.
- Send the monthly root-cause report to product, operations and marketing.
- Plan for the next peak season using the staffing model.
- Repeat the prevent, deflect, resolve review every quarter.
| Week | Milestone | Owner |
|---|---|---|
| 2 | Baseline report and top 20 reasons | Support lead |
| 4 | New policies published | Support lead with legal and operations |
| 6 | Help center and templates updated, one inbox live | Support team |
| 8 | AI agent live on first channel with five procedures | Support operations |
| 10 | AI agent live on all channels | Support operations |
| 13 | 90-day review against baseline | Support lead and finance |
The median Aftersales customer reaches a 71% resolution rate after 90 days, which is why this plan runs to week 13 before the formal review.
How do you set up aftersales service for a Shopify store?
For a Shopify store, a complete aftersales setup takes a few days: connect the store, write policies and procedures, turn on the channels you use and launch the AI agent with spend limits. Here is a step-by-step walkthrough using Aftersales.
- Create a workspace on the Free plan or start the 14-day trial of a paid plan.
- Connect Shopify so the Agent can verify orders, run order actions and create replacements. Connect Stripe if you issue refunds there, and Salesforce if you keep customer records in it.
- Import or write your knowledge. Add your shipping, returns and warranty policies and your top help articles to Knowledge.
- Write five procedures in plain language: order status, address change or cancellation, return eligibility and label, refund status, and damaged or wrong item.
- Set spend guardrails. For example, replacements up to $50 and refunds up to $75 without approval to start.
- Set escalation rules for negative sentiment, legal language, keywords like "chargeback" and VIP customers.
- Turn on channels: live chat on the store, the support email address, and WhatsApp or SMS if your customers use them. Phone is available on Growth and Scale.
- Test with real past questions. Paste in 30 real customer messages and check each answer and action.
- Go live on chat first, then add email and messaging channels after a week of review.
- Review weekly and raise limits or add procedures as results come in.
See our ecommerce page and the best Shopify customer support apps for more on Shopify setups.
What are common aftersales service mistakes?
- Silence after dispatch. Customers who hear nothing start asking. Send updates at dispatch, out for delivery, delivered and on any delay.
- Policies that live only in agents' heads. Inconsistent answers create repeat contacts and escalations.
- Measuring speed only. A fast first reply that does not solve anything lowers FCR and raises volume.
- Treating returns as a loss only. Returns data tells you about sizing, product quality and listing accuracy.
- Automation without actions. A bot that cannot touch the order just adds a step before the human.
- No loop back to the business. If support sees the same fault 40 times a week and product never hears about it, the fault stays.
Where does aftersales service usually break down?
Most aftersales failures come from a short list of causes. The table pairs each with its symptom and fix.
| Failure point | Symptom | Fix |
|---|---|---|
| No proactive updates | High WISMO volume | Shipping and delay notifications |
| Vague policies | Inconsistent answers, disputes | Plain-language policies with numbers |
| Data in too many systems | Slow replies, errors | One inbox with order context and actions |
| Agents without authority | Transfers and repeat contacts | Clear limits for what each tier can approve |
| Slow refunds | "Where is my refund" contacts, chargebacks | Refund on scan or within a set number of days |
| Chatbot that only links to articles | Frustrated customers, low resolution | AI agent that can take actions within guardrails |
| No route to a person | Angry reviews | Escalation rules and an always-visible human option |
| No feedback loop | Same problems every month | Monthly root-cause report with owners |
What is a quick aftersales service checklist?
Use this as a quarterly review.
- Top 10 contact reasons tagged and reviewed
- Delivery notifications at dispatch, out for delivery, delivered and delay
- Returns policy published, with window, costs and refund timing
- Warranty terms published, with evidence requirements
- Reply macros for the top 10 intents, reviewed for tone and accuracy
- AI agent connected to order, payment and CRM data, with escalation rules
- Resolution rate, FCR, CSAT, return rate and repeat purchase rate on one dashboard
- Monthly report of issues sent to product and operations
For tools that help with each step, see best post-purchase support tools.
What are the key aftersales service terms?
These are the terms used most often in aftersales service, defined briefly.
- Aftersales service: all support provided after the purchase.
- WISMO: "where is my order", order status requests.
- WISMR: "where is my refund", refund status requests.
- RMA: return merchandise authorization, a number that approves a return or repair.
- Contact rate: conversations divided by orders.
- Resolution rate: share of conversations resolved, often used for AI agents.
- FCR: first contact resolution.
- CSAT: customer satisfaction score.
- CES: customer effort score.
- SLA: service level agreement, a committed response or resolution time.
- Shrinkage: paid agent time not spent on conversations.
- Wardrobing: buying, using and returning an item as if unused.
- No fault found: a returned item that works when tested.
- Returnless refund: a refund where the customer keeps the item.
- Spend guardrail: a limit on what an AI agent can refund or replace without approval.
- Escalation rule: a condition that sends a conversation from AI to a person.