Consider the modest drama of calling a small business at five minutes past closing. The person who can help has gone home. Someone else is still working, but their number is elsewhere. The caller hears a greeting, presses a button and waits. A company can spend months finding customers, then leave their arrival to a badly arranged telephone menu.
PBXPlus by 500apps tried to make that arrangement editable. It put the business phone system in the cloud, with a visual builder for deciding where calls should go. Its larger wager was commercial: the phone system would live inside a subscription containing dozens of other business tools.
- The product: visual call routing, IVR menus, forwarding and voicemail.
- The bargain: historically advertised at $14.99 per user monthly, with suite access.
- The turn: 500apps now announces a wind-down and a shift to 500agents.
A phone system you could draw
The public launch announcement arrived on October 1, 2019. Manohar Chapalamadugu, identified as PBXPlus CEO and founder of 500apps and Agile CRM, described a familiar irritation: traditional phone systems were costly and complicated. His team’s answer was centralized control of phone numbers and automated menus, operated from the cloud.
The product’s useful detail was its canvas. A business could drag nodes into a call flow, connect them and specify what happened next. Business hours became a decision. A menu became a branching point. Forwarding and voicemail became destinations. That gave an administrator a picture of a process that callers otherwise experienced one recorded instruction at a time.
Its feature pages described multiple IVR trees, time-zone-specific working hours and uploaded audio for callers waiting on hold. These are ordinary ingredients of business telephony. Putting them together visibly was the point: an owner could review the route before asking a customer to travel it.
Keep the carrier, connect the record
A second announcement, issued the same day as the launch, explained another practical choice. PBXPlus integrated with Plivo, allowing customers already using that carrier to keep it. The company argued that retaining the carrier could reduce the cost of implementing a business phone system. Moving the routing controls did not have to mean replacing every underlying relationship.
The distinction matters. A carrier supplies communications infrastructure; the PBX organizes how business calls reach people. PBXPlus’s historical materials also listed Twilio. The attraction was flexibility around the service beneath the interface, rather than a requirement to buy every component from the same supplier.
Above that infrastructure sat customer information. The integration catalog listed Agile CRM, Salesforce, HubSpot and Zoho CRM, among others. Agile’s own page described combining calling with customer details and observing how callers navigated the phone system. For sales and service teams, the intended benefit was straightforward: start the conversation with some context already available.
The arithmetic of 50 apps
PBXPlus competed in a recognizable market. Its launch release named RingCentral, Nextiva and 8x8 among the alternatives. Automated menus and forwarding were familiar capabilities. The more distinctive proposition appeared on the invoice: PBXPlus belonged to the 500apps Infinity suite.
In September 2021, 500apps announced a suite of more than 30 applications at $14.99 per user per month. The catalog stretched across CRM, project management, recruitment, marketing and customer support. Later PBXPlus materials advertised access to 50 apps. The company was selling a wider answer to the small-business software shopping list.
The arithmetic was easy to understand. The practical value depended on how many of those applications a team could use well. A bundle can simplify purchasing, but it still leaves configuration, training and daily administration. Fifty available apps do not automatically remove fifty pieces of work.
For a small business choosing its first tools, the package could reduce the number of separate buying decisions. For a team already committed to other software, much of the catalog might go unused. This was the bundle’s central tradeoff: its appeal depended on the fit between a company’s actual tasks and the collection offered in the subscription.
What the breadth left unresolved
The customer evidence contains a small, revealing tension. In a May 2023 G2 review, Caitlin W. praised the ease of creating extensions and changing routing through the web interface. A different reviewer, posting in December 2024 and updating in February 2025, reported integration and service problems. Those accounts describe individual experiences; they cannot establish a product-wide failure sequence.
The parent’s current notice supplies its own explanation for changing direction. It says the team had spread its effort across too many products and is moving toward 500agents, a conversational AI platform. PBXPlus’s homepage now redirects there. The old promise of breadth has given way to a pitch for a more unified workflow.
“stop spreading thin across 50 products”500apps customer notice
The notice outlines continued support during a transition, assisted data exports and a 90-day sunset schedule. It is undated, so those intervals are not a calendar deadline. For someone evaluating PBXPlus today, the transition changes the decision: historical features and prices belong beside the vendor’s present direction.
A route worth copying
The enduring idea is useful even outside this product. Draw the incoming call. Name the person responsible at each destination. Test the closed-office branch and the unanswered extension. Connect the customer record where it helps. PBXPlus made these tasks visible, and visibility gave a small team something concrete to improve.
A team can apply the same discipline when changing providers. List the numbers it depends on, the routing rules it needs to reproduce and the records it must retain. Then test the replacement with realistic calls. The visual diagram is useful precisely because it can become a description of the business’s needs, rather than knowledge held by one administrator.
That approach requires maintained rules, working connectivity and people available to receive calls. It also requires a supplier whose plans fit the customer’s needs. An elegant call tree cannot compensate for an unattended destination. The customer who calls five minutes after closing still needs somewhere sensible to land.