In this article
Riyadh Season 2026 opens on 21 October, and for most Saudi SMEs a Riyadh Season business plan is really an operations plan. The Chairman of the General Entertainment Authority announced the 21 October launch, so the first wave of extra footfall, bookings and questions arrives in days, not months. Cafés, retailers, event suppliers, transport companies and the contractors behind them all feel it in the same week.
The companies that come out of a busy season well are rarely the ones with the biggest team. They are the ones whose requests all land in one place, get a priority, and get an answer inside the time the customer expected. What follows is a readiness plan for sales and support, written for a company of five to fifty people.
What actually changes when the season opens
Demand does not only grow, it changes shape. Enquiries move to the evening and late night, more of them arrive from a phone, and a bigger share come from people who have never bought from you before. First contact becomes a sales moment and a service moment at the same time.
Three pressures arrive together:
- Volume. More enquiries per hour, squeezed into a few hours of the day.
- Speed. A customer comparing venues or suppliers tonight will not wait a day for a price.
- Memory. With extra staff and long shifts, whoever answers at 11pm has no idea what was promised at 2pm.
Volume you can staff for. Speed and memory are process problems, and that is where the lost revenue usually hides.
Map your demand spikes before 21 October
Start with last season's numbers, even rough ones. Look at your busiest days, the hours inside those days, and the five questions that came up most often. If you have no history to look at, use the last two Eid weeks as a stand in and adjust upwards.
For every spike you expect, write down three things: what people will ask, who can answer it, and what a good answer contains. Price and availability questions need a current price list and a booking view. Refund and complaint questions need a written policy. Doing this on paper in the quiet week is what stops improvisation in the loud one.
Then set a capacity number you can defend. If one agent handles roughly 25 conversations in a shift and you expect 160 on a Friday evening, you need six people on that shift or a way to cut the work per conversation. Saved replies, a short FAQ page and a clear price list all cut the work per conversation.
Put every request in one shared inbox
The most common failure in a peak week is not a rude answer, it is silence. A message sits in one person's phone, a call goes unlogged, and a paying customer hears nothing. A help desk system for Saudi businesses fixes that by turning each customer question into a ticket in one shared inbox, with a priority, a status and a named owner.
Two things matter more than any feature list. First, every request has to enter the same queue, so nothing depends on one person remembering. Second, anyone picking up a ticket should see the customer's history next to it, including earlier tickets and the invoices and payments on the account, so the answer at 11pm matches the promise made at 2pm.
Daftarix answers in Arabic or English depending on the language the customer writes in, which matters when a season brings visitors from outside the Kingdom alongside regular local customers.
Set response targets your team can actually keep
A target nobody can meet is worse than no target, because the team stops trusting the board. Pick three levels, write an example for each, and agree who owns it. Keep it on one page and print it for the shift.
| Priority | Example | First response target | Owner |
|---|---|---|---|
| High | Booking failed, duplicate charge, event starting today | 15 minutes | Shift lead |
| Normal | Price and availability, group booking, invoice copy | 2 hours | Sales agent on duty |
| Low | General information, future dates, partnership offers | 1 working day | Next available agent |
Review two numbers daily during the season: open tickets and first response time. If open tickets grow for two days in a row, you have a staffing or a routing problem, and it will not fix itself. Complaint volume in the Kingdom is already high enough that slow handling is a growth issue, not only a service one, as we covered in our look at consumer complaints in Saudi Arabia in 2026.
Get sales ready, not just support
Seasonal enquiries are perishable. A group booking request on Thursday night is worth very little on Sunday morning. The fix is preparation rather than speed heroics: build the quotations before the rush.
Prepare three or four standard packages with fixed prices and a clear note on what is included, so an agent sends a correct quotation in two minutes instead of asking a manager. Decide in advance the discount an agent may approve alone and the point where a manager has to sign. Write down the handover rule too: when a support ticket turns into a buying question, who takes it and how fast.
Keep every enquiry in your sales records with a source, so that after the season you know which channel brought real business and which only brought noise. Quotations, invoices and VAT follow the same records, which keeps accounting out of a reconciliation mess in November.
A ten day readiness checklist
- List your expected spike days and hours, and the staff on each shift.
- Agree the three priority levels and response targets, and print them.
- Route every channel you use into one shared ticket inbox.
- Write saved replies for your ten most common questions, in Arabic and English.
- Publish the current price list and the refund policy where agents can reach them in one click.
- Prepare standard quotation packages and the discount approval limits.
- Give temporary staff access on day one, with a 30 minute walkthrough.
- Name a shift lead for every shift, including late evenings and weekends.
- Set the daily review: open tickets, first response time, tickets older than a day.
- Agree one escalation phone number for anything that affects a customer tonight.
After the season, keep what you learned
In the first week after the season closes, hold a one hour review with the numbers in front of you. Which questions repeated most, which shift fell behind, which promise did you miss, and which package sold best. Turn each answer into something permanent: a new saved reply, a changed target, a page on your site, a different staffing pattern.
That is how a season stops being an annual emergency and becomes a repeatable playbook. The teams that write the review down are the ones that need fewer people the following year.
If you want sales enquiries and support tickets in one place before 21 October, book a demo and we will walk through your busiest week with you.
Frequently asked questions
When does Riyadh Season 2026 start?
The Chairman of the General Entertainment Authority announced 21 October as the launch date for Riyadh Season 2026, reported by the Saudi Press Agency. Check the official channels for the programme and individual event dates.
How many extra support staff do we need?
Work from conversations, not guesses. Take the conversations one agent handles comfortably in a shift, divide your expected peak volume by that number, and staff the gap. Cutting the work per conversation with saved replies and a clear price list is usually cheaper than hiring.
What is the single most useful change before a peak week?
Getting every request into one queue with an owner and a status. Most peak season complaints come from requests nobody answered, not from answers customers disliked.
Does a help desk suit a team of five?
Yes, and small teams often gain the most, because there is no slack to absorb a dropped request. A shared inbox with priorities and a visible response time is useful from the first busy weekend.
How should we handle after hours enquiries?
Decide what you promise and say it clearly. Set an expected response window for messages that arrive after closing, assign a shift lead for late evenings during the season, and keep one escalation number for issues that affect a customer the same night.
