How can we help?
Real humans, fast replies. Pick whatever’s easiest — your leads keep getting answered the whole time.
Live chat
Fastest answers — chat with us right from the widget on this page.
Open chat →Book a call
Prefer to talk it through? Grab a time with our onboarding team.
Schedule a call →Email us
Send details and screenshots and we’ll get right back to you.
Email support →FAQ
Setup, billing, integrations and compliance — answered.
Read the FAQ →Popular help topics
What should I include when I contact support?
Five details get most tickets answered on the first reply instead of after three rounds of questions.
- The account emailThe email you log in with, so we can open the right account before we start reading.
- What you expected to happenOne sentence. "The workflow should have texted the lead after the form fill."
- What happened insteadIncluding the exact error text if there was one — a screenshot of it beats a description of it.
- When it last workedIf it used to work, roughly when it stopped. That usually points straight at the change that broke it.
- One affected contact or conversationA single real example lets us trace the record end to end instead of guessing at the pattern.
Can I check anything myself first?
Four of the most common reports have a cause you can confirm in under a minute. Still stuck after checking? Send it over — that is what support is for.
- Messages are not sendingCheck the A2P 10DLC registration status first. Carriers block unregistered traffic outright, and a pending registration looks identical to a broken workflow from inside the platform.
- A workflow did not fireOpen the contact record and read the automation history on it. It records every trigger that matched and every one that was skipped, with the reason.
- Calls are going to voicemailConfirm the number is assigned to the AI receptionist and that business hours are set for your timezone, not the account default.
- Email is landing in spamVerify SPF, DKIM and DMARC are still passing on your sending domain. These break quietly when DNS is changed for something unrelated.