Not all WISMO can be prevented. Storms happen. Carriers experience bottlenecks. Addresses get entered incorrectly. Supply chain disruptions occur. What separates brands with low WISMO rates from those drowning in tickets is how they handle exceptions before customers need to ask.
Implement automatic exception alerts from your carriers or shipping platforms. When a package experiences a delay, failed delivery attempt, or misroute, your team should know before the customer does. This advance warning gives you time to act proactively rather than reactively.
Set internal SLAs for reacting to exceptions during holiday season. For example: contact affected customers within 12-24 hours of an exception with an updated ETA or resolution path. Speed matters here—the longer a customer waits without hearing from you, the more likely they are to contact support or leave negative feedback.
Create standard operating procedures (SOPs) for common exception types:
- Damaged parcels: How to process claims and arrange replacement
- Lost in transit: When to declare lost (X days past delivery date), how to investigate, when to reship
- Customs holds: What documentation is needed, expected delay timeline
- Incorrect addresses: Process for address correction or return to sender
- “Delivered” but not received: Investigation steps, waiting period before resolution
Ensure support agents, operations teams, and warehouse staff share the same single source of truth for order status. Integrate your shipping platform, CRM, and helpdesk systems so everyone sees consistent, real-time data. When a customer calls and an agent sees different information than operations, trust erodes quickly.
Reduce internal WISMO by giving internal stakeholders self-service access. Sales teams asking about VIP orders, account managers checking on B2B shipments, and retail partners inquiring about their inventory—all of these create internal support burden. Dashboards and live order views help these users find answers without escalating.
Review WISMO tickets weekly during peak season to identify patterns:
- Is one carrier lane consistently delayed?
- Are apartment buildings in a particular city generating failed deliveries?
- Is a specific shipping method underperforming expectations?
These insights let you quickly adjust shipping methods, update delivery promises, or proactively communicate known issues.
When reaching out about exceptions, use empathetic and transparent language. Here’s an effective example:
“Hi [Name], we wanted to let you know your order is running behind schedule due to carrier delays affecting shipments in your region. Your updated expected delivery date is December 23. We’re sorry for the inconvenience and appreciate your patience. If you have questions, reply to this email and we’ll help immediately.”This message acknowledges the delay, provides specifics, and offers a clear next step—all before the customer needed to ask.