The Aura Business customer self-service portal is your customer's own branded login: where their order has reached, their invoices and documents, their contracts and outstanding, and a form to raise a service request without ringing anyone.
A customer self-service portal is a login for the people who buy from you. Instead of calling your office to ask where the order is, whether the invoice copy can be sent again, when the contract expires or how much is outstanding, they open the portal and read it for themselves.
In Aura Business the portal sits on the same records your team works in. An order status shown to the customer is the sales order your despatch team updated. A document in their vault is the invoice your billing desk raised. A service request they submit becomes a ticket in your helpdesk queue with the asset attached.
The point is not that customers enjoy portals. Most will still call sometimes. The point is that the routine questions, which are the majority, stop reaching a person who was doing something else.
None of these questions need judgement. All of them need somebody to stop working and look something up.
Asked three times by three people at the same hospital, answered three times by three people in your office.
Someone digs through email or a folder for a PDF that was issued weeks ago.
The accounts team prepares a statement by hand because the customer wants the current position.
A question that should take a second takes a call to the service desk and a look at a spreadsheet.
A breakdown reported on a personal WhatsApp number never becomes a ticket, so the SLA clock never starts.
Test certificates, delivery challans and contract copies are re-sent every time a staff member changes at the customer.
You enable portal access for a customer and their named contacts from the customer account.
They sign in to a portal carrying your logo and colours, not a generic software brand.
Orders, despatches, invoices, receipts, outstanding, contracts and assets, restricted to that customer.
A service request or quote request is submitted with the asset or product selected.
The request becomes a ticket or an enquiry with an owner, a status workflow and an SLA timer.
Status updates and the closed job are visible to them without anyone sending an update.
Workflow: He logs in, sees the order marked despatched with the challan attached, and stops calling your sales coordinator every afternoon.
Result: One fewer standing interruption in the working day.
Workflow: They open the portal at month end and match invoices and receipts against their own ledger.
Result: Statement requests drop and disputes are raised against documents both sides can see.
Workflow: The biomedical engineer submits a service request from the portal against the specific asset, and the SLA clock starts at submission.
Result: Response time is measured from the real moment the customer asked.
Workflow: When the customer's purchase officer changes, you add the new contact to portal access and the entire document history is already there.
Result: Nobody re-sends two years of paperwork.
Stores, biomedical and accounts all ask different questions.
Partners order and track without phoning the head office.
Customers log calls and check coverage themselves.
Plant buyers who need documents for their own audits.
Teams where every enquiry lands on the owner's phone.
Problem: A distribution business run entirely on WhatsApp and Excel.
Built: Field app, manager dashboard, GST billing and payment tracking.
Stack: React Native, Supabase, WordPress.
Problem: No online store or way to manage distributors.
Built: Storefront, distributor portal, quote-to-order and 253 SEO pages.
Stack: Supabase, JavaScript, Playwright.
Yours. Branded login, your logo and colours on the portal, dashboard, mobile app and invoices are part of setup, so the customer experiences it as your system.
No. Access is role-based and scoped to that customer's own records. Costs, margins, supplier prices and internal ticket notes are not exposed in the portal.
They are related modules in the same suite. The self-service portal is for end customers checking their own account, while the distributor portal lets partners place B2B orders and submit payment UTR details.
It enters the helpdesk as a ticket with the asset and contract attached, follows the status workflow, and runs against the SLA timers defined for that customer. See helpdesk ticketing.
Institutional buyers with their own audit needs usually do, because the documents they chase are in one place. Expect calls to fall rather than stop, which is still a real saving for a small office.
Plans are priced by module tier with unlimited users, so portal access does not add a per-login charge. The exact scope is settled on a call.
Tell us how you work today. We will show you what the platform would look like for you, and give you a clear scope and timeline.
Founder-led · Chennai, India · Built and supported by the person who wrote it