Fleet management for 3CX

Manage Your 3CX Fleet Without Opening Every PBX

Monitor phone systems, investigate alerts and make repeatable changes from one workspace. SYNOP•SYS brings fleet operations and the users, phones and settings inside each PBX into the same console.

  • Connects through the 3CX API; nothing to install on the PBX
  • Built for MSPs and multi-site IT teams
  • English and French console

What the console covers

  • Fleet inventory, health and licences
  • Alerts, incidents, on-call and escalation
  • Bulk and scheduled actions
  • Configuration templates and drift
  • Fleet-wide search and reports
  • Roles, PBX scopes and the write audit
Fleet overview of a demonstration workspace: 22 PBX instances, health by instance, open alerts and 24-hour availability. Demonstration data. Fleet overview of a demonstration workspace: 22 PBX instances, health by instance, open alerts and 24-hour availability. Demonstration data.
Fleet overview of a demonstration workspace: 22 PBX instances, health by instance, open alerts and 24-hour availability. Demonstration data.Open full imageOpen full image

Three Problems the Console Is Built Around

Each one has a page of its own. The home page shows the shape of the answer; the platform pages show the evidence.

The same change, PBX after PBX

Select users or phones inside one PBX, or several PBXs for a fleet action, choose the operation and read a result per target.

Bulk actions and schedules

An alert nobody owns

Review the condition and its evidence, group related alerts into an incident, and define who is paged when nobody acknowledges.

Monitoring and incident response

Configuration that quietly drifted

Capture the settings you want to repeat, apply them to the right systems and compare expected against observed on a schedule.

Templates and drift

Bulk actions

Stop Repeating the Same Change

Select PBXs in the fleet table and run a batchable action across them, or select users and phones inside one PBX and use the operations available for that selection. Either way you review the targets first and read the recorded result for each one afterwards.

  • Fleet actions: one result per PBX, grouped by batch in Run History
  • Per-instance actions: the selection stays inside that PBX
  • Scheduled actions with ordered stages and rolling batches

See how bulk actions work

Five PBXs selected in the fleet table; the bulk bar offers Run Bulk Action and Move to Group. Five PBXs selected in the fleet table; the bulk bar offers Run Bulk Action and Move to Group.
Five PBXs selected in the fleet table; the bulk bar offers Run Bulk Action and Move to Group.Open full imageOpen full image
Inside one PBX: five users selected, with the operations that apply to that selection. Inside one PBX: five users selected, with the operations that apply to that selection.
Inside one PBX: five users selected, with the operations that apply to that selection.Open full imageOpen full image

Monitoring and response

Give Your Team a Signal to Act On

An unregistered trunk, an unreachable PBX or a stopped service should land in your team’s workflow, not in a customer’s voicemail. Review the alert and its evidence, then coordinate the response through incidents, on-call schedules and escalation policies.

  • Built-in alerts for the common failures; custom policies with the Monitoring module
  • Incidents group related alerts with a timeline, an owner and notes
  • Escalation steps that fire until someone acknowledges

Explore monitoring and response

A critical trunk-registration alert with its lifecycle, SLA status and triggering context. A critical trunk-registration alert with its lifecycle, SLA status and triggering context.
A critical trunk-registration alert with its lifecycle, SLA status and triggering context.Open full imageOpen full image
An incident grouping two SBC alerts, acknowledged and assigned, with a note from the responder. An incident grouping two SBC alerts, acknowledged and assigned, with a note from the responder.
An incident grouping two SBC alerts, acknowledged and assigned, with a note from the responder.Open full imageOpen full image

Templates and drift

Find the Configuration Changes Nobody Noticed

Capture the settings you want to repeat, apply them to selected instances, groups or tags, and let a drift policy compare expected against observed values on a schedule. Unresolved checks stay separate from confirmed results.

  • Templates with variables for the values that change per site
  • Per-instance apply results, including fields a target could not accept
  • Drift verdicts: compliant, drifted, error and indeterminate

Explore templates and drift

Latest drift results for eleven PBXs: compliant, drifted, one error and one indeterminate check. Latest drift results for eleven PBXs: compliant, drifted, one error and one indeterminate check.
Latest drift results for eleven PBXs: compliant, drifted, one error and one indeterminate check.Open full imageOpen full image
Inspect difference: expected and observed values for the fields the template manages. Inspect difference: expected and observed values for the fields the template manages.
Inspect difference: expected and observed values for the fields the template manages.Open full imageOpen full image

Built for the Fleet You Manage

MSPs organise customer systems and assign technicians to the PBXs they support. Internal IT teams group sites, repeat configuration standards and review operations across the organisation.

For MSPs and 3CX Providers

Customer groups and tags, technician access confined to the PBXs they support, repeatable work through templates and chains, and reports you can bring to a customer conversation.

For MSPs and providers

For Multi-Site IT Teams

Every site in one inventory, one configuration standard applied deliberately and checked for drift, and maintenance planned across locations in the time zone you choose.

For multi-site IT teams

How it connects

Through the 3CX API, With Nothing to Install on the PBX

Add a PBX with its API credentials; the connection is tested before the instance is saved. Credentials are encrypted at rest, and available operations depend on the PBX version, its capabilities, your permissions and your plan.

Read the connection guide (sign-in required)

Add Instance with client credentials selected. The connection is tested before the instance is saved. Add Instance with client credentials selected. The connection is tested before the instance is saved.
Add Instance with client credentials selected. The connection is tested before the instance is saved.Open full imageOpen full image

Tell Us About the Fleet You Manage

We review every request and reply by email to discuss access and the plan that fits.