Approve, reply, done — without opening the app

August 20, 2026 · Abdulkareem H. Ali

A notification has always been able to tell you something. Until now, that was all it could do.

A leave request needs a decision. A guardian has asked a question. An announcement has gone out. Each one arrives on your phone, and each one asks the same thing of you: unlock, wait for the app, find the screen, find the button. The decision itself takes a second. Everything around it takes a minute.

In the latest Tawaasal app, a notification carries the verb as well as the news.

Decisions, from the notification

A leave request now arrives with Approve and Decline on it. Tapping either opens the app directly on that request's decision screen, with the confirmation ready.

Note the shape of that: the notification is a shortcut, never a bypass. Both decisions still pass through the app's own confirmation — and approving now confirms in the app too, which it never used to. There is one approve behaviour, not a screen version and a notification version.

That rule matters more than it looks. If your approval permission was withdrawn after the notification was sent, tapping Approve does nothing but show you the screen — holding the notification grants you nothing. And if a colleague decided the request while your phone was in your pocket, you land on a request that is already decided, offering no second decision.

Reply from the lock screen

A message notification carries Reply. Type the answer where you stand, and it goes.

It lands in the conversation exactly as if you had typed it inside the app, because it travels the same path: the same permissions, the same school, the same read receipts, the same notification to the person you answered.

One detail we are quietly pleased with — answer the same notification on your phone and your tablet, and the school receives one message, not two. The second device is simply told the reply was already sent, and shows you the words you no longer need to send.

Mark as read, and Request leave

Announcements and homework notifications carry Mark as read, for the times when the preview was the content. It clears the moment you press it.

And an absence alert now carries Request leave, opening the form on that child and that date, already filled in.

That last one is a small change with a different feeling. An absence alert reads like an accusation. A Request leave button reads like an invitation to explain — and it puts the explanation exactly where the school needs it to go.

Some notifications say nothing on purpose

A safeguarding or wellbeing notification carries no action buttons at all — and no preview either. On a lock screen it says only that something in Tawaasal needs your attention. No student name, no concern, no summary.

A lock screen displays whatever it was sent, in front of whoever is in the room, and no setting can take that back afterwards. So the detail is never sent: it is withheld on our servers before the message is composed, rather than hidden by the phone once it arrives.

And the rule is structural rather than remembered. A safeguarding or wellbeing notification cannot be given an action button — the attempt fails before the program ever runs.

In the reader's own language

Every button is written in the language of the person receiving it, across all eleven languages Tawaasal speaks, including full right-to-left. The word on the button is the same word on the screen it opens.

Nothing new is being sent

This adds verbs to notifications you already receive. It sends nothing new, and it overrides none of your notification preferences.

And where a phone or its operating system is too old to draw action buttons, the notification behaves exactly as it did yesterday: tap it, and the app opens on the right screen. Actions are a bonus, never a requirement.

The update is on its way to the App Store and Google Play. Once it arrives, the next leave request you receive can be decided before you have put your phone back down.