Among Sphere's projects is a corporate website and customer portal for a regional telecom operator. The task sounds familiar, but there are two different systems behind it. The website tells everyone who visits about the company and its services. The customer portal works with a specific customer's data: their contract, balance, active services and requests.
Below we cover why a regional operator needs both a website and a customer portal, how they differ under the hood, what such a solution usually needs to do, and how we approach customer portal development through our own phases. It will be useful to anyone planning a self-service portal on top of existing internal systems.
Why a regional operator needs a website and a customer portal
A regional operator, whether a telecom company, an internet provider or a utility, has thousands of customers with similar questions. How much do I owe? How do I pay? Why isn't it working? How do I change my plan? If an employee answers every one of these questions, support grows along with the customer base.
A corporate website with a customer portal covers two different jobs:
- The website attracts new customers: it presents services and plans, coverage area and connection options, publishes news and documents, and collects requests. It needs to rank well in search and load quickly on a phone.
- The customer portal serves people who are already customers: it shows the balance and payment history and lets them pay, change plans, submit a request and track its status.
For the operator, that means fewer routine calls and office visits. For the customer, it means solving their issue any time without waiting on hold. A good customer portal takes the most frequent requests off support, so staff can focus on cases that genuinely need a person.
The operator's website: what matters before login
An operator's corporate website is often treated as a wrapper for the "Log in" button. That's a mistake: it's the website that brings in new customers and answers the questions people would otherwise call the office about. For a telecom or other regional operator's website, these usually matter:
- separate service and plan pages for consumers and for businesses, rather than one combined price list;
- an address availability check and a short request form;
- a help section: how to pay, how to set up equipment, what to do during an outage;
- news and notices about scheduled maintenance;
- the documents the operator is required to publish: terms of service, plans, company details.
The website and the portal should be designed together. That way plans have the same names on both, and a connection request lands in the same CRM as requests from existing customers. Local search matters for a regional business too: pages with the names of towns and districts help people find the operator when they search with their address.
How a customer portal differs from a website
From the user's side, the portal looks like just another section of the site. Technically, it's a separate system with its own requirements. The difference is easiest to see side by side:
| Corporate website | Customer portal | |
|---|---|---|
| Who it's for | All visitors, including future customers | Only logged-in customers and staff |
| Data | Public: services, plans, news, documents | Personal: contract, balance, payments, requests |
| Where it comes from | The content management panel | Billing, CRM and other internal systems |
| Main risk | The site doesn't rank and doesn't bring in leads | A data leak or a wrong balance |
Roles and permissions
A portal usually has several roles: an individual customer, a business with several contracts and responsible employees, a support agent, an administrator. Each role has access to its own data and actions. Permissions are designed before development: retrofitting them into a finished system costs more and carries more risk.
Authentication
Login with a contract number and password, by phone with an SMS code, via a national digital ID service, or corporate single sign-on for staff: the choice depends on what information the customer knows and how sensitive the portal's operations are. Account recovery gets separate attention, since it's one of the most common reasons people call support.
Security and personal data
The portal stores and displays personal data, so GDPR and similar data protection laws apply. In practice that means encrypted connections, access control, an activity log, protection against password brute-forcing and regular updates.
A bug on a website spoils the impression. A bug in a customer portal shows someone else's data or the wrong amount owed.
What such a solution usually needs to do
The feature set depends on the operator's services and which processes are already automated. Operators' customer portals most often include:
- balance, charges and payment history with a clear breakdown;
- online payment and autopay;
- active services and plans, changing plans and adding extra options;
- requests and support tickets: creating them, tracking status, messaging with support;
- notifications about outages, scheduled maintenance and low balance;
- documents: contract, invoices, reconciliation statements for businesses;
- profile and contact details management.
We don't aim to do everything in the first version. It makes more sense to launch the portal with the features that remove the most requests, then evolve it based on data: which sections get used, where customers abandon an action, what they still call about.
Mobile web or an app
Most customers open the portal on their phone to quickly check their balance or pay. To start with, a good responsive version is usually enough. A separate app makes sense when you need push notifications and frequent actions, such as managing services daily.
Integrations: a customer portal is an interface to internal systems
On its own, the portal knows almost nothing. The balance lives in billing, contracts and tickets in the CRM, equipment status and outages in network monitoring systems. The development job is to connect them so that customers see live data, not yesterday's export.
Integrating a customer portal with billing and CRM usually comes down to a few questions:
- whether the system has an API, or the data has to be pulled from the database and export files;
- how often data must refresh: in real time, every few minutes or once a day;
- what the portal only reads and what it changes: switching plans or creating a ticket means writing to an internal system with its own rules;
- what to show the customer if an internal system is unavailable;
- who on the operator's side owns each system and can approve changes.
A separate integration layer is often placed between the portal and the internal systems. It hides the quirks of legacy systems from the interface, caches data and makes it possible to replace, say, the billing system without rebuilding the portal.
Load and availability
Load on an operator's portal is uneven. It rises on days of mass billing and payments, and spikes hardest during outages, when customers all log in at once to see what happened. That's exactly when the portal has to work.
So projects like this discuss upfront:
- the expected number of concurrent users on a normal day and at peak;
- load testing on realistic scenarios before launch;
- data caching so a peak doesn't land on the billing system;
- monitoring and alerting the team about failures;
- a status page or outage banner that heads off some requests before people even log in.
How we approach customer portal development
We follow the same phases on every project, but for a portal the emphasis shifts toward data and processes.
- Discovery, structure and messaging. We analyze services and plans, customer types, frequent requests, internal systems and their limitations. We design roles, scenarios and every screen of the website and portal, and document the integration and security requirements.
- Visual identity and design. We present options in different styles and design from scratch. The website and portal are designed as one system, so customers don't feel a jump between the "storefront" and the "account."
- Development and testing. We build the website with a content management panel, the portal and the integration layer. We test access rights, scenarios with real data, behavior when internal systems are down, and performance under load.
- Launch and growth. We migrate users, set up analytics and monitoring, and gather feedback from customers and support. Then we evolve the portal based on data about which features are in demand.
During discovery we separately check how a customer will get from their first visit to the website all the way to paying in the portal. A prototype of that journey exposes logic gaps before development begins: reworking a prototype is cheaper than reworking a finished integration.
What to prepare if you're planning a customer portal
End-to-end customer portal development moves faster when some questions are settled before kickoff. A short list of what to gather:
- a list of internal systems holding customer data and the contacts of their owners;
- API documentation, or a description of how data is exported today;
- support request topics and volumes;
- requirements from the security team and lawyers on personal data and storage;
- a list of features the portal can't launch without, and those that can wait.
Our projects as a web development agency, including corporate websites and internal services, are collected on our portfolio page.
FAQ
How is a customer portal different from a regular website?
A website shows everyone the same information, while a customer portal shows a specific customer's data: contract, balance, services, payments, requests. That's why a portal has authentication, roles and access rights, integrations with internal systems, and higher requirements for security and availability.
Can a customer portal be added to an existing website?
Yes, if the site technically allows it. Often the portal is built as a separate application on a subdomain with shared login and a unified design, while the website stays on its current platform. The decision is made after auditing the website and internal systems.
What should be prepared before customer portal development starts?
A list of the systems that store customer and service data, and contacts for their owners; API documentation, if there is any; a list of frequent support requests; requirements from the security team and lawyers on storing personal data. The sooner this is gathered, the more accurate the estimate.
Can a customer portal be integrated with billing if the billing system has no API?
Usually yes, but it's a separate task: you need an intermediate layer that pulls data from the database, export files or a message queue and serves it to the portal. This option has to be assessed during discovery, because it affects the timeline and how fresh the data will be.
Why should end-to-end customer portal development start with discovery?
The main complexity of a portal isn't the screens but the data and processes behind them: where the balance comes from, how a request is created, who handles it. If that isn't worked out in advance, the interface will have to be rebuilt after the first tests with real systems.




