A self-serve home for your customers' accounts
Somewhere your customers can check status, manage billing, and find answers themselves - so your support team isn't the only channel for routine account questions.
What customers stop emailing you about
Billing, usage, and settings your customers can handle without a support ticket. These are the emails that turn into a page instead:
Every open order shows where it is, with the courier and the date.
Every invoice, paid or due, downloadable as the GST copy.
The balance and what is overdue, with a Pay now that settles it.
Price lists, agreements and certificates in one Documents tab.
The ticket, its replies and who has it, on the customer's side too.
Done without asking anyone
Interface built around what a customer needs to see, not a repurposed internal tool.
- Track an order and download its delivery proof
- Pay an invoice, or download any past one
- Reorder from a previous order
- Raise a ticket and follow its replies
- Add or remove colleagues on their account
- Update delivery addresses and contacts
Raised from the portal, decided by your team
The request arrives with the account, the order and the history attached - nobody starts by asking for a PO number.
- Raising a credit limit
- Disputing an invoice
- Pricing outside the price list
- Cancelling an order already shipped
- Closing the account
Each customer runs their own team's access
Their admin decides who can order and who can pay. Your support team stops being the place people ask to be added.
Their own sign-in
Google or Microsoft sign-in for most customers, SAML single sign-on for the ones whose IT asks for it, and passwordless email links for the rest.
One company never sees another
Every query is scoped to the signed-in customer's account on the server, not just hidden in the interface.
Every action on record
Sign-ins, downloads, payments and role changes are logged, so a question about who did what has an answer.
Questions we get asked
Built from UI/UX Design and Web Development.
Do we need a portal yet?
Probably, if support tickets are dominated by 'what's my status/balance/plan' questions. Probably not if you have only a handful of customers who'd rather just email you.
Where does the data come from?
Reads live from whatever billing or product data you already run. Your ERP, accounting or CRM stays the source; the portal shows it to the customer it belongs to.
What if our account data is spread across several tools?
Then that is the first job - the portal needs one place to read each customer's orders and invoices from, and connecting those tools comes before the screens.
Can customers pay inside the portal?
Yes. An invoice's Pay now takes them to your payment gateway, and the invoice is marked paid when the payment confirms.
What happens to requests that need a person?
They are raised from the portal like any ticket, with the order or invoice attached, and routed to whoever on your team owns that kind of request.
Who builds it?
The same team behind our UI/UX Design and Web Development work - the customer's screens designed first, then built and connected.
Answering the same account questions every day?
Tell us what your customers ask for and where that data lives - we come back with the portal we would build first.