Get useful support and diagnose common problems

Identify the exact page, action, error message, time, and account role. Check whether the problem affects one record or all records, and whether a reload changes it. Avoid repeating an import, payment, or customer message until you know whether the first attempt succeeded.

Missing menu or denied action: ask the administrator to review your role. Missing choice in a form: check the related settings list and active state. Wrong report totals: review date field, filters, amounts, assignments, and missing attribution. Missing calendar slot: review capacity, override, timezone, and bookings.

Invitation/email failure: check server email configuration and sender verification. SMS failure: check provider, sending number, consent, and delivery error. Automation failure: check trigger conditions, sending window, and scheduled processing. MCP failure: check token validity, supported transport, approval, and deployment URL.

Do not include passwords, connection keys, verification links, payment card details, database exports, or provider credentials in support messages. Redact private contact data in screenshots unless a secure support process specifically requires it.

The in-app Support area may depend on an AI service and is not proof that a human support team or ticketing SLA is active. Use the help articles for repeatable setup and follow the contact options actually offered by your deployment.

Database migration, file storage, authentication, domain routing, payment webhooks, email delivery, messaging, background jobs, and external AI each have separate operational checks. If a feature reports unavailable configuration, the platform owner must resolve that service; entering more CRM data will not fix it.