How Do You Send Order Notifications to Customers? Training on Stage and Channel Selection, Shipment Tracking Links, Delay Messages and Measuring Support Load
How do you keep customers informed about their orders? Choosing channels and stages, the shipment tracking link, delay messages and measuring support load: an 8-lesson guide with examples.
Contents 14 sections
- What will you be able to do by the end of this training?
- Lesson 1: Why are order notifications needed?
- Lesson 2: At which moments do customers expect information?
- Lesson 3: Which channel should you choose?
- Lesson 4: At which stage and under which condition is a notification sent?
- Lesson 5: How is the shipment tracking link shared with the customer?
- Lesson 6: How do you inform customers about delays and cancellations?
- Lesson 7: How is the drop in support load measured?
- Lesson 8: How is the notification setup managed monthly?
- What are the most common mistakes in keeping customers informed?
- How does NetKasam make keeping customers informed easier?
- Mini quiz: Test what you have learned
- Conclusion: Count this week's customer questions by reason
- Frequently Asked Questions About Keeping Customers Informed About Orders
Three hours after placing an order, the customer writes: "Has my order been received?" The next day: "Has it been shipped?" When the shipment is on its way: "Where is my tracking number?" Each message requires an employee to stop what they are doing, check the panel, write a reply and, more often than not, give the same information again. Most of these questions arise not from the customer's lack of knowledge but from not being informed. Sharing the order status with the customer at the right stage and through the right channel reduces support load and gives the customer confidence.
This article is not a narrative but an 8-lesson practical training. We will answer the question how do you keep customers informed about their orders with numbers, using a sample business that receives 3,600 orders a month: at which moments the customer expects information, channel choice, at which stage and under which condition to send notifications, sharing the tracking link, proactive updates on delays and cancellations, measuring the drop in support load and the monthly routine. At the end there is a mini quiz with an answer key. For setting up shipping, see the article how shipping integration works and how to choose one; here we focus on carrying order information to the customer.
What will you be able to do by the end of this training?
In short: You will identify the moments when customers expect information, choose a channel and condition for each stage, give advance notice of delays and cancellations and measure the change in support load with numbers.
- 01MomentsList the moments when customers expect information.
- 02ChannelChoose the channel for each stage.
- 03ConditionDecide at which stage and under which condition to send.
- 04TrackingShare the shipment tracking link.
- 05ExceptionsGive advance notice of delays and cancellations.
- 06MeasurementTrack the number of questions and time spent.
The training's 8 lessons: (1) why notifications are needed, (2) moments when customers expect information, (3) channel choice, (4) stage and condition, (5) tracking link, (6) delays and cancellations, (7) measuring support load, (8) monthly routine.
Lesson 1: Why are order notifications needed?
In short: After placing an order, the customer experiences uncertainty. If no information arrives, they ask; and asking wastes time for both the customer and the business.
| Without notifications | With notifications |
|---|---|
| The customer writes to ask about the status | The information arrives on its own |
| An employee opens the panel and gives the same answer | The answer has been sent automatically |
| The tracking number is learned late | The tracking link is shared once the shipment leaves |
| When there is a problem, the customer complains before being told | When there is a problem, advance notice is given |
Sample business: an e-commerce seller with its own warehouse that receives 3,600 orders a month from three sales channels. Before notifications are set up, 648 customer questions come in each month. For the entire order flow, see the article how to manage orders in e-commerce.
Lesson 2: At which moments do customers expect information?
In short: There are four moments when customers expect information: when the order is received, when it is prepared, when it is shipped and when it is delivered. Problem moments are just as important.
| Moment | Customer's question | Information to provide |
|---|---|---|
| Order received | "Did my order go through?" | Order confirmation, summary |
| Being prepared | "When will it be shipped?" | Estimated shipping day |
| Handed to carrier | "What is my tracking number?" | Carrier and tracking link |
| Delivered | "Has it reached me?" | Delivery confirmation |
| There is a problem | "Why is it late?" | Reason and new date |
You do not have to send a notification at every stage; too many messages are also annoying. As a start, using the order received, shipped and delivered moments is a sufficient balance for most businesses. For the order picking and packing process, see the article how to do order picking and packing.
Lesson 3: Which channel should you choose?
In short: You can share the tracking link via WhatsApp, SMS or email. Choose the channel based on the customer's habits and the urgency of the information.
| Channel | Strength | Note |
|---|---|---|
| Read quickly, link opens easily | Customer consent and an accurate number | |
| SMS | Works on every phone | Short text, the link takes up space |
| Order summary and invoice can be attached | May be read late |
Instead of sending the same information through three channels at once, choose one channel per stage: order confirmation by email, shipment tracking by WhatsApp or SMS, for example. If the customer has a preference, record it on the order. Keep message texts short, clear and on-brand: "Your order has been shipped. Your tracking link: …" is enough.
When choosing a channel, also consider where the customer placed the order. For orders from marketplaces, communication with the customer often runs through the marketplace's own channels, and tracking information is passed to the sales platform separately; for orders from your own channel, you are the sole owner of the notification. Because of this difference, it is enough to set up more detailed notifications for orders in your own channel and, for marketplace orders, simply make sure the tracking information is passed on correctly.
Lesson 4: At which stage and under which condition is a notification sent?
In short: You decide at which stage and under which conditions notifications are sent. The condition keeps messages from multiplying unnecessarily.
| Stage | Sample condition | Why? |
|---|---|---|
| Order received | Every order | Confirmation is needed for everyone |
| Handed to carrier | If a tracking number has been created | So that no empty link is sent |
| Delay | If the shipping time has been exceeded | So that the customer is told about the problem in advance |
| Delivered | If delivery information has arrived | So that verified information is sent |
When defining conditions, start with a small test group: in the first week, send notifications only for orders coming from one channel, track customer feedback and the number of questions, then widen the scope. In NetKasam, orders and statuses are collected in a single list, and status updates can be made in one go from the bulk actions menu. For details, see the order management page.
Recommended readingHow to Manage Orders in E-Commerce?Lesson 5: How is the shipment tracking link shared with the customer?
In short: You can share the shipment tracking link individually or in bulk via WhatsApp, SMS or email. When the customer opens the link on their phone, they see the shipment's stage step by step.
| Step | How? |
|---|---|
| Orders are transferred to the carrier | Selected orders go to the carrier, a barcode is created |
| Tracking information is passed to the sales platform | No separate manual entry |
| The tracking link goes to the customer | Shared in bulk or individually |
| The customer tracks it | Sees it step by step on the tracking screen |
Shipments outside the panel can also be included in the same flow: shipments you bring into the system via Excel or manual entry appear in the same tracking flow. If you work with different carriers by region, see the article how to create a region-based shipping rule for setting up rules. For checking shipping charges, the article how to check a shipping invoice is a useful complement. For details, see the shipping integration page.
Lesson 6: How do you inform customers about delays and cancellations?
In short: Even bad news preserves trust if you deliver it to the customer first. For a delay, state the reason and new date; for a cancellation, state the options.
| Situation | What should the message include? | After that |
|---|---|---|
| Shipping delay | Reason, new estimated shipping day, apology | The new date must be kept |
| Out of stock / partial cancellation | Which product, what will be done | A partial cancellation is made; see order cancellation |
| Delay in transit | Status at the carrier, tracking link | Follow-up with the carrier |
| Return confirmation | That the return has been received, the refund process | Return invoice; see return invoice |
In NetKasam, you can change the order status and, if necessary, cancel the order or make a partial cancellation; workflows are created automatically when the status changes. Prepare the message content separately for bad news: the trio of apology, reason and solution removes the uncertainty that drives the customer to ask. For the cost of the return process, see the article how to calculate return costs.
When writing a delay message, keep the new estimated date realistic. Telling the customer "it ships tomorrow" and then being late again two days later causes a bigger loss of trust than the first delay. For a date you are not sure about, give a range ("within 2–3 business days") and send the tracking link immediately once the shipment goes out. These two steps largely prevent the delay from turning into a complaint and keep the support team from having to message the same customer a second time.
Lesson 7: How is the drop in support load measured?
In short: The value of notifications is measured by the number of customer questions and the time spent on them. Compare the month before setup with the months after.
- Question rate = Customer questions ÷ Number of orders × 100
- Support time = Number of questions × Time per question
- Time saved = Previous support time − Subsequent support time
- Reduction rate = (Before − After) ÷ Before × 100
Prepared with sample values.
- Where is my package?₺38960%
- Address or information change₺9715%
- Cancellation request₺7812%
- Invoice request₺528%
- Other₺324.9%
Prepared with sample values. Share of shipping questions is 60% (389 ÷ 648).
- Questions before notifications648 questions
- Fewer "where is my package?" questions (389 → 130)−259 questions
- Fewer other questions (259 → 86)−173 questions
- Questions after notifications216 questions
Prepared with sample values. The question rate drops from 18% to 6%.
| Indicator | Before | After |
|---|---|---|
| Monthly orders | 3.600 | 3.600 |
| Customer questions | 648 | 216 |
| Question rate | %18 | %6 |
| Support time (4 min/question) | 2,592 min (43.2 hours) | 864 min (14.4 hours) |
Time saved is 43.2 − 14.4 = 28.8 hours, and the reduction rate is 66.7%. That is about 3.6 working days. The figure may not look large, but the same employee can devote that time to preparing orders or selling. The real gain is that the uncertainty the customer experiences while waiting disappears. To add the number of questions to your weekly report, see the article how to prepare a weekly management report.
- Before setup18%
- First month9%
- Third month6%
Prepared with sample values. Question rate = number of questions ÷ number of orders.
Lesson 8: How is the notification setup managed monthly?
In short: Review message texts and conditions once a month. Whatever questions still come in point to a gap in your notifications.
| When? | What to do? | Who? |
|---|---|---|
| Weekly | Incoming customer questions are counted by reason | Support |
| Monthly | Question rate and support time are calculated | Management |
| When there is a delay | A message is sent in advance to the affected orders | Operations |
| Before a campaign | Message texts and frequency are checked | Operations |
| Once a quarter | Channel and stage choices are reviewed | Management |
During campaign periods, order volume increases and the likelihood of delays rises; writing the estimated shipping time in message texts during these periods immediately reduces the question load. For sales forecasting, see the article how to forecast sales, and for a bulk invoicing routine, how to invoice orders in bulk.
- 18% → 6%question rate (648 → 216)
- 60%share of "where is my package?" before notifications
- 28.8 hourssupport time saved per month
- 66.7%reduction in the number of questions
A side benefit of the notification setup is data. Counting incoming questions by reason shows which link in the process is weak: if there are many address change questions, address validation is missing on the order page; if there are many invoice requests, invoices are not going to the customer automatically; if there are many cancellation requests, the shipping time is not meeting expectations. This way, support volume not only drops, but the reason it drops is also known.
What are the most common mistakes in keeping customers informed?
- Sending a message at every stage. The customer is overwhelmed and messages lose their importance.
- Sending a link before the tracking number is created. An empty link undermines trust.
- Not mentioning a delay until the customer asks. Complaints and cancellations increase.
- Sending the same information through three channels. It creates unnecessary repetition.
- Keeping the message text long. The link gets overlooked.
- Not measuring the result. You never know whether notifications are working.
- Leaving shipments outside the panel out of the flow. Those customers still ask questions.
How does NetKasam make keeping customers informed easier?
- Status sharing. You automatically share order statuses with your customer at any stage you choose (order management).
- Tracking link. Shared individually or in bulk via WhatsApp, SMS or email; you decide at which stage and under which conditions notifications are sent (shipping integration).
- Customer tracking screen. The customer follows their shipment step by step; there is no need to ask your support team.
- Notification to the sales platform. Tracking information is also passed to the sales platform; you do not need to enter it separately.
- Excel and manual shipments. Shipments outside the panel are included in the same tracking flow.
- Cancellation and partial cancellation. The order status is changed and, if necessary, the order is canceled.
- Bookkeeping is free. e-Invoice, customer and supplier accounts, inventory, cash, bank and expense management are free in every plan; see the pricing page for details.
Mini quiz: Test what you have learned
In short: Answer the 5 questions below, then compare with the answer key. 4 or 5 correct shows you have completed the training.
- 300 customer questions came in for 2,000 orders. What is the question rate?
- If each question takes 5 min, how many hours is the support time?
- After notifications, the number of questions dropped to 120. What is the reduction rate?
- How many hours are saved?
- Why should a link not be sent before the tracking number is created?
Answer key:
- 300 ÷ 2.000 × 100 = %15.
- 300 × 5 = 1,500 min = 25 hours.
- (300 − 120) ÷ 300 × 100 = %60.
- 120 × 5 = 600 min = 10 hours; 25 − 10 = 15 hours.
- The customer encounters an empty or broken link, trust is undermined and they ask again.
Frequently Asked Questions About Keeping Customers Informed About Orders
Can I share order statuses with my customers?
Yes. In NetKasam, you can automatically share order statuses with your customers at any stage you choose.
Through which channels is the shipment tracking link sent?
You can send it individually or in bulk via WhatsApp, SMS or email.
Do I decide at which stage the notification is sent?
Yes. You decide at which stage and under which conditions notifications are sent.
Can customers track their shipment themselves?
Yes. Your customers see their shipments step by step on the tracking screen.
Are shipments I send outside the panel also tracked?
Yes. You can bring your shipments into the system via Excel or manual entry and include them in the same tracking flow.
Do I need to enter tracking information on the sales platform separately?
No. Once shipped orders are transferred to the carrier, the information is passed to the sales platform.
How is the question rate calculated?
The number of customer questions is divided by the number of orders and multiplied by 100. In the example, 648 ÷ 3,600 = 18%.
What should be done when there is a delay?
The reason and a new estimated date should be communicated before the customer asks; if necessary, the order status is changed or a partial cancellation is made.
Conclusion: Count this week's customer questions by reason
Before setting up notifications, you need to know what you are going to solve. Count all customer questions that come in this week by reason: where is my package, address change, cancellation, invoice. Set up a single notification aimed at the question with the largest share and recalculate the question rate a month later. When customers get information without asking, satisfaction rises and the team finds time for its real work during the day. Starting small and expanding as you measure makes this setup sustainable.
Bookkeeping Is Now Completely Free
Manage your bookkeeping and e-Invoice operations with NetKasam without paying a thing. Customer and supplier accounts, inventory, collections and more in one panel, completely free.