Hellasfone - Telecom Customer Portals, vPBX and ERP
A connected telecom operations ecosystem spanning WordPress sales journeys, separate Retail and vPBX customer portals, a Go API, and a Laravel ERP back office.
Project overview
Hellasfone - Telecom Customer Portals, vPBX and ERP
A connected telecom operations ecosystem spanning WordPress sales journeys, separate Retail and vPBX customer portals, a Go API, and a Laravel ERP back office.
Hellasfone is not a single website or dashboard. The project connects offer configuration, online ordering, account creation, service provisioning, PBX management, billing and support across several interfaces built for different users.
Retail and Business Retail customer portal
vPBX owner and user portal
Laravel telecom ERP and back office
WordPress pricing and checkout integration
Go REST API and role-aware access
Billing, payments, DID and provisioning workflows
Four interfaces, one operating model
A telecom product from pricing page to live service
Each interface has a distinct job, but the customer, product, number, plan and billing context must remain consistent across the full service lifecycle.
System core
Hellasfone
Customer · product · number · billing
WordPress pricing and checkout
The public layer turns telecom products into guided English and Greek sales journeys instead of static price tables.
- Retail, business and PBX pricing configurations
- New-number or porting choices, plans, minutes and channels
- Checkout hand-off to order and payment processing
Retail and Business Retail portal
A dedicated Next.js portal gives individual and business customers practical control over their telecom account.
- Balances, plans, DIDs and account profile
- Call history, recordings, voicemail and greetings
- Billing history, top-ups, rates and support
vPBX owner and user portal
A separate PBX product protects its own account scope while supporting both company owners and extension users.
- Users, extensions, numbers and scheduled routing
- Autoattendant, queues, call groups and branches
- Recordings, voicemail, faxes, greetings and VoIP devices
Laravel telecom ERP
The internal back office gives the Hellasfone team operational control over customers, products and the commercial processes behind each service.
- Retail, Business Retail, PBX and wholesale accounts
- Product, DID, plan and service assignment
- Orders, invoices, payments, statements and communication templates
Connected workflow
From product choice to daily telecom operations
The implementation keeps the commercial journey and technical service delivery connected without forcing every user into the same interface.
Configure
The customer selects a segment, number path, billing period, plan, minutes, channels and add-ons.
Order
Checkout captures customer and product context and routes the order into payment and onboarding workflows.
Provision
Accounts, DIDs, service schedules, SIP or PBX settings and billing ownership are created in the correct product scope.
Operate
Customers manage services in their portal while staff handle products, billing, support and exceptions in the ERP.
Shared technical foundation
Two product-separated Next.js portals use a shared Go REST API with server-side role and ownership checks. The Laravel back office, WordPress sales layer, telecom databases and external payment and communication services complete the operating environment.
Inside the Hellasfone vPBX portal
Selected product views from the public English PBX documentation show how company-level telecom operations are translated into guided customer workflows. Account-specific values, identifiers and routing names have been anonymized.
The owner dashboard combines service, number, call, voicemail and billing context in one company overview.
PBX plans connect billing periods and prices with the extension capacity available to the company.
The autoattendant editor maps keypad choices to users, call groups and other company call-flow destinations.
User provisioning brings together branch, extension, SIP, caller-ID, routing and voicemail settings.
Hellasfone
Project context and live links
Brief
Hellasfone is not a single website or dashboard. The project connects offer configuration, online ordering, account creation, service provisioning, PBX management, billing and support across several interfaces built for different users.
Result
One operational product ecosystem with dedicated sales, customer self-service and internal-control interfaces, all mapped to the same telecom catalogue, account context and service workflows.
Project links
Visit Hellasfone
Hellasfone's public multilingual telecom offer, pricing and service journeys.
https://hellasfone.grChallenge
Keep plan, DID, channel, minute, billing and renewal rules aligned across the public offer, two customer products and the ERP.
Separate Retail and PBX identities, permissions and data ownership while still using a shared API and telecom infrastructure.
Turn technical SIP, routing, provisioning, media and billing data into usable workflows for customers and operations staff.
Support equivalent English and Greek journeys across purchasing, account management and PBX documentation.
Approach
Product architecture: kept Retail and vPBX as separate Next.js applications with explicit customer-type and role boundaries.
API layer: implemented product-specific Go endpoints with server-derived account scope, ownership validation and bounded operational queries.
Operations: connected account, product, DID, schedule, order, invoice, payment and communication tools in the Laravel ERP.
Sales integration: mapped WordPress pricing and checkout selections to the operational catalogue and onboarding process behind each service.
Outcomes
Customers receive self-service tools suited to either Retail services or a role-aware company PBX.
Operational staff can manage accounts, plans, DIDs, billing and communication from a dedicated back office.
Commercial choices are carried into provisioning and billing workflows instead of ending at a website form.
The modular foundation supports continued development of routing, media, devices, documentation and customer-service workflows.
Project links
Visit Hellasfone
Hellasfone's public multilingual telecom offer, pricing and service journeys.
Open client websiteResult
One operational product ecosystem with dedicated sales, customer self-service and internal-control interfaces, all mapped to the same telecom catalogue, account context and service workflows.
Have a similar project?
We can help shape the technical plan, build the product, and support it after launch.
Let's talk