Quick Start Guide: Setting Up myCRMSIM

Welcome to myCRMSIM! This guide will walk you through the initial setup.
There are two ways to get started:
Path A – Connect a Third-Party CRM Use myCRMSIM with platforms such as HighLevel, HubSpot, Salesforce, Zapier, Make, and more.
Path B – Create a Custom Workspace Use myCRMSIM without any external CRM by creating your own workspace.
Both setup paths begin by connecting your devices.

myCRMSIM Quick Start Guide: Set Up & Send Your First Message

Prerequisites
Before starting the tests, make sure you have:
  • An active myCRMSIM Account.
  • An active HighLevel (HL) Account.
Step 1: Add Your Devices

  1. Go to Devices from the left sidebar.
  2. Select the device type you want to connect:
    • Android (SMS)
    • iMessage
    • WhatsApp
    • RCS
  3. Click Add Device.
  4. Follow the setup instructions for your selected device.
Device Setup Guides
Path A – Create a Custom Workspace
Use this option if you are not connecting HighLevel, HubSpot, or another CRM.
Step A1: Create a Workspace
  1. Go to Manage Workspaces.
  2. Click Add New Workspace.
  3. Complete the required information:
    • Workspace Name
    • Address
    • Email
    • Phone Number
    • Time Zone
    • Webhook URL (Optional)
  4. Click Create Workspace.
Step A2: Activate Your Workspace
  1. Go to Subaccount SIM → Connect Locations.
  2. Enable your workspace.
  3. Refresh the page.
Your workspace is now ready to use.
Step A3: Assign Devices
Go to Subaccount SIM → Manage SIM.
Assign:
  • SMS device
  • iMessage device
  • WhatsApp device
  • RCS device
Step A4: Configure Message Routing
  1. Click the Message Routing icon.
  2. Arrange your preferred messaging priority.
  3. Click Save.
Guide: Custom Workspace & Webhook Integration Guide
Path B – Connect a Third-Party CRM
Step B1: Connect Your CRM
  1. Open Integrations.
  2. Select your preferred platform.
  3. Click Connect and complete the authorization process.
Step B2: Connect Your Locations
  1. Go to Subaccount SIM.
  2. Open Connect Locations.
  3. Enable the locations you want to connect.
  4. Refresh the page.
Your connected locations will now appear in the left sidebar.
Step B3: Assign Devices
Go to Subaccount SIM → Manage SIM.
Assign your devices:
  • SMS: Select a SIM from the dropdown.
  • iMessage, WhatsApp & RCS: Click the + button under the appropriate column.
Step B4: Configure Message Routing
  1. Click the Message Routing (⚙️) icon.
  2. Configure your preferred priority order.
Example:
  • Primary – SMS
  • Fallback 1 – iMessage
  • Fallback 2 – WhatsApp
You can arrange the priority order however you prefer. If one channel fails, myCRMSIM automatically tries the next configured fallback.
Click Save.
Guide: Configure Message Routing
HighLevel Setup
Step 2: Start Using Your Workspace
Related Guides
Once your workspace is active, you can access all myCRMSIM features:
  • 👥 Contacts
  • 💬 Conversations
  • 📊 Pipelines
  • ✅ Tasks
  • 📥 Lead Capture
  • ⚡ Automations
  • 🤖 AI Dashboard
To send messages from HighLevel using your connected myCRMSIM devices:
  1. Log in to your HighLevel sub-account.
  2. Go to Settings → Phone Numbers → Additional Settings.
  3. Under Custom Provider, select:
    • SMS, WhatsApp & iMessage Gateway
    • or iMessage Gateway (for iMessage-only users)
  4. Click Save.
