Techbanq

Software · customer self-service

A customer portal is judged by the question it answers without a phone call

Customers do not come to a portal to admire it; they come with a bill they do not understand, a request they need progressed, a detail they need changed. Whether they leave satisfied depends on the account model, the Arabic, and the systems behind the glass — which is why we design those before any screen.

Serving Saudi Arabia from our Riyadh office and our engineering hubs in Lahore and Karachi

Market
Saudi Arabia
Written for
Head of CX, Head of Digital, COO
Decision
Give customers a self-service channel that actually resolves their questions

Information security for software delivery

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

The customer's path

One customer, four moments, and what the portal must do in each

The portal earns its keep moment by moment. Each of these either resolves on the screen or becomes a call — and which way it goes is decided by the systems wired in behind it.

01

First sign-in

A customer proves who they are and expects to see their own accounts — all of them, and nobody else's.

The identity and account model does the work: verified sign-up, recovery that does not require a branch visit, and an account structure that matches how customers actually hold products.

  • Identity
  • Account registry
02

The bill question

The commonest visit: why is this amount what it is, and how do I pay it.

The portal shows the live figure from billing with its breakdown, not a stale copy — and takes the payment through the methods customers here use.

  • Billing
  • Payments
03

The request

Something needs doing — a change, a complaint, a service order — and the customer wants to know it landed and where it stands.

The request is created in the CRM the service team already works from, with its status visible in the portal — one case, two windows, no parallel inbox.

  • CRM
  • Case management
04

Coming back

The second visit decides the habit: if the portal remembered nothing and notified nothing, the phone wins.

Notifications that arrive where the customer is, in their language, about the things they asked about — and a portal that opens on their situation, not a brochure.

  • Notifications
  • Preferences

Language and access

Arabic in a customer portal is an original, not a translation pass

A portal for this market has two first languages. That is a design constraint from the opening sketch, not a localisation task at the end: layouts must mirror correctly under right-to-left reading, numerals, dates and currency must follow the customer's expectations, and the Arabic itself must read as if it were written first — because for most of your customers, it is the version they will live in. Bills, error messages and notifications are where translated-last portals betray themselves, and they are precisely the texts a worried customer reads most carefully.

Accessibility belongs in the same sentence. A customer portal serves everyone who holds an account — including customers using screen readers, high zoom or a keyboard alone — so semantic structure, contrast, focus order and properly labelled forms are checked in both languages as part of the build, not audited after launch. A self-service channel that a portion of your customers cannot operate has quietly excluded them and sent them back to the queue the portal was meant to relieve.

Behind the glass

The back-end connections that decide whether self-service resolves

Every panel on the portal is only as good as the system it reads from and writes to. These are the connections the build actually consists of.

01

Identity and the account model

Who the customer is, which accounts they hold, and what each may see and do — designed before the first screen, because every later feature inherits its shape. National identity verification is integrated where the service warrants it.

02

Billing, read live

Balances, breakdowns and payment status come from the billing system at the moment of asking. A portal showing yesterday's copy of a disputed amount generates calls instead of deflecting them.

03

CRM as the single case file

A request raised in the portal is the same case the agent sees, with one history. The failure mode this prevents is the customer repeating their story to every channel.

04

Notifications with a return path

Status changes reach the customer in their chosen channel and language, and link back to the exact place in the portal where the matter continues — closing the loop that makes self-service a habit.

Our role

Building the customer portal around the questions people actually ring about

  1. 01

    Start from the call log

    Discovery begins with what customers contact you about today, in their words. The portal's first release is scoped to resolve the most common of those end to end, rather than to showcase features nobody rings about.

  2. 02

    The integrations as the build

    We treat the billing, CRM and identity connections as the substance of the engagement and the screens as their surface — because that is the order in which they determine success.

  3. 03

    Deflection read honestly

    After launch we look at which question types stop arriving by phone and which still do, and why — a qualitative reading that steers the next release. We do not promise a percentage in advance, because deflection is earned per question, not declared per project.

Which services customers may complete alone, and where a human must stay in the path, are service-design decisions that remain yours; we build the portal so the ones you choose actually finish on the screen.

Common questions

What buyers ask

Why does the account model come before the customer portal's screens?+

Because every screen inherits it. Whether a customer can hold several accounts, whether a family member may act on one, what a business owner sees versus an individual, how a closed account appears in history — these rules shape every page, and retrofitting them after launch means reworking the portal rather than extending it. The account model is also where security lives: the isolation that guarantees one customer never sees another's data is a property of the model, not of any screen. Screens are cheap to change; the model underneath them is not, so it gets designed first and deliberately.

Will a customer portal actually reduce the load on our contact centre?+

Only for the questions it genuinely resolves end to end, which is why we scope it from your call log rather than from a feature list. A bill enquiry stops arriving by phone when the portal shows the live breakdown and takes the payment; it keeps arriving when the portal shows a summary and the customer still needs a person for the detail. Some contact will and should remain — complex cases, vulnerable customers, moments where judgement matters — so the honest goal is moving the routine questions to the screen and freeing the centre for the calls that need a human. We read the effect qualitatively after launch, question type by question type, and let that steer what the portal learns to do next.

What does accessibility require of a customer portal beyond larger text?+

Structure a screen reader can narrate, in both languages: headings that describe, forms whose fields announce their labels and errors, and a focus order that follows the task. Everything operable by keyboard alone, because not every customer uses a mouse or a touchscreen. Contrast that survives sunlight and older eyes, states not signalled by colour alone, and notifications that do not vanish before assistive technology reads them. Under right-to-left Arabic all of this is verified again, since focus order and layout mirroring can break in RTL what worked in LTR. Built in from the start this is a discipline; bolted on later it is a redesign.

Plan it with us

A discovery session that maps your customers' top questions to the systems that hold the answers, and scopes the portal around resolving them.

What happens next

  1. 1We reply within one business day.
  2. 2A 30-minute scoping call with a senior consultant.
  3. 3A written proposal with scope, team, and timeline.

Or reach us directly

By submitting this form you agree to our Terms of Use and Privacy Policy.