A Bicom Systems website integration is most valuable when it removes hand-offs between sales, operations and the customer. The goal is a controlled journey in which approved website actions become traceable PBXware tasks without exposing the PBX administration surface.
Choose the right integration boundary
The public website should collect intent and validated customer data. A protected backend should decide whether that request is allowed, map it to the correct tenant or edition-specific operation and communicate with PBXware using the interfaces available in your deployment.
Exact capabilities can differ by PBXware edition and release. Confirm supported methods and permissions in the documentation for your installation before fixing the workflow design.
Turn products into templates
Commercial names such as Business Voice or Contact Centre Starter rarely map one-to-one to a PBX object. Create an internal product template that defines the required tenant, extensions, limits, routes, numbers, features and billing references.
Version these templates. If the plan changes next month, existing customers should not be silently altered simply because the current website configuration is different.
- Validate extension ranges and number ownership.
- Use least-privilege service credentials.
- Store the PBX identifier beside the CRM and billing identifiers.
- Require approval for high-impact changes such as route or trunk updates.
Let's map the integration before complexity grows.
Tell us which platforms need to connect. We'll help turn the workflow into a clear, reliable implementation plan.
Talk to iMingos ↗Design for asynchronous work
A website request may need payment confirmation, number assignment and PBX configuration. Persist those steps and process them in a queue. Return a useful order status to the user instead of holding the browser open while the PBX completes every operation.
Idempotency is essential. Replaying the same event must not create a second tenant or duplicate extensions. Use a stable order key and check for an existing result before creating anything new.
Give operations a control surface
Automation without visibility creates harder support work. Provide an internal view of pending, completed and failed operations, with timestamps and safe retry controls. Record who requested a change and which system completed it.
Begin with one narrow workflow—such as approved extension creation—measure failures, and expand only after the team trusts the audit trail and recovery process.
Frequently asked questions
Can customers create PBX users directly from a website?
They can submit an authenticated request that a protected backend validates and provisions. Direct browser-to-PBX administration is not recommended.
Can the integration support multiple tenants?
Yes, if tenant mapping, permissions and product rules are explicit. The precise implementation depends on the PBXware deployment and supported interfaces.
What data should be synchronized with the CRM?
Usually the customer, tenant or account identifier, service status, selected plan, assigned resources and actionable provisioning errors—not secrets.