Support

Get Help With Your Workspace

Use the guides for everyday tasks, or contact support with the details of the problem. Include your workspace address, the affected PBX, your time zone and the exact error where available.

  • User guides require sign-in
  • support@synopsysapp.com

Find Your Workspace

Sign in to the console to choose a workspace you belong to. If your workspace requires Microsoft sign-in, follow that method when prompted.

Sign in

Send the Details That Help Us Investigate

Explain what you expected, what happened and when it happened. Never include passwords, sign-in codes or backup codes in your message.

Email support@synopsysapp.com

Privacy Requests

Questions or requests about your personal information go to the privacy contact in the policy.

Read the Privacy Policy

What to Include

Workspace address
The address you sign in at, such as yourcompany.synopsysapp.com.
Affected PBX
The instance name as it appears in the console, and its 3CX version if you know it.
When
Date, time and your time zone, so we can match the server logs.
What you saw
The exact error text or a screenshot with no credentials visible.

Frequently Asked Questions

Which 3CX versions does SYNOP•SYS support?

SYNOP•SYS works with 3CX version 20 through its Configuration API. Settings and actions that exist only from a later update, such as 3CX 20.0.10, are offered only on PBXs running that update.

What access does SYNOP•SYS need to a PBX?

An API client created in the PBX under Integrations → API with the System Owner role (only the Configuration API is required), or a system owner account without two-factor authentication. The PBX must be reachable over HTTPS on its management port; nothing is installed on it. The connection is tested before the instance is saved, and the credentials are encrypted with a key that belongs to your workspace.

Can I review a change before it reaches a PBX?

Yes, the targets and values. Run Bulk Action lists the PBXs and the parameters before anything runs, and actions flagged as destructive ask for confirmation. Applying a template shows the scope, the template and its values first, and saving a template applies nothing. There is no simulated run: each target’s result is recorded once the change is sent.

What happens when a PBX is offline?

Monitoring raises the built-in PBX unreachable alert once the failure is confirmed, and records no new metrics until the PBX answers again: the values on screen are the last ones read. An action sent to it fails and the failure is recorded for that PBX, while the other targets of a bulk run continue. A fleet search lists it as Did Not Respond in Instance Coverage rather than as a PBX with no matches.

Who can see what in a workspace?

Roles decide what a person can do: Owner, Admin and Member come with every workspace, and you can add your own. Access scope decides which PBXs they reach: a member confined to groups or tags sees only those instances across the console. A member with no scope sees every instance their role allows.

How do I get started?

Send the request access form. We review each request and reply by email to discuss access and the plan. If you go ahead, we create your workspace and you receive an email to set your password, then another when the workspace is ready.

Where are the user guides?

In the console, at User Guides in your avatar menu or at console.synopsysapp.com/docs. They require signing in with a workspace account.

How do I report a problem?

Email support@synopsysapp.com with your workspace address, the affected PBX, when it happened (with your time zone) and the exact error or a screenshot with no credentials visible. If your plan includes the Feedback module, you can also send a report from Feedback in the console and follow it under My Feedback.