Wataniya

Two departments were buried in work that customers could do themselves

Wataniya Insurance customers had no way to manage their own policies online. Every add-on request — adding a driver to a car insurance policy, extending geographic coverage, requesting a cancellation — required a phone call or a visit.

This created a compounding problem on two fronts simultaneously: the call centre was handling a relentless volume of routine requests that required no specialist knowledge, and the operations department was manually processing the same requests in their back-end systems, one by one, every single day.

The core tension

"Customers were waiting on hold for tasks they should be able to do in two minutes. Staff were spending their days on data entry instead of actual customer service. Neither side was getting value from the interaction."

Understanding the problem before designing the solution

Before opening a single design tool, I ran structured research sessions with each affected department. The goal was to map the full picture — not just the surface complaints, but the underlying reasons these problems existed and what a realistic technical solution might look like.

1. 01
   Call centre research sessions

   Sat with the customer care team to document the most frequent request types, average handling times, and the exact manual steps involved. Identified that driver additions and geographic coverage changes made up the majority of call volume.

2. 02
   Operations department mapping

   Walked through the back-office workflow step by step with the operations team. Documented each manual touchpoint in the policy modification process — this became the blueprint for what the system needed to automate.

3. 03
   Technical discovery with the dev team

   Worked with the development team to understand why the self-service capability didn’t already exist — whether it was a data access issue, a platform limitation, or a policy constraint. This shaped which features were achievable in the first release.

4. 04
   Wireframes and user flow design

   Translated the research into a customer-facing user flow — login, policy overview, action selection, confirmation — then built interactive prototypes for stakeholder review before moving into OutSystems development.

A self-service portal that puts customers in control of their own policies

The solution was to build a dedicated self-service portal where customers could log in with their existing Wataniya account and perform policy modifications themselves — without calling, without waiting, and without involving any member of staff.

I designed and developed the portal end-to-end on OutSystems, integrating with the eBao insurance platform for policy data. The portal was simultaneously delivered as a web application and as a native mobile app for both iOS App Store and Google Play.

Customers handle their own policies. Staff focus on what matters.

The Self-Service Portal became the first customer-facing digital platform in Wataniya Insurance’s history. Customers can now log in and modify their policies independently — at any time, from any device — without needing to contact the company at all for routine changes.

What changed

"The portal didn’t just digitise a process — it redistributed how two departments spend their working day. The call centre isn’t a bottleneck anymore. Operations isn’t a data entry team anymore. That’s the outcome I’m proudest of."

The customer care team now operates in an oversight and excellence role — monitoring activity, resolving edge cases, and focusing on the complex customer situations that genuinely need a human. The operations team shifted from manual data entry to quality control. Both departments gained time back for work of higher value.

Staff needed for routine policy changes

0

Customer access, no business hours dependency

24/7

Live apps shipped: iOS + Android

2

Check it live ↗

What I learned