Note: When sending messages from HighLevel Conversations, use SMS as the message type. myCRMSIM will automatically route the message based on your configured Message Routing settings.
Step 3: Messages Test
(A) First Outbound Message Test
The outbound test confirms that a message can be sent successfully from HighLevel through myCRMSIM to the recipient.
Test Steps
  1. Open the correct HighLevel subaccount/location.
  2. Open a test contact.
  3. Open the contact's conversation.
  4. Send a short test message, for example:
    This is a myCRMSIM outbound test message. Please reply with "Received".
  5. Confirm that the message appears in the HighLevel conversation.
  6. Check the myCRMSIM Messages Log and confirm the message status.
  7. Confirm that the recipient received the message.
  8. Record the test result.
Expected Result
  • The message is sent successfully from HighLevel.
  • The message appears in myCRMSIM.
  • The correct device/channel processes the message.
  • The recipient receives the message.
  • The message appears as Sent in the CRM.

Do not continue until the outbound test passes.

      (B) First Inbound Reply Test
      The inbound test confirms that the recipient's reply is received by the connected device and synchronized back to HighLevel.
      Test Steps
      1. From the recipient's phone, reply to the outbound test message.
      2. Use a short reply, for example:
        Received. This is the inbound test.
      3. Confirm that the reply reaches the connected device.
      4. Allow time for myCRMSIM to synchronize the message.
      5. Check the myCRMSIM Messages Log.
      6. Open the contact conversation in HighLevel.
      7. Confirm that the reply appears in the correct conversation.
      8. Record the test result.
      Expected Result
      • The reply reaches the connected device.
      • The reply is detected and synchronized by myCRMSIM.
      • The reply appears in the correct HighLevel conversation.
      • The sender and recipient information are correct.
      Do not proceed to go-live if outbound messages work but inbound replies do not synchronize.
      (C) Message Routing Test
      The routing test confirms that messages follow the configured Message Routing order. See Configure Message Routing for the full setup guide.


      1.Open myCRMSIM Dashboard → Subaccount SIM and open Message Routing for the test subaccount.
      2.Confirm the primary channel, fallback row order, and any channels configured in the same row.
      3.Remember: different rows are sequential fallbacks; channels in the same row may be attempted simultaneously.
      4.Send one message from HighLevel using a test contact.
      5.Confirm that it uses the primary channel and appears in the HighLevel conversation.
      6.Record the channel, device, and timestamp.
      If a different device or channel is used, check the “Send From” Device Selection in HighLevel guide, user-specific device/SIM assignments, Multi-SIM Override settings, the logged-in user, the routing configuration, and the HighLevel sending method.
      (D) Fallback Test
      The fallback test confirms that myCRMSIM uses the next routing row when the primary channel cannot send the message.
      Important: Use an internal test contact only. Do not interrupt live customer messaging.
      1. Open Message Routing and record the current primary and fallback configuration.
      2. Temporarily make the primary test channel unavailable.
      3. Send one test message from HighLevel and check its status in myCRMSIM.
      4. Confirm that the next routing row is attempted and that the recipient receives the message through the fallback channel.
      5. Confirm that the message appears in the HighLevel conversation.
      6. Restore the primary channel and the original routing configuration.
      7. Save the configuration and send one final test message.

      Expected Result

      If the primary channel succeeds, the fallback channel is not used. If the primary channel fails, myCRMSIM attempts the next routing row. Channels configured in the same row may be attempted simultaneously.

      iMessage Note

      When Send as SMS is enabled on the iPhone, iMessage has a built-in SMS fallback. Do not add SMS as a separate fallback row for the same iMessage path, as this may cause duplicate or unexpected routing behavior.
      ✅ Go-Live Checklist
      Before starting live messaging, confirm that:
      • myCRMSIM Account is active.
      • HighLevel Account is active.
      • HighLevel subaccount/location is connected.
      • Outbound message test passed.
      • Inbound reply test passed.
      • Message Routing was tested successfully.
      • Fallback behavior was tested successfully.
      • Correct devices/channels are being used.
      • The final Message Routing configuration is saved.
      • The primary channel is working after restoring the test configuration.
      • No unexpected duplicate messages were received.
      Go live only after all applicable tests have passed.

      Related Article

       

      Was this article helpful?

      0 out of 0 liked this article

      Still need help? Message Us