3CX Telephony
Connect your 3CX phone system seamlessly with your ERP and boost communication efficiency
ContactTelephony Meets ERP
The 3CX integration connects your phone system directly with Nuxbe. Incoming calls are automatically recognized and matched to the corresponding contact, giving your team instant access to all relevant customer data.
Outgoing calls can be initiated with a single click from the contact view or any other area where a phone number is stored. This saves time and eliminates errors from manual number entry.
Click-to-Call from ERP
Start phone calls with a single click directly from contacts, orders, or tickets. The 3CX integration automatically detects phone numbers and establishes the connection without requiring manual dialing.
Automatic Call Logging
All incoming and outgoing calls are automatically logged and assigned to the respective contact. This creates a complete communication history that is always available to your team as a reference.
Caller Identification with Customer Data
When a call comes in, customer data is displayed immediately: name, company, open orders, and recent interactions. Your team can greet callers personally and work in the right context from the start.
What actually happens on a call
The call that is already matched
When the phone rings, 3CX looks the number up in Nuxbe and puts the name on the display before anyone picks up. If the number is unknown, Nuxbe can create a new address instead of letting the call end as an anonymous line.
A call log with no follow-up work
Every answered, missed and outgoing call is recorded on the contact with extension, direction and duration. If 3CX reports the same call twice, Nuxbe recognises it and does not create a second entry.
Recordings and transcripts
Where 3CX archives call recordings to a directory, Nuxbe collects them hourly and attaches them to the matching call. With the AI package installed, a transcript is produced from them. The audio can then expire after a defined retention period while the text stays on the contact.
One file uploaded, one mapping done
In the settings an administrator downloads the prepared integration file and loads it into the 3CX admin console under CRM integrations. The file carries this instance's access token; downloading it again invalidates the previous one.
Then extensions are mapped to users. That mapping is what later attributes a call to the right employee, and it is the only maintenance work that remains.
For recordings, add a path Nuxbe can read the files from, a tolerance in seconds for matching, and a retention period. Transcription additionally needs a locally hosted AI connection.
Requirements
- A 3CX installation with access to the CRM integrations
- Extensions mapped to Nuxbe users
- For recordings, a directory Nuxbe is allowed to read
- For transcripts, the AI package and a local AI connection
Where the integration stops
Nuxbe listens and logs, it does not drive the phone system. Placing, transferring or hanging up a call from the ERP is not in scope, and neither are presence, video or messaging over 3CX.
Recordings arrive over the file system, not over an interface, so 3CX has to write them into a directory the server can reach. Matching happens on extension and end time within the configured tolerance; anything that cannot be matched unambiguously is set aside rather than guessed.
Transcription runs exclusively on a locally hosted AI. Connections to cloud providers are deliberately refused for this purpose, because call recordings are personal data.
All packages included
All premium packages are included in the Nuxbe license. Contact us for more information.
Contact