We are excited to share some exciting updates and new features added to the Ringotel apps and platform over the past few weeks.

Screen capture prevention

The latest Windows desktop app now has a screen capture prevention mechanism. It can only be enabled via the admin panel (the changes require a restart of the app to take effect).

If this option is enabled, users will not be able to take screenshots of Softphone app content (currently only supported on Windows devices).

Mute outgoing team messages in shared SMS chats

An option has been implemented that disables notifications about outgoing SMS messages sent by other team members in shared chats. To enable it, in the Ringotel admin panel, open the user menu > Settings > enable the option "Mute outgoing team messages in SMS chats".

This option will be added to the app's settings in future versions. It is designed to reduce distractions when working in multiple shared SMS chats.

Screen Pop-ups on incoming calls with enabled integration

If CRM or cloud contacts integration is enabled, you can specify the integration ID in the screen pop-up settings in the Ringotel admin portal to enable automatic opening of a contact's profile during an incoming call (or after answering an incoming call) if their phone number matches the records in the CRM.

To enble screen pop-ups for integrations, navigate to an organisation > connection Features settings > Screen Pop-ups > in the "Screen pop-up URL/Path" field, specify integration ID (e.g. HubSpot), then click Save changes.

Tip: You can find the integration ID in the settings of a specific integration or by going to Menu > Integrations.

New Integrations

We've added the following CRM integrations so you can sync your users' data with the tools they use.

• Creatio CRM
• ERPNext
• Freshsales

Additionally, the following changes and improvements have been made to existing integrations.

• Added "address" field to Wealthbox, Freshdesk, GoHighLevel. This allows you to synchronize the contact address with the mentioned CRM systems when creating or editing a contact.
• Pipedrive: All created call activities are automatically set to “Done” when the call is completed, so there’s no need to manually change the status. The default call activity subject has also been changed to show more details about the call. You can find more details about this change in our news center.

For Developers

Webhook integration: New "CreateActivity" method

We've added a new "CreateActivity" method to the Webhook integration, so you can now use it to collect call data immediately after a user or other party picks up the phone and the call is connected. You can find more details in our documentation.

Zapier integration example

Don't see the integration you need right now? Learn how to set up Zapier workflows with Ringotel here. With the Ringotel Webhook integration, you can create simple Zaps to transfer data from Ringotel to Zapier-supported apps!

Changes to Voip.ms integration

Due to recent changes in Voip.ms handling of messages longer than 160 characters, we have implemented conditional use of the MMS endpoint as per the operator's documentation. Please note that if users send a message longer than 160 characters, it will be sent as an MMS message.

API: New methods

We've added the following methods to the Admin API to help you control your use of AI Assistant:

getAIUsageInfo: Returns data about AI Assistant usage by each user in the organization for the specified time range.

{
    "method": "getAIUsageInfo",
    "params": {
        "domain": "companyabcd",
        "begin": 1760828400000,
        "end": 1763510399000
    }    
}

getAccountStatistics: Returns data about AI Assistant usage in each organization for the specified time period.

{
    "method": "getAccountStatistics",
    "params": {
        "begin": 1760828400000,
        "end": 1763510399000
    }
}

Pass custom data in the “initCall” requests.

You can now pass custom data in the "initCall" API request and then receive that data in subsequent notifications to your webhook URL specified in your webhook integration settings, so you can easily map webhooks to your internal data (such as company ID, module ID, and user ID). This improvement should simplify integration, reduce database lookups, and make webhook processing more robust.

For example:

"initCall" request

{
    "method": "initCall",
    "params":{
        "from":"511",
        "tonumber": "0851344344",
        "toname": "Test",
        "orgid": "17629027527954336546",
        "custom_data": {
            "param1": "testValue1",
            "param2": "testValue2"
        }
    }
}

"StopCallActivity" notification to the Webhook

{   
    "method": "StopCallActivity",
    "api_token": "",   
    "params": {     
        "call_end": 1762903208319,
        "extension": "511",     
        "user_id": "17629028023247184684",     
        "activity_type": "outbound",     
        "call_cause": "0",     
        "call_start": 1762903182412,     
        "called_number": "0851344344",     
        "caller_number": "511",     
        "call_duration": 19,     
        "call_id": "1762903182412-ffe4731537a8a93de8"   
    },   
    "custom_data": {     
        "param1": "testValue1",     
        "param2": "testValue2"   
    } 
}

"UpdateCallRecording" notification

{   
    "method": "UpdateCallRecording",   
    "api_token": "",   
    "params": {     
        "call_recording_url": "https://uk.ringotel.co/public/DLA35vQKGC....AJKEqkB4nHybsEIF8.wav",     
        "call_id": "1762903182412-ffe4731537a8a93de8"   
    },   
    "custom_data": {     
        "param1": "testValue1",     
        "param2": "testValue2"   
    } 
}

We hope you'll find these udpates helpful. As always, we happy to hear from you should have any questions or feedback!