Every shop knows the feeling. The offer post goes live, comments start arriving faster than anyone can read them, and the same five questions come in again and again. Getting your bot ready for peak campaigns is mostly quiet work you do in the calm weeks beforehand. You write clear answers, decide who handles what, and plan the messages you will send. This guide follows that order, with examples from small shops and the mistakes worth avoiding.
Why getting your bot ready for peak campaigns starts early
A peak campaign is any short period when demand jumps. That could be Ramadan evenings, the days before Eid, Black Friday week, or the rush when school lists come out. The questions barely change from one season to the next. What changes is how many people ask at the same time, and how little patience they have.
If you prepare during the rush, you are writing replies with one hand and packing orders with the other. If you prepare a few weeks before, the bot handles the repeated questions and your team spends its time on the conversations that need a person.
Start with one simple exercise. Open last season's conversations in the unified inbox and write down the questions you answered most often. That list becomes your plan.
Step 1: Write stock answers for the questions you already know
Stock answers are short, approved replies to the questions that come up every season. You want them ready before the first offer post goes out.
The usual list for a small shop:
- Price and offer details. What is discounted, until when, and whether the offer combines with others.
- Availability. Sizes, colours, and what happens when an item sells out.
- How to order. Ordering inside the chat, what details you need, and how the order is confirmed.
- Payment. Cash on delivery, card through your own provider, or pickup from the shop.
- Returns and exchanges. Especially for gifts bought before Eid or Black Friday.
- Opening hours. Ramadan hours often differ from the rest of the year, so say so clearly.
Write each answer the way you would say it at the counter. A perfume shop in Riyadh might write: "The Eid gift boxes are back. You can order here in the chat, and we'll confirm your order with you before we ship it." That reads better than a block of policy text.
In the no-code flow builder, turn the most common questions into quick paths. A shopper who picks "Delivery" gets the delivery answer straight away, with no typing and no waiting. Keep AI replies for open questions such as "Which of these suits a ten-year-old?" The AI answers in the customer's own language, so a mixed audience in the Gulf or Europe is covered without separate scripts.
If you find yourself typing the same sentence a third time in one day, it belongs in a stock answer.
Step 2: Get delivery questions right before anything else
In peak weeks, delivery questions often outnumber product questions. "Will it arrive before Eid?" "Do you deliver to my area?" "Can I collect it tonight?" These need careful answers, because a wrong promise turns into an angry message later.
Practical habits that help:
- Set a cut-off and state it everywhere. If orders after a certain day may not arrive before Eid, put that in the offer post, the stock answer and the order confirmation. Change it once the cut-off passes.
- Separate areas you serve from areas you don't. A bakery in Alexandria that delivers only within the city should say so in the first reply, not after the customer has chosen a cake.
- Offer pickup as a clear option. "Pick up from the shop" saves many last-minute orders.
- Confirm the order inside the chat. A confirmation that repeats the items, the address and the payment method catches mistakes before the courier leaves.
Never let the bot guess a delivery date. If the answer depends on the address or the item, the flow should collect those details and pass the chat to a person. "Usually" is fine. A firm promise the shop cannot keep is not.
Step 3: Plan the human takeover, not just the bot
Automation carries the volume, but some conversations need a person. Decide in advance which ones, so nobody improvises in the middle of the rush.
Hand a chat to the team when:
- the customer is upset or reports a problem with an order
- the question involves a custom request, a large order or a special price
- the bot's answer clearly didn't help and the customer asks again
- the conversation touches payment problems or a refund
With human takeover, a team member picks up the chat in the unified inbox and the bot stays quiet in that conversation, so the customer never gets two answers at once. Read more about choosing the right moment in when to hand over to a human.
Then plan the people side:
- Assign by topic. Use assignment rules in the team inbox so order problems go to one person and product questions to another.
- Cover the real peak hours. In Ramadan that often means after iftar and late at night, not the usual office hours.
- Reply from anywhere. The mobile app lets someone on the evening shift answer from home or from the shop floor.
- Agree on tone. A short shared note on how you greet customers, apologise and close a chat keeps replies consistent when several people answer.
Step 4: Broadcast etiquette for the busy season
Peak campaigns tempt every shop to message everyone, often. That is the fastest way to lose people who liked you. Broadcast messages and reminders work best when they reach people who care about the news, with something they can actually use.
Good etiquette looks like this:
- Follow each platform's messaging rules. Messaging channels set their own rules on who a business may message, what it may send and when. Check those rules for the channel you plan to use before you write a word.
- Match the message to the people. If only some of your customers care about school supplies, a back-to-school message to everyone reads as noise. A bookshop in Cairo earns more goodwill by keeping the school list for the parents who asked about it.
- Send fewer, better messages. One clear announcement when the offer starts and one useful reminder before it ends will do more than daily pushes.
- Respect opt-outs every time. Leave out anyone who asked not to be contacted, however tempting the offer.
- Pick humane times. Avoid prayer times and the minutes around iftar in Ramadan, and don't send late at night.
- Be ready for replies. Every broadcast starts conversations. Schedule it when your team is around to answer in the inbox.
For a deeper look at tone and frequency, see broadcast messages without spamming.
Step 5: Schedule the content and test the paths
Once replies and people are ready, put the public side in place. Schedule the offer posts and short videos ahead of time, so publishing doesn't depend on someone remembering at midnight. Use the AI Studio to prepare captions and images in one sitting rather than every morning.
Then test like a customer. Comment on your own test post, send a message, try every quick path, place a test order and ask a delivery question. Check that each path ends somewhere useful: an answer, an order or a person. Fix any loop where the customer goes in circles.
It also helps to ask someone outside the team to try it. A friend or relative who has never seen your flows will find the confusing step in minutes, because they read the replies the way a real shopper does.
What to avoid
- Copying last year's answers without checking them. Prices, hours and delivery areas change.
- Letting the bot promise what the shop can't deliver, especially dates and stock.
- Sending broadcasts to everyone because the season feels urgent.
- Leaving no person on shift during the hours your customers actually shop.
- Changing the offer mid-campaign without updating the stock answers.
After the campaign
When the rush ends, send a short thank-you to customers who ordered. Check the analytics dashboard while the season is still fresh, and read back through the conversations in the inbox to find the questions the bot couldn't answer and the replies that confused people. Write down three things to change. That note is the first page of your plan for the next peak.
Common questions
How early should I start preparing for a peak campaign?
Start as soon as you know the dates and the offer. That gives you time to review last season's chats, write stock answers and test your flows. Waiting until the week of the campaign usually means fixing things while customers are already writing.
Should the bot answer delivery questions on its own?
It can answer the general ones, such as areas you serve, pickup options and order cut-offs. When the answer depends on a specific address or item, the flow should collect the details and hand the chat to a person. Avoid any reply that promises a firm date the shop can't guarantee.
What happens when a team member takes over a chat?
The team member answers from the unified inbox and the bot stays quiet in that conversation. The customer talks to one voice instead of two. Other chats keep running with automation as usual.
How many broadcasts should I send during a campaign?
There is no ideal number. Send only what is useful to the people receiving it. A start announcement and a reminder before the offer ends are usually enough, and each platform's own messaging rules always apply. Leave out anyone who has opted out.
Can I message customers who never contacted my shop?
Messaging platforms generally limit what a business may send to people who haven't written to it first, so check the rules of each channel. To reach new people, rely on your scheduled posts and videos and on quick replies to the comments they bring in.
What should I check right after the campaign ends?
Read through the season's conversations to see where customers got stuck and which questions the bot couldn't answer. Update your stock answers and delivery replies while the details are fresh. That makes the next campaign easier to prepare.



