---
title: "Ecommerce Customer Support During Festive Sales: How Indian Brands Handle the Call Surge"
url: "https://www.elisiontec.com/ecommerce-customer-support-during-festive-sales/"
date: "2026-11-07T16:42:08+05:30"
modified: "2026-11-07T16:42:10+05:30"
author:
name: "Bhagyashree"
categories:
- "eCommerce Support Center Solution"
tags:
- "contact center solution"
- "Customer Experience"
word_count: 4394
reading_time: "22 min read"
summary: "A festive sale call surge is the short, steep rise in calls, chats and WhatsApp messages an ecommerce brand gets around big sale events, driven first by orders and payments, then by delivery delays..."
description: "Ecommerce customer support during festive sales: how Indian brands handle call surges with IVR, AI bots, priority queues and a plan for the refund wave."
keywords: "ecommerce customer support,festive sale call surge,Diwali contact center surge ecommerce India,ecommerce call center software India, contact center solution, Customer Experience"
language: "en"
schema_type: "Article"
---
# Ecommerce Customer Support During Festive Sales: How Indian Brands Handle the Call Surge
_Published: November 7, 2026_
_Author: Bhagyashree_
**A festive sale call surge is the short, steep rise in calls, chats and WhatsApp messages an ecommerce brand gets around big sale events, driven first by orders and payments, then by delivery delays, then by returns and refunds.**
Elision Technologies · Last reviewed 7 November 2026 · About 12 min read
For most Indian brands, ecommerce customer support has its hardest month between the start of the festive sales and the last refund of the season. Diwali falls on Sunday, 8 November 2026, with Dhanteras on 6 November, and the big platform sales ran for weeks before it. The order and payment calls are mostly behind you now. The delivery, return and refund calls are just starting, and they come with legal clocks attached. This guide covers both: how brands absorb the sale-day spike, and how they get through the slower, longer wave that follows, with the rules, staffing maths and checklists to plan the next sale.
Key takeaways
- A festive surge changes the mix of calls as much as the number. Payment and order questions dominate sale days; delivery, return and refund calls dominate the weeks after.
- The post-sale wave runs on legal deadlines: complaints must be acknowledged within 48 hours and resolved within a month under India’s E-Commerce Rules, and failed payments have RBI reversal timelines.
- From 1 January 2027, amended E-Commerce Rules require brands to give complainants a copy of their recorded complaint and to join the National Consumer Helpline convergence process.
- AI does two jobs in a surge: voice bots and chatbots answer the repeat questions in Hindi and regional languages, and AI voice analysis checks every call from seasonal agents, which no QA team can do by hand at peak.
- In our worked example, every 10% of calls deflected to IVR, bots or proactive messages removes about 28 rostered agents from a tenfold peak.
- Offer calls and order-update calls follow different TRAI rules. Keep promotions on registered 140-series numbers and out of service calls.
In this guide
1. [What is a festive call surge?](#what-is-surge)
2. [Why it is different](#why-different)
3. [Rules that set the clock](#rules)
4. [Five levers that work](#levers)
5. [Where AI helps](#ai)
6. [How many agents you need](#agents)
7. [Six weeks out to the refund wave](#timeline)
8. [The next four weeks](#next-four-weeks)
9. [Mistakes to avoid](#mistakes)
10. [Questions for vendors](#vendor-questions)
11. [FAQs](#faqs)
## What is a festive sale call surge?
It is a spike in customer contacts that is both larger and shorter than any other peak in the year, followed by a smaller but longer tail. Sale launches often open at midnight, so the first hours can bring more callers than a team normally sees in a day. Averaged over the whole season the rise is far smaller than in the launch hours, so plan for both: a season-long base case and a short stress case. This guide uses ten times normal volume as the stress case for the opening hours of the biggest sales. It is a planning assumption, not a measured industry figure, so replace it with your own last-season interval data wherever you have it.
## Why is a festive surge different from a normal busy day?
A normal peak is the same work arriving faster. A festive surge is different work arriving all at once, from customers with a deadline of their own.
- **The window is short.** The heaviest load can sit inside three days, which is too short to hire and train your way through it.
- **The reasons for calling shift.** General product questions fall away. “Where is my order?”, failed payments, coupon disputes and address changes take over.
- **Patience is lower.** A gift that misses Dhanteras or Bhai Dooj is not a routine delay to the customer, and the tone of the call reflects that.
- **The peak moves.** Sale days bring pre-purchase and payment calls. A week later it is delivery. Two to four weeks later it is returns and refunds.
- **Your partners are stretched too.** Couriers, payment gateways and warehouses hit their own limits at the same time, and every slip on their side becomes a call on yours.
| Phase | What customers call about | Best way to handle it | Clock that applies |
|---|---|---|---|
| Before the sale | Offer terms, coupon rules, stock, delivery estimates | IVR options, WhatsApp, knowledge-base answers | None regulatory; lost sales if unanswered |
| Sale days | Payment failures, order confirmation, address changes | Priority routing, callbacks, agents who see order and payment data | RBI reversal timelines for failed payments |
| Week after | Order status, delays, non-delivery | Proactive delay messages, complaints routed to the dispatch team | 48-hour acknowledgement once it becomes a complaint |
| Two to four weeks after | Returns, refunds, exchanges, damaged items | Refund status self-service, a dedicated returns queue, refunds routed to accounts | Complaint resolved within one month of receipt |
## Which rules set the clock for ecommerce customer support in India?
Four sets of rules decide how fast a festive complaint has to be handled and how you may contact customers about it. Most surge plans cover staffing well and these rules badly, which is why the refund wave produces escalations long after the sale-day queues have cleared.
| Rule | What it requires | What it means for your contact center |
|---|---|---|
| Consumer Protection (E-Commerce) Rules, 2020 (Department of Consumer Affairs) | A grievance officer must acknowledge each consumer complaint within 48 hours and redress it within one month of receipt. | Every festive complaint needs a ticket, a timestamp and an owner on day one. A queue that only tracks wait time cannot show you which tickets are about to breach. |
| Consumer Protection (E-Commerce) (Amendment) Rules, 2026, in force from 1 January 2027 | Complainants must receive a copy of the complaint as the grievance officer recorded it; every e-commerce entity must join the National Consumer Helpline convergence process. | Plan an automatic SMS, WhatsApp or email with the recorded complaint, and a separate intake path for complaints arriving through the National Consumer Helpline before the January sales. |
| RBI circular on turnaround time for failed transactions (20 September 2019) | When a customer is debited but the merchant gets no confirmation, UPI and card payments must be auto-reversed within T+5 days, with ₹100 per day of delay payable after that. | Agents should tell callers the date by which the reversal is due rather than “5 to 7 working days”. The IVR can say it too. |
| TRAI Telecom Commercial Communications Customer Preference Regulations, 2018 (amended February 2025) | Promotional calls must come from registered 140-series numbers and do not reach customers who blocked that category on DND. Commercial SMS must use registered headers and templates. | Keep coupon and offer broadcasts separate from delivery and refund updates, and never add an upsell to a service call. |
Call recordings and order data also fall under the Digital Personal Data Protection Act, 2023, whose rules phase in obligations through May 2027. Masking shopper numbers when agents or delivery partners call them reduces how much personal data moves around during the peak.
This section summarises published rules for operational planning and is not legal advice. Check how they apply to your business model (marketplace, inventory or seller) with your legal or compliance team.
## How do ecommerce companies handle the festive season call surge?
The brands with the strongest ecommerce customer support during sales do not try to answer every call with a person. They combine five levers: elastic capacity, IVR deflection, bots for repetitive questions, priority routing for post-sale cases, and proactive messages that stop calls before they start.
### 1. Elastic capacity: add seats for the sale, release them after
A fixed setup is sized for an ordinary Tuesday. A festive sale needs something closer to a rubber band. Cloud telephony lets you add agent seats and call capacity for the sale window and scale back afterwards, so you are not paying for Diwali-level capacity in February. Brands with a large, steady team on their own infrastructure often keep that core on-premise and add cloud seats only for the peak. Seasonal agents, whether in-house, from a partner BPO or working from home, should log into the same platform, with the same routing and the same reports, from their first shift.
How DialShree handles it
DialShree’s eCommerce solution is built for on-demand scalability, so call capacity and agent seats can grow with a campaign and shrink after it. Seasonal and remote agents can work from a browser or the DialShree Mobi app, and the platform runs in the cloud or on-premise.
### 2. IVR deflection: answer the easy calls without an agent
A large share of festive calls are one of a handful of questions. If the IVR can read the order status from your order system and answer “where is my order?”, the customer is done in under a minute and no agent picks up. A multi-level IVR also sorts what remains, so a payment problem goes to the payments desk and a delivery complaint never waits in the general queue. When wait times climb, an automated callback that keeps the caller’s place beats hold music.
How DialShree handles it
DialShree includes a multi-level IVR available 24×7 and an automated callback feature. Its CRM integration puts order and customer details on the agent’s screen when a call does reach a person.
### 3. AI voice bots and chatbots for the repeat questions
AI bots do well on narrow, repeated questions: order status, return pickup slots, refund status, coupon rules. They do badly when a customer is angry or the case has three moving parts. Let the bot take the first group and hand the second to an agent along with the conversation so far. On WhatsApp, a chatbot can answer in seconds without adding a call to the queue; on the phone, a voice bot that understands Hindi, Hinglish and regional languages takes the same load off your agents. The next section covers where AI fits and where it should stop.
How DialShree handles it
DialShree brings calls, SMS, email, social media and WhatsApp into one omnichannel platform, and its knowledge-based integration suggests answers to agents based on the shopper’s query. For AI voice bots, Elision’s [Voice API and VoiceLink](https://www.elisiontec.com/products/voicebot-indian-number-solution/) provide the Indian telephony layer, so your bot can answer and place calls on Indian numbers.
### 4. Post-sale queue priority: serve the right customers and cases first
When you cannot answer everyone at once, order matters. Many brands put loyal and high-value shoppers first, then urgent post-sale cases such as non-delivery of a gift or a failed payment, while routine questions wait or go to self-service. Complaints should go straight to the team that can fix them instead of passing from agent to agent.
| Priority | Who or what | Handling |
|---|---|---|
| 1 | Loyal or high-value shoppers; gift orders at risk of missing the festival date | Skip the general IVR; first available agent |
| 2 | Payment debited, order not confirmed | Payments desk; quote the reversal due date; callback if the queue is full |
| 3 | Non-delivery and damaged-item complaints | Ticket opened at once; routed to dispatch or the resolution team |
| 4 | Returns and refund status | Self-service first; refund cases routed to accounts |
| 5 | General questions | IVR, WhatsApp, knowledge base |
How DialShree handles it
DialShree’s smart routing can send elite and loyal shoppers to an agent ahead of the general queue, divert non-delivery complaints to the dispatch department and route refund cases to accounts. Elision reports that for Nykaa, routing prime members past the general IVR and balancing calls across four locations helped cut the dropped-calls ratio by 71%.
### 5. Proactive messages: prevent the call before it happens
The cheapest call is the one that never comes. If a courier has flagged a delay, tell the customer before they ask, and include the new date. Order confirmations, delay notices and refund updates sent by SMS, WhatsApp or voice each remove calls from your queue. Offers and coupon reminders can use the same tools, but they are promotional under TRAI rules: send them only from registered 140-series numbers and approved templates, and keep them out of service messages.
How DialShree handles it
DialShree supports voice broadcasting, SMS and cross-channel messaging from one platform, for order follow-ups as well as offers. [Number masking](https://www.elisiontec.com/services/number-masking/), including temporary numbers for outbound calls, keeps shopper phone numbers private when support or delivery teams call them.
## Where does AI help in a festive surge, and where should a person take over?
AI helps most in two places during a festive sale: answering the high-volume repeat questions before they reach an agent, and checking the quality of every call once they do. It helps least with upset customers, disputed payments and damaged high-value orders, where a person should take over quickly.
| Task | What AI does | Hand over to a person when |
|---|---|---|
| “Where is my order?” and refund status | A voice bot or chatbot reads the order or refund record and answers in the caller’s language | The order is late for a festival date or the refund is past its due date |
| Return pickup and exchange requests | Books the pickup slot and confirms it by SMS or WhatsApp | The item is damaged, high-value or the customer disputes the return policy |
| Agent assistance | Suggests knowledge-base answers while the agent is on the call | The answer is not in the knowledge base; the agent escalates |
| Quality checks on seasonal agents | Transcribes and scores every call, flags frustration, long silences and missed script steps | A flagged call needs coaching or a callback to the customer |
| Compliance checks | Spots keywords such as an offer pitched inside a service call, or a refund quoted without a date | A pattern repeats across agents; fix the script or the training |
**Why AI quality checks matter more in a sale than at any other time.** A supervisor who normally reviews a small sample of calls cannot keep up when headcount doubles with agents in their first week. Scoring every call automatically shows by the end of day one which new agents are quoting the wrong return window, going silent on payment questions or leaving customers angrier than they called. That gives you time to coach them while the sale is still running, not in the post-season review.
How AI Voice Analysis handles it
Elision’s [AI Voice Analysis](https://www.elisiontec.com/products/ai-voice-analysis/) transcribes 100% of calls, tracks customer sentiment and emotion through each call, detects silence and over-talking, scores every call against your quality standards and ranks agents on a scoreboard. It works in Hindi, Hinglish, English, Gujarati, Tamil, Telugu and Marathi. Elision reports that it frees QA teams from 90% of manual review work.
**Three guardrails for AI in a sale.** Always offer a one-step route from the bot to a person. Tell callers when they are speaking to an automated assistant. And keep outbound bot calls under the same TRAI rules as human ones: offers from 140-series numbers, service updates kept free of promotions.
## How many agents does a festive surge need?
Staffing ecommerce customer support for a sale starts from four numbers: forecast calls per hour, average handle time (AHT), target occupancy and shrinkage. Here is a worked example. A normal peak hour has 200 calls, AHT is 5 minutes, occupancy is capped at 85% and shrinkage is 30%. During the sale, volume rises tenfold to 2,000 calls an hour.
| Scenario | Calls per hour | Workload (agent-hours per hour) | Erlang C minimum for 80% in 20 seconds | Agents on the phones (85% occupancy cap) | Agents to roster (30% shrinkage) |
|---|---|---|---|---|---|
| Normal peak hour | 200 | 16.7 | 21 | 21 | about 30 |
| Surge, no deflection | 2,000 | 166.7 | 176 | 197 | about 280 |
| Surge, 40% deflected to IVR, AI bots and messages | 1,200 reach agents | 100 | 108 | 118 | about 168 |
Workload is calls × 5 minutes ÷ 60. The Erlang C column is the smallest team that answers 80% of calls within 20 seconds. At surge volumes that number is low because large queues are efficient, but it would keep agents at about 95% occupancy for three days, which leads to burnout and mistakes. Capping occupancy at 85% gives the “on the phones” column; dividing by 0.70 for breaks, training and absence gives the roster. The figures are illustrative, but the lesson holds: in this example every 10% of calls you deflect removes roughly 28 rostered agents. For more on shrinkage, see our guide to [BPO workforce management](https://www.elisiontec.com/bpo-workforce-management-india/).
## What does a festive support plan look like, from six weeks out to the refund wave?
A workable plan has six phases. The first three happen before the sale; the last two are where most teams under-plan.
| Phase | What to do |
|---|---|
| **6 weeks out: forecast** | Pull last season’s interval data by day and query type. Model a base, expected and extreme case. Decide how much to deflect and how many seats to add. Book seasonal agents and partner BPO capacity. Confirm channel and number capacity with your telephony provider. |
| **4 weeks out: build** | Design surge IVR menus and order-status flows. Write bot and knowledge-base answers for the top 20 questions, including the payment reversal timeline. Set queue priorities and routing rules. Register SMS and WhatsApp templates for delays and refunds; keep offer templates separate. |
| **2 weeks out: test and train** | Load-test calls and agent logins at peak numbers. Train seasonal agents on offer terms, the returns policy and escalation. Run mock peak hours with supervisors. Freeze major configuration changes. |
| **Sale days: run and adjust** | Staff a command desk: one person per queue, one watching IVR drop-offs, one in touch with logistics and payments. Compare plan with actual every 15 to 30 minutes. Switch on callbacks when waits cross your threshold. Send delay notices early. |
| **Week after: delivery issues** | Share courier status with agents and the IVR daily. Open a ticket for every non-delivery complaint and start the 48-hour acknowledgement clock. |
| **Weeks 2 to 4: returns and refunds** | Keep a dedicated returns queue. Report daily on tickets close to the one-month limit. Release seasonal seats only when refund volume is back to normal. |
**Starting late?** If the sale is days away, skip the big rebuild and do three things: add an order-status option and a callback to the IVR, prepare delay and refund message templates, and set one priority rule for gift orders and payment failures.
## Diwali sales are over. What should support teams do in the next four weeks?
Hold on to ecommerce customer support capacity, because the refund wave is still ahead. Delivery and refund questions usually peak a week or two after the sale and can keep coming for most of a month, and that is the stretch where the grievance clock is running.
1. **Count open complaints by age.** List every ticket by days since receipt. Anything near 48 hours without acknowledgement, or near a month without resolution, goes to the top.
2. **Answer refund status without an agent.** Add refund status to the IVR and WhatsApp, with the date it is due, not a range of working days.
3. **Tell delayed customers first.** Send proactive updates for every shipment your couriers have flagged, before the customer calls.
4. **Release seasonal seats in steps.** Cut seats as daily refund and return volume falls, not on a fixed date.
5. **Capture the data for next time.** Save interval volumes, call reasons, AHT and deflection rates by day. This is next season’s forecast, and the January sales are close.
## Which mistakes hurt most during a sale?
Most ecommerce customer support failures in a festive sale trace back to a few planning gaps.
- **Planning for sale day only.** The refund and delivery wave arrives later, lasts longer and carries the legal deadlines.
- **Hiding the callback option.** Customers who cannot get through call again, which doubles the load.
- **Deflecting without an exit.** An IVR or bot with no route to a person creates angrier callers and more complaints.
- **Quoting vague refund dates.** “It will reflect soon” brings a second call. A specific due date usually does not.
- **Testing at normal load.** A system that works at 100 agents may behave differently at 400.
- **Training seasonal agents too late.** A week-one agent with a six-page returns policy is a risk.
- **Mixing offers into service calls.** An upsell inside a delivery update turns a service call into a promotional one under TRAI rules.
## What should you ask a contact center vendor before the next sale?
1. How quickly can I add 100 or 200 agent seats, and who does the work?
2. What peak concurrent call volume have you handled for an ecommerce client?
3. Can the IVR read order and refund status from my order system?
4. Can I set queue priority by shopper tier and by query type?
5. How do bots hand over to a human, and does the agent see the conversation?
6. Can every complaint get a ticket, a timestamp and an automatic copy sent to the customer?
7. Can I send service updates and promotional messages from the right number series and templates, from one platform?
8. Can I mask shopper numbers when agents or delivery partners call them?
9. Can AI transcribe and score every call, in Hindi and regional languages, from the first day of the sale?
## Why Elision for ecommerce customer support?
- **A solution designed around shoppers.** Our [ecommerce call center solution](https://www.elisiontec.com/solutions/ecommerce-communication/) combines a multi-level IVR, smart routing for elite shoppers, broadcasting, on-demand scalability and cross-channel integration.
- **A published ecommerce result.** [Nykaa reduced its dropped-calls ratio by 71%](https://www.elisiontec.com/success-stories/nykaa/) with a customised DialShree setup that included smart routing, load balancing across locations and number masking.
- **AI where it pays off.** [AI Voice Analysis](https://www.elisiontec.com/products/ai-voice-analysis/) checks every call in seven language options, and VoiceLink connects AI voice bots to Indian numbers.
- **Privacy by default.** Number masking hides shopper phone numbers from agents and delivery teams.
- **Deployment that fits.** DialShree runs in the cloud or on-premise and connects to your CRM and order systems through APIs.
Plan your next sale with real numbers
Send us last season’s peak-hour volumes and your top five call reasons. We will show you how DialShree would route, deflect and staff them, including AI voice bots for order status, AI quality checks on every call and a returns queue that tracks the complaint clock.
[See DialShree for ecommerce](https://www.elisiontec.com/solutions/ecommerce-communication/)
[Or book a 30-minute walkthrough](https://www.elisiontec.com/contact/)
## Glossary
Surge
A sudden, steep rise in contact volume over a short period.
Deflection
Resolving a query through self-service, IVR, a bot or a proactive message, so it never reaches an agent.
Elastic capacity
Adding and removing agent seats and call capacity as demand changes.
Callback
A feature that keeps a caller’s place in the queue and calls them back instead of holding.
AHT
Average handle time: talk time plus hold and after-call work.
Shrinkage
The share of paid agent time not available for calls, such as breaks, training and absence.
Erlang C
A queueing formula that estimates how many agents are needed to answer a given share of calls within a target time.
AI voice analysis
Software that transcribes calls and uses AI to score them, detect customer sentiment and flag compliance or quality issues.
Grievance officer
The person an e-commerce entity must appoint under the E-Commerce Rules to acknowledge and resolve consumer complaints.
## FAQs
### How do ecommerce companies handle festival season call surge?
They plan capacity weeks ahead, deflect routine questions to IVR, bots and WhatsApp, add agent seats on demand, prioritise high-value shoppers and urgent post-sale cases, send proactive updates, and keep capacity for the returns and refund wave that follows the sale.
### How fast must an ecommerce company respond to a customer complaint in India?
Under the Consumer Protection (E-Commerce) Rules, 2020, the grievance officer must acknowledge a consumer complaint within 48 hours and redress it within one month of receipt.
### What changes for ecommerce customer support on 1 January 2027?
The E-Commerce (Amendment) Rules, 2026 come into force. Brands must give complainants a copy of the complaint as recorded by the grievance officer and join the National Consumer Helpline convergence process, among other changes.
### How long does a refund take when a payment fails but no order is confirmed?
RBI’s 2019 turnaround-time circular requires auto-reversal within T+5 days for UPI and card payments where the merchant did not receive confirmation, with ₹100 per day payable for further delay. Your agents and IVR should quote that due date.
### Can we send offer and coupon calls during a festive sale?
Yes, but they are promotional calls under TRAI rules. They must come from registered 140-series numbers and will not reach customers who have blocked that category on DND. Keep them separate from delivery and refund updates.
### How many extra agents do we need for a sale?
Start from forecast calls, handle time, occupancy and shrinkage. In this guide’s example, a tenfold surge needs about 280 rostered agents instead of about 30, and about 168 if 40% of calls are deflected.
### Does the surge end when the sale ends?
No. Delivery and refund queries often peak a week or two later and continue for most of a month, so keep a dedicated returns queue and release seasonal seats gradually.
### Can AI handle festive customer support queries?
AI voice bots and chatbots handle narrow, repeated questions well, such as order status, return pickups, refund status and coupon rules, including in Hindi and regional languages. Upset customers, payment disputes and damaged high-value orders should go to a person, with the conversation passed along.
### How can we check call quality when seasonal agents join for a sale?
Use AI voice analysis to transcribe and score every call automatically. It flags frustrated customers, long silences and missed script steps by agent, so supervisors can coach new agents within the first day instead of sampling a few calls by hand.
### When should we start preparing for the next festive sale?
About six weeks before it. That leaves time to forecast, book seasonal agents, build IVR and bot flows, register message templates and test at peak volume.
**About this guide.** Prepared by Elision Technologies for ecommerce support and operations heads. Last reviewed 7 November 2026. We will revise it before the amended E-Commerce Rules take effect on 1 January 2027 and whenever TRAI or RBI changes the rules cited here. Festival dates follow widely published panchang calendars and can vary by region.
## Sources and regulatory references
- Department of Consumer Affairs, Consumer Protection (E-Commerce) Rules, 2020, G.S.R. 462(E), 23 July 2020: [consumeraffairs.nic.in](https://consumeraffairs.nic.in/acts-rules/consumer-protection-e-commerce-rules-2020)
- Press Information Bureau, amendment of the E-Commerce Rules through the Consumer Protection (E-Commerce) (Amendment) Rules, 2026, September 2026: [pib.gov.in](https://www.pib.gov.in/PressReleaseDetail.aspx?PRID=2308759)
- Reserve Bank of India, Harmonisation of Turn Around Time (TAT) and customer compensation for failed transactions using authorised Payment Systems, DPSS.CO.PD No.629/02.01.014/2019-20, 20 September 2019: [rbi.org.in](https://www.rbi.org.in/scripts/NotificationUser.aspx?Id=11693&Mode=0)
- TRAI, Telecom Commercial Communications Customer Preference Regulations, 2018, and Second Amendment Regulations, 12 February 2025: [trai.gov.in](https://www.trai.gov.in/). Our explainer: [140 and 160 series regulations](https://www.elisiontec.com/140-and-160-series-regulations-from-trai-complete-guide-faqs/)
- National Consumer Helpline: [consumerhelpline.gov.in](https://consumerhelpline.gov.in/)
- Diwali 2026 dates: widely published panchang calendars (Dhanteras 6 November, Lakshmi Puja 8 November). Regional dates for later days vary.
- The tenfold peak is a planning assumption, and the staffing figures are a worked example, not a forecast for any brand.
- Elision success story: [Nykaa](https://www.elisiontec.com/success-stories/nykaa/)
** 
---
_View the original post at: [https://www.elisiontec.com/ecommerce-customer-support-during-festive-sales/](https://www.elisiontec.com/ecommerce-customer-support-during-festive-sales/)_
_Served as markdown by [Third Audience](https://github.com/third-audience) v3.5.3_
_Generated: 2026-11-07 11:12:11 UTC_