The comment section is a storefront that most Egyptian brands leave unstaffed after six in the evening, which happens to be when the majority of their customers are looking. Community management is not a junior task bolted onto whoever does the posting. It is the part of social media where money changes hands, and it is entirely possible to run it well with two people if the system underneath is right.
Community management in Arabic starts with choosing your dialect
Your audience writes in at least three registers. Modern standard Arabic, which reads formal and slightly distant. Egyptian colloquial, which reads human. And Franco Arabic typed in Latin characters with numbers, which is how a large share of younger customers write on a phone. Add English, and code switching inside a single sentence, and you have a problem no template solves on its own.
Pick a house voice and write it down. Ours for most Egyptian consumer brands is colloquial Egyptian for ordinary replies, standard Arabic for anything official such as a policy statement or a public apology, and English only when the customer opened in English. Reply in the register the customer used. Someone who wrote in Franco and receives a formal standard Arabic paragraph feels handled by a machine, and half the time they are right.
A reply bank, not a script
Scripts fail in chat because customers arrive mid thought. What works is a bank of forty to sixty short blocks that an agent assembles: price and availability, delivery windows by governorate, the returns policy in one sentence, sizing help, an apology that admits the specific fault, and the escalation line. Store them as saved replies in the business inbox so nobody is retyping them at eleven at night.
Then write the escalation ladder on a single page. What an agent resolves alone, what needs a supervisor, what goes to the founder immediately, and what never gets answered in public. Safety complaints, legal threats, anything naming an individual employee, and political or religious arguments in the comments all belong in that last group.
Publish your hours and defend them
Two people cannot cover a day that starts at nine in the morning and peaks at eleven at night. Pretending otherwise produces slow replies at unpredictable times, which reads worse than a clear limit. Publish response hours in the profile and in the automated greeting, staff a genuine evening shift if evenings are when your customers buy, and write an away message that says when a human returns instead of thanking the customer for their patience.
Ramadan breaks every assumption in that plan. Traffic moves to late night, complaints about delivery timing spike, and a normal daytime rota leaves the busiest hours uncovered. Build the Ramadan rota weeks in advance, not in the first few days of it.
Measure three things: median first response time, the share of conversations that end in an order, and the number of issues that had to be escalated twice. Those three tell you whether the community is being managed or merely watched.
Most of this is process rather than headcount, and it is one of the first things we rebuild inside a social media strategy and management engagement.
