Client portals that move customer operations online
As customer interactions grow, more staff time goes into sending documents, checking statuses, confirming payments and processing routine requests. We design connected client portals that let customers handle the right interactions themselves, while keeping every action connected to the systems your business already uses.
When customer service starts becoming an operational process
As a company develops, its internal systems and processes become more capable. Yet many routine customer interactions may still depend on staff moving information between the customer and those systems.
- 01
Customers contact staff for information that already exists somewhere in the business.
- 02
Account managers repeatedly send invoices, contracts, certificates or status updates.
- 03
Payments and requests have to be recreated manually in CRM, ERP or accounting software.
- 04
Repeat orders, renewals or bookings still require an employee to coordinate them.
- 05
Customers depend on office hours for routine actions that could happen safely online.
- 06
Customer-facing information and internal operational information live in different places.
The useful question is not simply whether to build a portal. It is which customer interactions can safely become self-service, and what needs to happen inside the business when a customer completes them.
What should actually become self-service?
We start with the existing customer journey and the operational workflow behind it, not with a predetermined list of portal features.
Repeated actions
Which requests and handovers happen often enough to justify a self-service route?
Rules and permissions
Who can perform an action, when is it available, and which exceptions require approval?
Data and calculations
Where does the required information live, and what must be calculated or validated?
Operational response
What record, document, notification or workflow change should follow the customer action?
Connected systems
Which CRM, ERP, accounting, payment or other systems need to read or update the data?
The goal is not to put every process online. It is to remove unnecessary coordination without losing operational control.
Self-service can go further than documents and status updates
For some businesses, customers only need access to information. For others, they need to make payments, renew services, submit requests or complete actions that continue into real operational workflows.
The more an action affects the business behind the portal, the more important the underlying rules, calculations and integrations become.
What customers can handle without involving your team
A portal is not an isolated website account. It is the customer-facing part of a wider operational system.
- 01
Access information
Order, project or service status; account information; balances; history and relevant operational information.
- 02
Access and manage documents
Invoices, contracts, certificates, statements, generated documents, uploads and downloads.
- 03
Complete transactions
Payments, renewals, repeat orders, bookings, subscriptions and other permitted transactions.
- 04
Submit information and requests
Forms, applications, specifications, supporting documents, service requests and customer data updates.
- 05
Complete actions that continue into your operations
A customer action can create or update records, register payments, run calculations, generate documents, start approvals or move work to the next stage.
What connected self-service changes for the business
Less manual administration
Customer actions can create the correct records and transactions directly instead of requiring employees to recreate them manually.
Fewer routine service requests
Customers can access information, documents and available actions without contacting a manager.
Faster customer actions
Eligible payments, renewals, orders or document requests can happen without waiting for staff availability.
More consistent information
Customers and employees work with information connected to the same underlying systems.
Moving real financial operations online
Custom CRM
Extensions and redemptions
Financial and operational logic
Context
Golden Lombard already had a custom CRM managing pledges, financial operations, documents and internal workflows. The next step was to give customers secure self-service access to selected operations while keeping them connected to the existing system.
The challenge
The challenge was to connect online extensions and redemptions directly to the financial and operational logic already managed by the CRM.
What we built
We connected the client portal to the existing CRM and payment infrastructure. Customers can see their pledges and, where the business rules allow it, extend or redeem them online. The portal validates the operation, processes the payment and passes the action into the existing financial and operational workflow.
The difficult part was not adding online payment. It was making sure an online transaction behaved correctly inside the business.
Moving the process online also required the underlying rules and edge cases to be formalised and verified.
Eligibility
Pledge status, overdue position and other conditions determine which actions are available.
Calculations
The system applies the required financial calculations and adjustments before the transaction proceeds.
Partial repayment
A partial principal repayment is reflected correctly in the calculation and subsequent CRM operation.
Multiple items
Where a pledge contains multiple items or related loans, payments can be allocated according to the underlying business logic.
What happens after a customer acts
- 01
Customer action
- 02
Eligibility and calculation
- 03
Online payment
- 04
CRM operation created
- 05
Records and documents updated
- 06
Workflow moves to the next stage
The operational result
Online extensions and redemptions now flow directly into the existing CRM workflow. Once an eligible customer action is validated and paid, the corresponding operation is created, financial records are updated, relevant documents are generated and the workflow continues to the appropriate next stage. This removes the need to recreate online transactions manually inside the CRM.
Read the full Golden Lombard caseThe portal does not need to replace the systems behind it
If an existing system performs its role well, it can remain part of the architecture. We add the missing customer-facing layer, connections and business logic around it.
Improve
Extend the parts of the existing software that already support the business well.
Integrate
Build APIs, webhooks and data synchronisation so customer actions reach the right systems.
Build
Create the missing portal, workflow or business logic where the current ecosystem has a genuine gap.
Could self-service remove repetitive work from your team?
We can look at how customers interact with your team today, which actions could move online, and what would need to happen behind the scenes to make them work reliably.