Phone System

Allow Default Outbound Phone Number Selection for Each User and Automation
Currently, GoHighLevel does not provide a simple way to permanently assign a preferred outbound phone number for manual calls while ensuring consistent number usage across automations. We manage multiple purchased phone numbers, and each number needs to be used consistently for specific users and campaigns. Current Workaround: We create dedicated users and assign specific phone numbers to them. This helps ensure automated SMS messages and calls use the intended numbers. However, when our team makes manual outbound calls, they still have to select the correct phone number from the dialer every time. This becomes time-consuming and increases the risk of calling customers from the wrong number, especially when managing multiple numbers. Requested Feature: Introduce a Default Outbound Number setting that allows us to: Assign any purchased phone number as the default outbound caller ID for a specific user. Optionally create a custom variable or number profile that can be referenced in workflows and automations. Automatically use the assigned number for manual outbound calls without requiring agents to select it each time. Allow agents to override the default number when necessary. Maintain consistent caller ID across manual calls, automated calls, and SMS communications. Expected Outcome: Once an administrator assigns a default outbound number, the agent can simply click Call, and GoHighLevel automatically uses the correct number. This would eliminate unnecessary manual selections, reduce mistakes, and make the phone system significantly more efficient for teams managing multiple phone numbers.
1
·
New Feature
Allow Power Dialer to Call All Phone Numbers for Each Contact
Currently, GoHighLevel's Power Dialer calls only the primary phone number associated with a contact. After that call, it moves to the next contact, even when the call results in a Wrong Number, disconnected number, or another outcome that requires trying a different number. This creates a problem for businesses that store multiple phone numbers for each contact. For example, a contact may have five phone numbers, but the dialer moves on after attempting only the first one. It would be extremely helpful to have an option to dial all available phone numbers for each contact sequentially before moving to the next contact. Suggested functionality: • Allow the Power Dialer to call the primary number and all additional phone numbers stored on the same contact. • Let users configure the dialing behavior based on call disposition. • If a number is marked as Wrong Number, automatically proceed to the next available number. • Allow users to configure whether No Answer, Busy, or Failed Call should trigger another attempt. • If a successful connection is made, stop dialing the remaining numbers when appropriate. • Keep call logs and dispositions associated with the correct phone number and original contact. For example, if Contact A has five phone numbers, the dialer should attempt the next number based on the selected disposition and continue until the configured dialing rules are satisfied. Only then should it move to Contact B. This could be implemented as an optional setting: "Dial all phone numbers for each contact before moving to the next contact." This feature would reduce manual work, improve calling efficiency, and make the Power Dialer much more useful for sales teams, appointment setters, and businesses managing large contact lists. Please consider adding sequential multi-number dialing to the native GoHighLevel Power Dialer.
0
·
New Feature
Load More
→