Skip to main content
First determine whether the problem is connection setup, incoming delivery, automated response, or outgoing human reply.
Check the script, allowed domain, mobile visibility, browser blockers, and cached page version. The allowed-domain list must contain the actual website; example.com also covers www.example.com. Test on the exact production URL in a private window.
Retry with pop-ups enabled and sign in to the account that administers the intended Page, business, spreadsheet, or Official Account. Approve the requested access and keep the Jaaxis page open.
Find the current Jaaxis agent and disconnect the third-party account there before connecting it to the new agent.
Read the visible error first. A closed Meta reply window is not fixed by reconnecting; follow the channel guidance in Human replies. For expired authorization, reconnect the intended account, send a fresh customer-side test message, and check delivery. Use the failed message’s Retry action only after resolving the cause.
Compare every DNS host and value with Jaaxis. Check whether the DNS provider automatically appends the domain. Wait for propagation and require both SPF and DKIM to pass.
For support, record the agent name, channel, approximate time, direction of the failed message, and visible error. Do not include access tokens, channel secrets, customer message content, or personal data.

​
Google Sheets does not show the expected file

Open Google Sheets → Manage and check the signed-in Google account and picked-file list. For a new workflow, ask the Assistant to request a sheet pick. For an existing selection, use Change and confirm the worksheet, header row, and detected headers. Reconnect when Jaaxis requests it. Ask the Assistant to inspect the worksheet and columns if access works but the configured lookup or write fails.