Jania Henderson We'd use the integration to perform Moves, Adds and Changes by adding/removing phones and updating parameters of an extension like changing the name, voicemail PIN, email address, etc. Initiating passwords resets, etc.

Jania Henderson Creating extensions, syncing with 365 and Teams, updating ring groups, provisioning desk phones. Basically any action that we currently can do in the GUI. The 3CX API is massively fleshed out and (pretty much) has feature parity with anything that can be clicked in the GUI

Jania Henderson Updating PSA additions with extension counts for billing, creating users/extensions, adjusting departments, etc.

This would be a big one and a massive pipe dream, but I have played with the API and you can initiate calls from the API, and the calls have transcriptions. I could have a portal where a tech can select a ticket to call on. 3CX calls from that tech to the tickets contact and logs some info about the call, ticket id, time stamp, from who and to who in a queue or SQL table. Then every 30 minutes or so, poll 3CX for completed calls that match the items in the queue, grab that calls AI Summary and append that as an internal ticket note. Now documentation on tickets is generally automated on any ticket called on via that portal.

Jania Henderson Auto transcription and time logging into PSA of calls. Contacts sync for PSAs etc.

Jania Henderson Good idea is to have Voicemail to Text and then post this to a Teams/Slack Channel.

I know there are other ways to do this and not sure if Rewst could but this is one use case we are looking at.

Jania Henderson We would be using it for User Onboardings and Offboardings, as well as what many others have mentioned, updating user extension parameters, password resets and more.

Jania Henderson - Moves, Adds, Queue Management. More importanly though would be ETL for call queue metrics for storage and reporting.