Most marketing automation courses sold in Cairo are tool tours. You get shown where the buttons are in one platform, you build a welcome email, and you leave with a certificate and no ability to design a flow that survives contact with a real contact list. The subject is not hard, but it is taught in the wrong order, and the wrong order is why graduates can operate a tool and not fix one.
Here is what the module should contain, in the order that makes the later parts possible, and what it should say about the channel that Egyptian businesses actually automate.
Automation is a data problem first
A workflow is a set of instructions that reads a contact record and decides what to do. If the record is wrong, the workflow is confidently wrong at scale, which is worse than doing nothing by hand.
So the first sessions should be unglamorous. What a contact record is. What happens when the same person arrives twice, once from a form with a mobile number and once from a chat with an email. Which field is the identity key and why picking the wrong one creates duplicates that no later clean-up fully repairs. How a lifecycle stage differs from a tag, and why using tags as stages produces a database nobody can report on six months later.
A course that reaches the workflow builder in session one has skipped the part that decides whether anything built in it works.
Triggers, not schedules
The conceptual jump that students miss is from time to event. A newsletter goes out on Tuesday. A flow fires when something happens: a form is submitted, a stage changes, a cart is abandoned, a payment fails.
Once that lands, the hard questions become askable, and these are the ones to listen for in a syllabus. What happens if the trigger fires twice. What happens if someone enters a flow they are already in. What stops a contact receiving three messages in an hour from three different flows that each individually made sense. Does the flow have an exit condition, and what is it. Who gets told when it breaks.
Those five questions are the actual content of the subject. If the course cannot tell you how it teaches them, it is a tool tour.
The channel Egyptian businesses actually automate
Email is on every syllabus. In practice the automated channel here is WhatsApp, and it comes with documented rules and a documented price that moved recently. A course that teaches flows without teaching these is teaching something students cannot deploy.
Meta's documentation is explicit that businesses are required to obtain opt-in permission before messaging people on WhatsApp. The opt-in has to state clearly that the person is agreeing to receive communication from the business, and it has to name the business. It does not have to be WhatsApp-specific, and it can be collected by SMS, on a website, through a phone IVR flow, or on paper. Meta also suggests taking separate opt-ins per message category rather than one blanket consent, because it lowers the chance of being blocked.
Then there is volume. The platform's documented messaging limits apply at the business portfolio level and count unique users messaged outside customer service windows in a moving 24-hour period. A new portfolio starts at 250. Getting to 2,000 requires either business verification or delivering 2,000 template messages to unique numbers across a 30-day moving window with a high template quality rating, after which Meta reviews quality before granting the increase. From 2,000 the limit scales automatically to 10,000, then 100,000, then unlimited, and each step needs high-quality messaging across all numbers and templates plus having used at least half the current limit in the last seven days. When the criteria are met the increase lands within six hours.
Read that again as a student would need to: the sequence you design has to work inside a cap that starts at 250 a day and only rises if the messages are good. That constraint changes what a sensible first flow looks like, and no tool tour will mention it.
Email gets one session, not six
Email automation is worth teaching and it is a smaller subject than it used to be, because the difficult part moved from writing to deliverability. The sender requirements, the spam rate ceiling, authentication and one-click unsubscribe are the gate, and we have set them out in what changed for email and why deliverability comes first. A good automation module points at that, teaches the flow mechanics once, and spends the recovered hours on the data model instead.
Where a course gets this backwards, you can tell from the hours: four sessions on writing subject lines, none on why the sends are landing in spam.
What belongs on the syllabus, and what does not
Belongs:
- The contact data model, deduplication and identity keys.
- Lifecycle stages, and reporting that uses them.
- Event-triggered flows, with entry and exit conditions written down.
- Consent capture, storage and withdrawal, for each channel separately.
- WhatsApp template categories, quality rating and the messaging limit path.
- One monitoring habit: a weekly look at what the flows actually sent.
- Handover to sales, including what a salesperson sees when a flow has been running.
Does not belong, or belongs elsewhere:
- A tour of six platforms. One platform properly, and the concepts are portable.
- Lead scoring models with ten criteria, before the student has clean data to score.
- Anything described as a growth hack.
- Attribution theory, which belongs with the analytics module and its own honest limits.
Who needs this module and who does not
It pays off for three people. Someone running marketing in a company with a list and a CRM already in place, because they have the raw material and no system. A media buyer whose cost per lead is fine and whose lead-to-sale rate is not, because the leak is after the click. And a business owner doing follow-up by hand on WhatsApp and losing track of who has been contacted.
It does not pay off yet for a fresh graduate with no account to practise on, and this is the honest answer rather than the convenient one. Automation taught on a demo database is the least transferable thing in marketing, because every real problem in it comes from dirty data you did not create. If you are starting out, the foundations in which tools come first and why and a grounding in how a funnel actually behaves will serve you better, and automation will make sense a year later when you have a list that is yours.
The sequence is the lesson, and it is not only a marketing one
The useful insight in automation is that the shape of a follow-up sequence matters more than any single message in it. That is understood more rigorously on the sales side than the marketing side, and it is worth reading across: BDG Labs set out what a follow-up cadence should look like after first contact, including how many attempts are reasonable and where sequences go wrong. Swap the channel and the logic transfers directly to a nurture flow.
Questions to ask before you pay
Four, and the answers are quick to judge.
Which platform will I build in, and do I keep access after the course ends? A free tier you can still log into is worth more than a shared demo account you lose.
Do we work on real data? If the answer is a sample database, ask whether you can bring your own list, even a small one.
What do I ship by the last session? The useful answer is a named flow that is live and sending, not a diagram.
Who teaches it, and what have they run? This is the one that separates courses, and the general version of the question is in what a performance course should actually teach.
The honest limits
We cannot tell you that an automation course raises your salary, and we have no data that would support the claim. What it changes is the type of work you are trusted with, because someone who can build and debug a flow is holding a system rather than performing a task.
And the platform numbers above will move. The messaging limit path and the pricing model have both changed inside the last two years, which is itself the point worth taking from the module: learn where the documentation lives and check it, because the course notes will be out of date before the certificate is a year old.