The Eduway student engagement platform. Journeys do the work. Calendar and broadcast handle the rest.
Journeys run each student’s path on their own, and book a call when it matters. Calendar: messages on the term’s dates, each on the channel that fits. Broadcast: one message, one channel, now or scheduled, with a live preview.
Design it on a canvas. Simulate it. Deploy it to thousands.
Drag-and-drop canvas
Messages, questions, menus, waits and conditions. Branch on a reply or on profile data, and personalise every message with parameters.
Every channel in one flow
WhatsApp first, plus SMS, email, Telegram, voice and web chat, in a single journey, with fallback if a channel fails.
Triggers
A status change in your SIS, a form, a WhatsApp keyword or a segment starts the journey. Nobody has to press send.
Design to execution
Simulate with a test student before you deploy. One run is one journey for one student, and thousands run in parallel.
Journey Builder
Describe the journey in one sentence. Eduway drafts it.
Then edit it on a canvas, test it on a sample student and deploy. Thousands run in parallel, one for each student.
Guide new admits from offer to registration: deposit, documents and fees. Remind anyone silent after 3 days, and offer a call with Admissions if they are stuck.
Drafting the journeySimplified from the Journey Builder. The real canvas is one click away.
Admin interface
Where your engagement team runs everything.
Insights dashboard
Live journeys, message volume per channel, top journeys with week-on-week change.
People and segments
One directory for students, prospects, parents, alumni and professors. CSV import or API. Segments built from plain words.
Outreach
Campaigns, a calendar of messages on the term’s dates, and broadcasts, now or scheduled, with a live preview.
Chatbot
A branded website assistant trained on your documents. For anything personal, it offers a call.
Governance
Communication logs, audit trail, media library and credits. Available in English, Arabic and French.
AI does 3 jobs a team cannot do at scale. People keep the decisions.
-
1Predict
Predictive segments surface students likely to drop out, burn out or need tutoring, before anyone asks. Every flag shows its signals.
-
2Draft
Your team starts from a draft, not a blank canvas: the flow, the timing and the tone, in Arabic and English.
-
3Answer
A website and WhatsApp assistant answers 24/7 from your institution’s own documents. For anything personal, it offers a call.
Everything that sends, sends through one engine.
Pick who. The journey picks what, when and where.
- Who
- 640 admitted, not confirmed
- What
- Step 1 of 3, in Arabic or English
- Where
- WhatsApp, then SMS if unread
- Then
- A call booked, if she replies 2
Every message logged: sent, delivered, read, replied.
640students, one step at a time
Every role sees only what it needs.
| Interface | Who uses it | Platform |
|---|---|---|
| Admin interface | Administration and engagement team | Web |
| Journey Builder | Admins, from inside Admin | Web |
| Recruiter interface | Recruitment and admissions staff | Web |
| Educator interface | Teachers, professors and advisors | Web |
| Alumni Admin | The alumni relations office | Web |
| Alumni App | Graduates, in Arabic and English | iOS, Android |
| Company interface | Employers invited by the alumni office | Web |
WhatsApp first, with 5 more channels in the same journey.
Not read on WhatsApp? The journey tries the next channel on its own, and your team never has to chase it.
- SMS
- Telegram
- Voice
- Web chat
89%of internet users aged 16+ in the UAE used WhatsApp in the past month. In Saudi Arabia, 82.9%.GWI Q2 2025, via DataReportal Digital 2026
- Mon 09:00 WhatsApp Reminder: housing deposit due Friday Delivered
- Tue 09:00 Journey Not read after 24 hours. Switch channel. Rule
- Tue 09:00 SMS Same reminder, shorter, with the link Delivered
- Tue 18:40 SMS Read. Deposit paid at 18:52. Done
Nothing gets ripped out.
Eduway sits beside the systems you already run. Your SIS, LMS, CRM or a web form can start a journey with an API call; people and segments can come in by API or a scheduled export; replies and outcomes are logged where your team can see them.
- API triggers from your SIS, LMS, CRM or forms
- People import by API, CSV or a scheduled export
- Hosting agreed with you in the contract, confirmed in scoping
- You are the data controller
Made for universities in this region, in both of its languages.
Arabic and English in every journey and in the Alumni App. Hosting is agreed with you in the contract, confirmed in scoping.
- Hosting
- Agreed with you in the contract, confirmed in scoping
- Access
- Role-based access with per-module scopes; staff sign in with OAuth 2.0 and OpenID Connect
- Audit
- Every message logged with delivered and seen status
- Consent
- Opt-in on every channel; WhatsApp on Meta’s official platform
- Your data
- You are the data controller; Eduway processes it on your instructions
- Reviews
- Security controls shared under NDA in your security review
Before we talk.
What is a journey?
A journey is a sequence of messages, waits, questions and conditions that runs for one student at a time. You build it once; Eduway runs it for every student who meets its trigger, on the right channel, and logs every step.
Which channels does Eduway support?
WhatsApp first, plus SMS, email, Telegram, voice and web chat. A single journey can use several, with fallback when a message is not delivered or read. Push notifications are part of the Alumni App.
Where is our data stored?
Hosting is agreed with you in the contract, confirmed in scoping. Access is role-based, staff sign in with OAuth 2.0 and OpenID Connect, and every message is logged with delivered and seen status. You are the data controller, and we share our security controls under NDA in your security review.
Which languages does the platform support?
Journeys, the assistant and the Alumni App work in Arabic and English. Admin is available in English, Arabic and French.
See the engine running on your own journeys.
A discovery session built around one stage of your student lifecycle.