Two integrations can both connect a CRM to messaging while behaving differently in its inbox and workflow editor.
Inspect the native connection
Miss Blue’s public GoHighLevel guide labels its connection beta and requires project opt-in and a location binding. It describes new direct-message synchronization in both directions.
Existing history and group conversations are not imported by that connection. Verify the actual scope before promising an operator a complete migrated inbox.
Choose the correct workflow action
The guide documents a Custom Webhook path for workflow sends. A standard CRM SMS action does not automatically select the Miss Blue channel.
Treat the destination and authentication as part of the configured action. Use an owned contact to verify the resulting sender and thread in both systems.
Respect media and event limits
The connection documents media restrictions and duplicate handling keyed to CRM message identifiers. Follow those constraints rather than assuming the inbox accepts every attachment mix.
A missing send confirmation is not a reason to blindly post the same customer message again. Inspect the known state or route uncertainty for review.
Define disconnect behavior
Miss Blue’s guide says disconnecting cancels pending sends but does not recall messages already sent. Operators should understand that difference before stopping a live integration.
A CRM implementation platform may offer a different arrangement. Request its exact behavior and acceptance criteria instead of assuming all integrations share this beta channel’s scope.