We've got your back. Try a quick fix below โ or submit a support ticket and our team will jump in.
Start here โ the most common issues and the first thing to try for each.
Check your content calendar for the scheduled date, time and time zone. If a post shows "scheduled" but never went out, the social account connection likely expired โ reconnect the account and retry. Still stuck? Submit a ticket and we'll republish it for you.
Reply directly in your approval thread with the change you need. Revisions requested before 2pm ET are usually turned around the same day.
First confirm the ad account's payment method is current โ a declined card pauses all campaigns. Then check Ads Manager for "limited" or "rejected" status before assuming a delivery problem.
Your monthly report covers reach, engagement and growth, compared month-over-month. A "drop" right after a viral month is normal regression, not lost performance.
Changing your Facebook/Instagram password breaks the connection. Reconnect from your dashboard's Integrations page and accept all permission prompts.
Submit a ticket with examples of the direction you want โ your AI brand strategist profile gets updated the same week.
Check on another device or network first โ it's often local cache (hard-refresh with Ctrl+Shift+R). If it's truly down, submit a ticket right away โ uptime issues jump the queue.
Small text or image swaps are covered โ submit the exact page URL and the new content. Bigger layout changes get a quick scope and timeline from us first.
If the widget doesn't appear, a cache purge usually fixes it. If it appears but answers oddly, tell us the exact question that was asked โ we retrain the bot with it.
Test in an incognito window โ browser extensions and ad blockers often block form scripts. If it still fails, submit a ticket with the page URL and a screenshot of any error.
"Not secure" warnings usually mean an SSL certificate renewal is pending โ these auto-resolve within 24 hours. Recent domain changes can take up to 48 hours to propagate.
Force-close and reopen the app, and check the app store for a pending update. If it persists, include your device model and OS version in your ticket.
Confirm call forwarding is still active on your business line โ a carrier reset can drop it. Test by calling your own number; if it rings past 30 seconds with no AI pickup, submit a ticket.
Texts to landlines silently fail โ verify the caller's number is a mobile. Also check the contact isn't marked DND in your CRM.
Check All Contacts first โ leads may be arriving without a pipeline assignment. If the source is a form or ad, confirm that integration is still connected.
A contact who replied STOP or is marked DND halts all automation for them. Check the contact's activity log; if it shows "skipped," include the contact name in your ticket.
Review requests trigger when a job or appointment is marked complete โ confirm it was. Also verify your Google Business Profile connection is active.
Double-bookings usually mean a personal calendar isn't synced for conflict checking. No slots showing? Check your availability hours and minimum scheduling notice.
Check the trigger conditions against what actually happened โ tag spelling, form ID, pipeline stage. Contacts who already went through may be blocked if re-entry is off.
Note which contact it happened on, what you expected and what happened โ the execution log shows us the exact branch taken. Please don't edit the live workflow; we'll fix it on a draft.
Submit the workflow name and the change in plain language ("when X happens, also do Y"). We'll confirm scope before touching anything live.
Describe the manual process step-by-step as you do it today, including the tools involved. We'll scope it on a discovery call and build from there.
Submit a ticket with your business name and invoice number, or email [email protected] โ billing questions are answered within one business day.
Can't find your fix above? Send the details below โ the more specific, the faster we can jump in.