Why I Built Schoolvoice: A Busy Father's Story of Fixing School–Parent Communication

Schoolvoice did not start in a boardroom or on a whiteboard full of market projections. It started with a feeling every busy parent knows: the quiet guilt of not being there.

I am Ali Bin Yahia, and before I was a founder, I was a father — a busy one. I traveled from place to place, trying to do my duty toward my business while still being a loving dad. Every time I felt bad, it wasn't because I didn't love my children. It was because I wasn't around. And the reason I was so busy was, in its own way, an act of love: I wanted to give them a very good life, and whatever they needed. But I still wanted to be next to them. So I started looking for something that could solve this problem for me.

The messages I kept missing

Back then, my kids' schools kept me updated by SMS. But SMS came with a lot of problems. It was short. And it arrived in the same crowded inbox as my bank alerts and traffic fines — so I didn't like to check my messages until the weekend. And sometimes, on the weekend, I forgot. As a father, I missed a lot of updates, including urgent ones.

What bothered me even more was how the messages were written. They were often short and without context, so I couldn't understand what the school actually wanted from me. I learned the reason later: SMS was expensive. Some schools were spending anywhere from forty thousand to a hundred and eighty thousand dirhams a year just on text messages. So they rationed them — they sent as few as possible, kept them short, or pushed a link to some other website to go and do something. And often, honestly, I didn't feel I had time for that.

There was another hidden cost. Schools here — especially in the UAE and international schools — often needed to send each message in both Arabic and English, and to both the father and the mother. That's the same message sent four times. No wonder they hesitated to send anything but the essentials. And so, again, we parents were left out of the loop.

When schools didn't text, they sent paper memos home. But I wasn't there to read them, and my kids were young — the note would be forgotten, or lost somewhere between the pages of a textbook. All of it added up to one stubborn thought: no. I want to solve this.

A designer who couldn't stop noticing what was broken

I began my career as a UX designer, and later became a UX specialist. That shaped how I move through the world. I walk down a street and watch how things work, and when something feels broken, I get this itch to fix it. At that time, I became certain of one thing: communication between schools and parents was broken.

Not because schools didn't want to reach parents — they did. And not because parents didn't care — they were simply busy with the weight of their own lives. It was broken because the tools were bad. That was the real problem, and it was worth solving. I was sure there were thousands of parents out there just like me, quietly wishing for a better way.

From a sketch to a promise

So I started building — though at first it wasn't even a real product. It was a set of high-fidelity wireframes. I took them to a few schools and administrators I knew, showed them the idea, and asked a simple, honest question: if I build this, would you pay for it? They said yes. "We like it. It will solve a lot of problems."

That was the permission I needed. But I didn't want to build on a hunch, so I dug deeper — and the more I looked, the more I saw.

Two sides of the same broken bridge

Schools were juggling a pile of fragmented tools. Some used SMS, some used paper, some had started using WhatsApp — and every one of them came with its own headaches. SMS was costly. Paper was slow and painful in a digital age. And when a message did reach me, I was left with the same question every time: okay… what do you actually want me to do?

There was no context, and no clear call to action. And even when I understood, the action itself was a chore. If the school wanted me to approve my child's trip, I had to print the form, sign it, scan it, and send it back. Or download an email, or an attachment, or go to yet another website to fill in a form. Everything was difficult.

The schools were struggling on their side too. Parents didn't reply and didn't engage, so staff were forever chasing them for a response. And when the paper slips finally came back, an administrator had to re-read them, re-type them, and rebuild a soft copy by hand. There was no proper way to collect feedback.

Then there was the noise. Schools would send a message and add at the end, "if you've already done this, please ignore." I couldn't tell the difference between the signal and the noise — whether a message was for me specifically, for all parents, or just a reminder to ignore. So I did what tired parents do: I started ignoring everything. Add the language barrier in international schools, and the picture was complete. The bridge between home and school was broken on both ends.

So we didn't build another WhatsApp

This is important: Schoolvoice was never meant to be a copy of WhatsApp or a fancier way to send SMS. We built it with focus. We designed it with both schools and parents in mind at the same time, solving each side's real problems, and obsessing over one thing above all — ease of use. That was my design philosophy from day one: make it simple enough that any parent, of any age or comfort with technology, can use it without a manual.

I was also lucky. My team was full of parents — and husbands of teachers. So we thought like parents and like teachers, because that's who we were. We looked at our own daily frustrations, and we built to solve them.

Every feature started as something we needed

People sometimes ask how we chose what to build. The truth is we didn't sit and brainstorm features in the abstract. Almost every part of Schoolvoice began as a real problem one of us lived through.

Actionable Messages — because I just wanted to know what to do

