Frequently asked questions

First confirm that you are using your company’s correct system URL and the exact login account created by the administrator. Use the reset option if shown; otherwise ask the administrator to reset the temporary password. Never send a password or one-time code to support.

The current administrator flow creates the login account and temporary password directly; it does not send an email invitation. Confirm the exact account name, reset the temporary password if needed, and check the assigned team and role. Correct the existing record rather than creating a duplicate employee.

Menus may depend on role permissions, plan entitlements, tenant feature gates or required setup. Ask an administrator to check all four. A hidden or disabled feature must not be treated as available.

Check provider authorization, channel status, inbox-to-team mapping, agent access and active filters. Send one test message from a separate customer account and record its time before contacting support.

Read the visible error first. Common causes are an expired channel token, provider window rules, unsupported file type, file-size limit or network failure. Keep the original error and reduce the attachment only when the limit message asks you to.

Visibility follows the inbox team mapping and permissions. Assignment identifies the current owner but does not replace the team boundary. If no agent owns the conversation, the mapped team must monitor its unassigned queue.

Search using verified email and phone values, then use the supported merge flow when available to authorized users. Do not delete a record merely to hide duplication because it may contain conversation history. Contact support when merge is unavailable.

Check assignment, team visibility, application notification preferences, browser permission and whether the event occurred while you were already viewing the conversation. Notification delivery does not replace monitoring the work queue.

The system should preserve the known limit message and stop the blocked action instead of silently exceeding entitlement. Existing data remains subject to the active plan. Ask an administrator or support to review the exact limit.

No general autonomous promise is made. Sales AI action type and risk are currently rule-driven, with optional generated rationale. Ad AI suggests actions but does not directly write changes to Meta. A person must review external impact before approval.

Business data is scoped to the company tenant and deployment controls. Users must still follow least privilege. Never send passwords, one-time codes, API keys, access tokens or unnecessary customer secrets through chat or screenshots.

Open Help & Support in the signed-in application and choose Online Support. Include the page, approximate time, action and observed result. Messages may be left at any time; the first release does not promise an immediate response SLA.