With this enhancement the IVR Gather action, now contains the branching options "Match condition" for all the Keypress options which the users want to configure in the action.

Earlier the users would have to first configure the IVR Gather step, entering the message which would be played for the caller, based on which they would make a choice by pressing the Key. After this the users would then have to add a separate action, where the users would then map further actions based on the Key press.

This was not very intuitive and took and additional action to be able to achieve the outcome from the IVR gather action itself. With this enhancement we are solving for

We had observed for some carriers the DTMF tone after keypress was not recognised by twillio. As a fix and an enhancement, we have provided a toggle "CONNECT CALL AFTER KEYPRESS".

When enabled (default), we will wait for the agent to press any key to connect the call with the contact. When disabled, we will play the whisper message three times and automatically connect the call. Also we have moved this and DISABLE VOICEMAIL DETECT toggle under advanced settings.

🪄

We have introduced a new design to bill and rebill messaging via LC Phone, we have moved to the static pricing model to avoid any delays on the Telephone System for fetching the info.

We have introduced check on A2P submission to make sure that the sub-account/agency is active along with their wallet balance is not negative.

Previously, email notifications for A2P and Toll-Free registrations were only activated when a sub-account had submitted its A2P. Now, Toll-Free registrations will also trigger the event stream setup, ensuring that agencies receive email notifications for any updates.

🪄

We have introduced support to have multiple A2P Brand and Campaigns in the system which can easily help better optimise your sending capabilities. Salient features involve:

⚙️

📞

A lot of times a new location/sub-account uses multiple cards for testing and filling up the balance to spam the system.

An agency/sub-account can add a maximum of 3 cards in their lifetime with a maximum daily try of 5 times(both success and failure included). In case they want to add a new card they will need to reach out to our support team.

We want any new sub-account to go over a ramp model similar to email warmup we want to implement a messaging ramp-up.

Starting 1st Feb all the sub-accounts created under LC Phone will have an 8-level ramp instead of the 7-day ramp with a lower limit. Below is the table which will give you a detailed idea of the ramp:

We have seen locations sign up and buy a number that does not need a reg bundle or number registration. Then they send out a blast to international numbers.

We will only allow sending messages when the country code of from and to numbers is the same to avoid any international traffic and reduce the risk of fraud.

We sometimes get flagged when our customers send disallowed content messages, we want these messages to not go to Twilio.

We have implemented a model to identify these on our end to avoid the network being affected due to these messages and avoid any impacts on the good messaging campaigns.

The connect call action now supports the ability to add a custom phone number, which earlier was not possible. This would be helpful in case when you don't want to have users in connect call, specifically in cases where the call is getting connected to someone in a different location. Ex: A central store would have the IVR inbound call, and based on the inputs this can be redirected to different stores (sub accounts) IVRs.

With this enhancements users can simply click on the "Add Custom Number" field and add the phone number along with the country code.

We've implemented a subtle yet impactful improvement by displaying the phone number alongside each user, streamlining the configuration process within the IVR. This enhancement is designed to make the setup more intuitive and user-friendly, empowering our users with an enhanced level of control.

To further refine the user experience, we've disabled the selection of users who do not have an associated phone number in the Connect Call action. This ensures that the call forwarding process remains efficient and avoids any potential roadblocks that may arise in the absence of a phone number.

Added the ability to detect whether a call was answered by the user or directed to voicemail. Users can now set up customized workflows based on the voicemail detection condition.

Before the introduction of the Voicemail Detect feature, the users had no way to detect if the call was answered by the agent/user or if it went to their voicemail.

A caller calls to the IVR, the call is transferred to an agent. But the agent did not answer the call, instead it went to their voicemail.

Now with the above feature enabled they can also use Voicemail as an option in Call Status condition and further create actions in the workflow for this condition. (edited)

What do you need to know?

T-Mobile has introduced A2P 10DLC non-compliance fines for messages including prohibited content. If T-Mobile detects any messages that violate the tiers listed below, they will issue a Sev-0 violation (the most severe consumer violation), a non-compliance fine, and carriers will immediately block the offending messages.

This applies to all commercial messaging non-consumer A2P products (SMS or MMS short code, toll-free, and 10DLC) that traverse the T-Mobile network.

Because Sev-0 violations also infringe on HighLevel acceptable use and messaging policies, HighLevel will pass on these fines to you for every Sev-0 violation, starting February 15, 2024. These fines include, but are not limited to, the following:

These non-compliance fines apply to violations across any A2P messaging product (SMS/MMS short code, toll-free, and 10DLC).

T-Mobile reserves the right to permanently suspend any brands, campaigns, and your company’s access to the T-Mobile Network in the event violations are deemed to be excessive. If you are subject to these fines, HighLevel will send you a Sev-0 violation notice and will subsequently charge the respective fine amount.