The heart of Schoolvoice is what we call Actionable Messages. On the message card itself, I see a clear action button — Read, Approve, Pay, Acknowledge — so I know exactly what's being asked, and I can do it right there, in one tap. No emails to open, no forms to hunt down, no other website. If a message concerns two of my children at the same school — even in different grades — I understand it's for both. And if it carries only one child's photo, I know instantly which one it's about. We added importance flags and reminder markers so I'd know at a glance when something was urgent. And we built the Smart Reminder, so a school can nudge only the parents who haven't acted yet — and stop bothering the ones who already have.

Stories — changing "how was your day?"

When we built Stories, I had a few reasons in mind. Schools love to show parents what happens during the day — but as a parent, I didn't want my children's photos on some public, generic platform. I wanted something private, where only the right people, maybe the parents of their classmates, could ever see them.

But there was a softer reason too. I wanted to change the most boring question I asked every single day: "How was your day?" You know the answer — "okay." Sometimes kids don't even know how to explain it. So I wanted that question to become, "I saw you in the lab today," or "I saw you in sports," or "I saw you drawing something." That small change turns a dead end into a real conversation over lunch or in the evening. And it lets me see, and celebrate, the effort of the teachers — the people who do so much for our children that we never get to witness. Schools can feel like black boxes; we only see the paper that comes home. Stories opens the box.

The Emergency Alert — the day I saw why it mattered

Some features were born from a single, unforgettable moment. I was visiting a school, trying to introduce Schoolvoice, when a child fell and was hurt. In an instant it was chaos. The manager was shouting, "Call his father! Call his mother!" — and no one answered. The number on file was wrong. The nurse froze, unsure whether she could give the child a certain medicine, or whether he was allergic to it. It was a frightening thing to witness.

We walked away and asked ourselves: the numbers are already in the system — why can't one tap reach every guardian of that child at once, even if their phones are on silent? That is exactly what the Emergency Alert became. One press reaches all of a single student's guardians simultaneously, breaks through silent mode, and keeps the whole exchange on the school's official, recorded channel. I hope no school ever needs it. But if they do, it's there.

Live Broadcasting — for the parent who's traveling

I built Live Broadcasting as the traveling father I was. There was an event at my kids' school I didn't want to miss. Schools that used something like Zoom had to send links out to parents — and inevitably forgot a few, because everyone lived in different WhatsApp groups. Personally, I don't like WhatsApp groups. Everything is buried in there; you scroll and scroll, and half of it isn't about your child, and every new year you're added to a new group all over again.

So now, if there's an event, the school simply chooses the classes it belongs to and starts broadcasting. Every related parent gets a push notification, taps once, and is watching live. No links, no lost invitations, no WhatsApp scroll.

Voice notes, translation, and a one-minute call

Not all of our parents read and write comfortably, and not all of them speak English. So we added in-chat translation, and we built voice notes — because a parent who can't easily type can simply speak. The funny part: teachers came back and told us parents were sending very long recordings, so we capped voice notes at five minutes and added playback speed for busy teachers. We believe a voice sometimes carries what text can't; writing can feel dry, and it's easy to misread. That same belief led to one of our newest features, secure Voice Calls — because sometimes a one-minute call is worth ten messages, and it should happen without anyone sharing a personal number.

More than a company — a legacy

If I'm honest about my own reasons, I didn't build Schoolvoice only to start a company or to make money. I wanted to build a legacy. I want to inspire my kids, and other young people, with a simple idea: if you find a problem, solve it. Bring something that adds real value to people's lives, and success will follow. Don't make money the goal — make value the goal, and the money comes with the success. Leave a good example for the people around you.

I also wanted to build something rooted in our culture and our region. There are excellent international players in this space, and I respect them. But I wanted to create something that genuinely reflects who we are.

The road was not easy

I want to be honest about the part that gets left out of most founder stories: it was hard. Much harder than a list of features makes it sound.

In the beginning, schools rejected us. We were a new, unproven company, and trust is not given to newcomers easily — it's earned, slowly. Even when a school was willing to listen, we ran straight into the hardest thing of all: change. People had their habits. Some teachers pushed back on a new way of working. Many schools simply didn't want to leave the tools they already knew, however broken those tools were. And some parents resisted too, because change asks something of everyone.

We didn't take it personally, and we didn't give up. We listened, we improved, we showed up again, and we proved the value one school and one parent at a time. Every piece of feedback — even the difficult kind — made the product better. That patience is the real story behind where we are today: a platform that schools across sixteen countries now use as their official channel to reach the families they serve.

Where we are, and where we're going

The idea may have started with me, but Schoolvoice was never a one-man project. My co-founder helped me turn a designer's dream into real, dependable technology, and the team helped us bring the right solution to parents and schools. The feedback we receive from families and educators every single day still shapes what we build and pushes us to make it better.

That's the honest story of why we built Schoolvoice — to fix something that was broken, to add value to schools and parents, and to leave a little inspiration behind. We're still just as passionate about where we're taking it next.

If your school is still fighting scattered messages, unread notes, and tools nobody enjoys, I'd love to show you what we built. Book a 20-minute Schoolvoice demo, or learn more about who we are.