How to Set Up SIM-Based Mobile Calling for On-the-Go Client Teams

Field-based clients often need to place immediate outbound calls when lead notifications arrive on their mobile devices. When full phone integration is not yet configured on a sub-account, switching between CRM contact details and native phone dialers creates friction and potential dialing errors.

HighLevel solves this initial operational friction through SIM-based mobile calling. This feature allows users to trigger calls through their mobile carrier plan directly from the mobile app with a single tap, bridging the gap during early client onboarding or for light-usage sub-accounts.

Understanding the Operating Rules of SIM-Based Calling

SIM-based calling serves as a fallback mechanism for accounts that do not have active platform phone numbers configured. Understanding how the system routes these calls helps prevent unexpected behavior across client devices.

• Activation requirement: The mobile app automatically defaults to SIM-based dialing only when no active LC Phone or custom telephony integration is active on the sub-account.
• Carrier charges: Calls route through the device's native SIM card, consuming standard mobile carrier minutes and applying standard plan fees.
• Call tracking limitations: Because calls take place on personal cellular networks, automatic call recording, transcriptions, and inbound tracking metrics are unavailable.
• Automatic transition: Once an agency provisions a dedicated phone number within the sub-account, the mobile app automatically upgrades from native SIM dialing to platform-managed routing.

Initiating Native Calls Within the Mobile App

When operating on an unprovisioned sub-account, call icons across the mobile interface automatically trigger the native phone dialer. Users can launch outbound calls from three primary locations within the mobile application interface.

• Contact Profiles: Open any individual contact record to locate the phone icon positioned in the top header action bar.
• Opportunity Cards: Tap a lead inside the pipeline stage view or open the opportunity detail view to reveal the quick-dial button.
• Conversation Threads: Access the quick-action toolbar situated directly above the chat message input window.

Tapping the call icon immediately launches the mobile device's default phone application with the contact's phone number fully pre-populated. The user simply confirms the call on their native screen to establish the connection.

Logging Call Outcomes and Maintaining Activity Records

Because SIM-based calls execute over personal carrier networks, call activity does not automatically sync back to the sub-account timeline. Operators must establish clear logging habits for field personnel to maintain accurate CRM data.

1. Manual Profile Notes: Field staff should return to the contact profile immediately after ending a call to record key details, conversation outcomes, and required follow-ups.
2. Workflow Attribute Logging: Implement automated workflows utilizing the Log External Call action, allowing team members to select standardized call dispositions.
3. Task Scheduling: Utilize manual call workflow actions to automatically schedule structured follow-up call windows for active pipeline leads.

Best Practices for Transitioning to Integrated Telephony

While SIM-based calling offers immediate utility during account setup, it should function primarily as a temporary bridge or specialized feature for specific remote roles.

Agencies scaling client accounts should move toward dedicated telephony infrastructure as accounts mature. Integrated voice setups provide centralized call recording, attribution reporting, inbound routing, and automated multi-channel follow-up triggers that cannot be executed through disconnected cellular lines.