Decide what the integration should do
Start with one complete workflow: a new inquiry creates an expected message, the recipient replies, and the reply reaches the correct CRM record and team. Decide who owns the next response when a person replies.
Choose the intended Miss Blue organization, project, and sending number before configuring credentials. Use the supported integration for your CRM when one is available, or connect through the public API and webhooks.
Keep credentials on your server
Store API keys in your integration’s secret configuration. Do not put them in a browser widget, a public repository, screenshots, or support messages. Give the integration access to the intended sending numbers and check that an unavailable number produces a clear error.
If you need to troubleshoot with support, share a request ID, approximate time and timezone, and the error code. Those details are useful without exposing the credential.
Test the whole event flow
- Use a sandbox key to create a simulated message from your workflow.
- Record the returned message and conversation identifiers alongside your CRM record.
- Test delivery updates and an inbound reply through your registered test webhook.
- Verify that repeated webhook events do not create duplicate activities or trigger repeated replies.
- Test failed, rate-limited, and timed-out requests before switching to a live key and a consenting test recipient.
Keep automation and people in sync
- Pause automated follow-ups when a member takes over the conversation.
- Prevent your integration from treating its own outbound activity as a new inbound reply.
- Update the external CRM or sequence when a person asks you to stop. A Miss Blue block does not edit the CRM’s preferences.
- Keep a clear route for a person to review errors or unusual replies.
- Check that the workflow still uses the intended project and number after changing team access.