Support
Most problems have a known cause, so start with the page that matches your symptom — you will usually get an answer faster than a support round trip.
Start here
Sign-in, apps, numbers, messages not sending, the AI agent not replying.
Failed deliveries, retries, and how to replay them.
Every connection error the integration returns, and the fix for each.
Connection status meanings, authorization failures, and threads not syncing.
Before anything else, check your Mac agent is online — the green indicator on your dashboard. An offline agent is the single most common cause of “messages stopped working”, and it produces confusing symptoms: outbound calls are accepted and nothing is delivered.
Contact MessageBlue
support@messageblue.ai — for account, billing, and anything you could not resolve above.
app.messageblue.ai — your apps, numbers, agent and usage.
Try a real, signed API request against your own app.
What to include
A ticket with these lands on the right person immediately; one without them costs a round trip before anyone can even look:
Your App ID
From Settings → API & secrets. It identifies which app to look at, and it is safe to share.
What you expected, and what happened
Including the exact error text or code if there was one. Screenshots of the error are useful; screenshots of a whole screen usually are not.
Never send a secret. Support never needs your App Secret, Zapier secret, webhook signing secret, or any HubSpot credential. Sharing one means it has to be regenerated, which breaks every live integration using it. Your App ID and Portal ID are identifiers, not credentials — those are fine to send.
Reporting a documentation problem
If a page here is wrong, out of date, or missing the thing you needed, say so in the same email and include the page URL. That includes the API reference and the SDKs — both are generated from one specification, so a mismatch between them is a real bug worth reporting rather than something to work around.