Sign-in and session review
Password reset, device memory, concurrent sessions, and the half-hour after a customer thinks they have left the portal.
From RM 6,400 · 5–7 working days
Kuching · Sarawak
We read the portal your customers already live in.
Schema Signal Hub writes audits of customer portal applications — sign-in, account home, bills, documents, and the chores people only attempt when something is already wrong. You receive a dated pack, not a dashboard mock-up.
Primary engagement
A full reading of the live customer portal
Most teams do not need another workshop. They need someone to sit with the URL customers actually use, walk the journeys that generate tickets, and write down where the screen, the copy, and the record disagree.
The full audit is our usual starting point: agreed roles, agreed environment, a finding register, and a close-out you can take to the people who will change the portal. Fees are quoted in Malaysian ringgit and paid by invoice — nothing is charged through this site.
Also commissioned
Narrower readings when the whole portal is too much
Personal data and account mapping
What the portal stores, shows, exports, and forgets — read against how Malaysian customers actually use account pages.
From RM 8,900 · 7–10 working days
Self-service flow walkthrough
Bills, tickets, appointments, document requests — the chores customers hoped they would never need a counter for.
From RM 7,200 · 6–8 working days
Schema and contract check
Forms, APIs, and exports compared with what the screens promise — the quiet mismatches that become night-time incidents.
From RM 9,600 · 8–12 working days
Remediation verification pass
A second reading after your team has fixed the first audit. Same journeys, new evidence, a shorter report.
From RM 4,800 · 3–5 working days
From the studio
What a sponsor actually walks away with
A letter, not a score
The first page is for the person who paid. It names the environment, the limitation, and the three findings that will still hurt customers next month if nobody owns them.
A register with evidence
Each row has a customer consequence, a place in the journey, and a suggested owner. Screenshots sit with the row they belong to.
A list you can retest
When fixes land, we can walk the same paths again. Memory is a poor audit tool. The retest list is dated on purpose.
Notes
Recent writing from the reviews
Portals that create their own tickets
A customer portal is meant to deflect contact. Some of them manufacture it. Here is how that shows up in Kuching support queues.
The half-hour after sign-out
Customers believe they have left. The portal sometimes disagrees. Shared counters and family tablets make that disagreement expensive.
Read the schema before the screen
Labels are a story. Fields are a contract. Audits go faster when you start with the names the system already uses.