A subscriber receives her box around the middle of the month. She has decided it arrives on the fourteenth, because it did twice.
This month it dispatches on the sixteenth as part of a normal batch. By the fifteenth she has messaged support, by the seventeenth she has messaged again, and the box arrives on time by every definition except hers.
1. Publish the cycle dates
Billing date, dispatch window and expected delivery range, in the account and on the website. Customers with the real dates stop inventing their own.
2. Explain the batch dispatch reality
That orders ship across several days, and that receiving later than a friend is normal rather than an error. One sentence prevents a recurring complaint.
3. Narrow the window as far as you honestly can
A three day window generates fewer questions than a two week one. Where operations allow it, tightening this is the highest value change available.
4. Send a dispatch notification with tracking
Immediately, with a link that works. The absence of this is the single largest driver of contacts in subscription businesses.
5. Send a pre dispatch message too
A note saying boxes ship this week sets expectation before anybody starts wondering, which is considerably cheaper than answering afterwards.
6. Show the next delivery date in the account
Permanently visible, updated automatically. Customers check the account first and contact support when it tells them nothing.
7. Separate the billing date from the dispatch date
Customers see a charge and expect a parcel. Explaining the gap removes a predictable wave of messages every cycle.
8. Say what happens with a first order
First boxes frequently follow a different schedule, and new subscribers are the most anxious and the least informed.
9. Handle the address and holiday cases
Somebody away during a dispatch window needs a pause or a redirect, which links to the mechanics in subscription and repeat order questions.
10. Explain what happens when something is out of stock
A substitution, a delay or a partial box. Silence here turns a minor issue into a cancellation.
10b. Say what a failed payment does to the schedule
A card that declines on the billing date quietly removes somebody from that cycle's batch, and they find out when no box arrives. Telling subscribers immediately, and saying how long they have to fix it before the dispatch window closes, prevents the message that begins by asking where the box is.
10c. Explain the address change deadline
Addresses edited after a batch has been picked will not reach the labels, and a box goes to a house somebody has moved out of. A stated cut off, shown next to the address field itself, is more effective than any note in a help page.
11. Be honest about seasonal peaks
December schedules shift and customers need telling in November rather than discovering it.
12. Handle gift subscriptions carefully
The buyer needs the date more than the recipient does, which is the complication in gifting and recipient questions on subscription sites.
13. Recognise the repetition
The same question arrives every cycle from a different group of subscribers, which is the pattern in delivery window questions subscription customers repeat.
14. Automate the answer
An assistant that gives the dispatch date, the tracking link and the next cycle date answers the highest volume question without a person, and the standard responses can be drafted with a reply generator. The wider handling is set out in ai assistant subscription business.
15. What precision produces
An inbox with genuine problems in it rather than the same question forty times. See features, start at try, and the sector view sits under ecommerce.