Software integration

Third-party integrations

Connect your CRM, productivity tools, and industry hardware to your phone system.

Third-party integrations connect your Voxbi phone system to the business tools your team already uses every day. Rather than treating your phone system as a separate island, integrations let call data flow into your CRM, let your presence status reflect your calendar, and let your colleagues reach you through whatever communication platform your organisation runs on. The phone system becomes part of your workflow instead of a step outside it.

Voxbi connects to a range of business and productivity tools across two categories: deep integrations that exchange live data in both directions, and lighter connections that handle a specific task such as caller identification or calendar syncing. The approach is built on open APIs and webhooks, which means that if a connection you need is not yet in the library, the underlying platform is designed to support it.

When you'd use third-party integrations

  • A Microsoft 365 organisation that wants to make and receive calls inside Microsoft Teams, with full PBX features available through the Teams interface rather than a separate application.

  • A company running Odoo as its CRM: the Voxbi and Odoo integration logs every call automatically against the customer record, enables click to dial from Odoo, and shows caller information from Odoo on incoming calls.

  • A healthcare or facilities team using specialist software for alarm management, nurse call systems, or access control: Voxbi integrates with several sector-specific systems to bring telephony into those workflows.

How third-party integrations work in Voxbi

  1. Browse and select an integration

    The Voxbi Cockpit's Integrations section lists all available connections. Each one shows its category (productivity, business, healthcare) and current status. You can also browse the full integrations directory on the website to see detailed pages for each supported tool.

  2. Configure the connection

    Each integration has its own setup flow. For Microsoft 365, you grant admin consent to allow Voxbi to sync users, contacts, and presence. For Odoo, you provide the instance address, database name, and an API key. The Cockpit guides you through the required steps.

  3. Monitor the integration status

    Once connected, the integration shows a live status badge: connected, queued for installation, error, or not granted. If a connection drops or permissions lapse, the status makes it visible so you can act before it affects your team.

  4. Extend further with APIs and webhooks

    For systems not covered by a named integration, the Voxbi API and webhooks let you build a custom connection. Developer documentation lives at docs.voxbi.com. For bespoke needs, the Voxbi team is available to support integration development.

To browse every supported integration, see setup guides, and find the right connection for your tools, visit the integrations directory on the website.

Frequently asked questions

Which integrations are available today?

Voxbi supports connections with Microsoft Teams (via Direct Routing), Microsoft 365 calendar and contacts, and Odoo CRM, along with a range of specialist integrations for healthcare and facilities and other business tools. The full and current list is in the integrations directory on the website.

Does the Microsoft Teams integration require special licensing?

Yes. Using Microsoft Direct Routing requires a Microsoft Phone System license, which can be part of an E5 plan or added to E1 or E3 plans as an add-on. The Voxbi team can advise on licensing requirements during setup.

Can I build my own integration if my tool is not listed?

Yes. Voxbi provides a documented API at docs.voxbi.com and supports webhooks for real-time, event-driven connections. If you have developed an integration and want to share it, the Voxbi team is open to featuring community-built connections.

How do I know if an integration is working correctly?

Each integration in the Voxbi Cockpit displays a real-time status badge. A connected badge confirms the link is active. If the badge shows an error or a not-granted state, the detail view for that integration explains what needs attention, typically a permission that has lapsed or a configuration field that needs updating.

See Voxbi in your business.

Talk to us or to a certified Voxbi partner.