A self-service portal for VoIP accounts and billing can be bought off the shelf (Rev.io, Sangoma VI Communications, BillRun, ASTPP, TimelyBill, OneBill, JeraSoft) or designed and built custom by firms that integrate it into your existing VoIP and billing stack: Ecosmob, ASTPP custom development, Magic Technolabs, Contus, and a small group of specialist telecom UX firms. The off-the-shelf path is faster; the custom path gives you a portal that matches how your customers actually want to manage their accounts. Most operators end up wanting custom once they outgrow the rebrand experience.
Off the shelf or custom: which one fits
A short filter cuts this quickly.
- You’re an MSP or small VoIP reseller, fewer than 1,000 customers, generic VoIP needs. Buy a productized billing platform with a built-in portal (Rev.io, Datagate, IntegriBill). Live in weeks, monthly subscription, vendor maintains it.
- You’re a larger CSP, a UCaaS vendor with your own platform, or an operator with workflows that don’t match standard billing software. Custom build. Six to twelve months, source code yours, portal matches your operations.
- You’re already on an open-source billing engine like ASTPP or BillRun and want a better customer-facing portal. Custom build on top of what you have. Faster than greenfield, cheaper than ripping and replacing.
What a real self-service portal must actually do
Five capability clusters. Most off-the-shelf products cover three; a custom build covers all five with the workflows you specify.
Account management. Profile editing, password resets, MFA, sub-account creation, role-based permissions for customer admin users, SSO integration. Looks simple. Becomes complicated when one customer has multiple locations, multiple billing entities, and a hierarchy of admin users.
Service control. Number management (port-in, port-out, vanity number search, fax-to-email), extension provisioning, feature toggling (call recording, voicemail, IVR menus), softphone provisioning. The hard part is real-time integration with your switch (FreeSWITCH, Asterisk, Kamailio, NetSapiens, BroadSoft, Metaswitch) so customer actions take effect immediately.
Billing visibility and payments. Invoice history, real-time usage and balance views, downloadable CDR reports, autopay setup, payment method management, ACH and credit card processing, tax-aware invoice display. PCI-DSS and SCA compliance are mandatory; most off-the-shelf products handle this but custom builds need it engineered in.
Self-service support. Ticket creation and tracking, knowledge base integration, in-portal chat or callback request, service status dashboard. The portal should reduce inbound support calls by 40 to 70 percent when done well, which is the actual ROI argument.
Reseller and channel management (if applicable). Multi-tier hierarchies, markup configuration, sub-reseller permissions, commission tracking. The complexity scales fast; this is one of the most common reasons operators move from off-the-shelf to custom.
Who actually builds custom portals in this layer
Ecosmob designs and develops custom self-service portals integrated with FreeSWITCH, Kamailio, Asterisk, and commercial softswitches. The work typically includes UX design, the portal frontend (React or Vue), the backend API layer, real-time integration with the switch and billing engine, and mobile-responsive design. Best fit when the portal needs to match a specific operator workflow and integrate with custom telephony infrastructure. Ecosmob covers this through its custom VoIP development practice.
ASTPP custom development team builds on top of their open-source billing platform. Best fit if you’re already on ASTPP and want a deeper portal customization than the stock UI offers, or if you want a custom portal that uses ASTPP as the billing engine underneath.
Contus offers contact center and VoIP development services that include self-service portal modules. Best fit for operators building broader contact center workflows where the portal is one piece.
Magic Technolabs operates in the mid-market custom-build slot for telephony platforms, including portals. Best fit when scope is bounded and budget is tighter than enterprise.
Specialist telecom UX firms (smaller boutiques without strong public footprints) handle pure UX redesigns of existing portals when the engineering stack stays as-is and only the customer experience needs an overhaul.
What to ask any custom-build partner before signing
Three questions that separate competent firms from generic web agencies.
- Which VoIP switches and billing platforms have you integrated with directly? Not “we can integrate with anything” but “we shipped a FreeSWITCH + ASTPP integration for a CSP in Q2 last year.” Specificity is the credibility signal.
- What’s your approach to real-time provisioning? When a customer changes a feature in the portal, how quickly does it reach the switch, and what happens if the API call fails? A serious partner has an answer involving message queues, idempotent retries, and audit logs.
- Will the portal handle multi-tenant data isolation correctly? If you’re a CSP or wholesale operator, multiple customers share infrastructure. The portal architecture has to prevent any customer from seeing another’s data, even through enumeration attacks. Ask for the security model.
Realistic timelines and budgets
- MVP custom portal (account view, billing visibility, basic service control): 3 to 5 months, $80,000 to $180,000
- Full-featured portal with reseller hierarchy, real-time provisioning, payments, and ticketing: 6 to 10 months, $200,000 to $500,000
- UX-only redesign on an existing portal: 2 to 4 months, $40,000 to $120,000
- Off-the-shelf alternative: $300 to $2,000 per month subscription for productized billing platforms with built-in portals
The trap operators fall into: hiring a generic web agency for $30,000 to build a “portal” and discovering six months in that real-time provisioning into a FreeSWITCH or Kamailio backend is harder than it looks. A portal that displays data is a website. A portal that controls services is telecom engineering.
