Too many chats at once? How a small team handles a rush

What a rush usually is

For a small business, a rush is rarely random. It is the evening before Eid, the first day of a sale, a delivery delay that affects many orders, a social post that sent visitors to your site, or a price change. That is good news: when you know the cause, most of the chats are asking the same thing.

The rush plan

Step 2: find the common question

During a rush, five minutes spent reading saves an hour of typing. If eight of the last ten chats ask "is the sale price valid online too?", that is your answer to write.

Step 3: one clear answer, published

Write the answer in two or three sentences, in both languages you serve, and publish it so everyone uses the same words and the same facts. In StayReplied, documents and price records are drafted, reviewed and published, with every version kept, as the docs describe; for a fast-moving situation, a short published update beats each person improvising (standard answers that don't sound canned).

Step 4: split the queue

With two or three people, split by type, not by arrival:

• Quick answers: chats that the common answer, or one more sentence, closes. One person works through these fast.
• Complex chats: order problems, bookings that need checking, complaints. These get an owner each and an honest time (the five complaint steps).

In the StayReplied unified inbox, taking a conversation makes you its owner, presence shows who is in which chat, and you are asked to review before sending if the customer wrote again while you typed, which matters when customers add messages while they wait.

Step 5: acknowledge, honestly

A customer waiting in silence during a rush assumes the worst. A short line buys patience:

• "Thanks for waiting. We're busier than usual today; I'll reply to your question within 20 minutes."
• "شكرًا لانتظارك. لدينا ضغط أكبر من المعتاد اليوم، وسأرد على سؤالك خلال 20 دقيقة."

Then keep the promise. If 20 minutes becomes 40, say so before the 20 run out.

What not to do in a rush

• Answer in arrival order. Quick chats wait behind long ones and everyone waits longer.
• Improvise prices or exceptions to get through faster. They come back as complaints.
• Copy-paste without reading. A customer who asked something different gets a wrong answer, and a second chat.
• Answer from personal phones to speed up. The next person cannot see what was said.

Can AI absorb a rush?

It can help with the common question if you have set it up beforehand. No plan includes AI today; with your own Anthropic key, the AI answers only from published knowledge, so step 3 is what makes it useful. The answer mode is set per channel (off, draft for a person, or answer), and daily and monthly AI budgets stop the AI at the limit while human replies keep working (AI sales and support). Complaints and refund demands still go to a person, so in a delivery-delay rush your team is still needed.

Prepare before the next busy day

• Write down your predictable rush days: holidays, sale launches, month-end (the holiday checklist).
• Prepare the likely common answers in advance and publish them that morning.
• Put an extra person on the rota for those hours, if you can.
• Update the welcome message to mention the busy period and the main answer ("Sale prices apply online and in store").
• Check your plan's capacity. Message records per month are listed on the pricing page: 10,000 on Starter, 40,000 on Team and 100,000 on Business. Messages above the limit are kept in the queue, never dropped, and your team is told.

When this is not for you

If you have never had more chats than one person can handle, a rush plan is insurance rather than a need; keep the five steps in a note for the day it happens. And if your rush comes mainly by WhatsApp or phone, the same steps work, but web chat is the channel you connect today and WhatsApp is coming soon; who StayReplied is for describes the teams it fits.