Support

Email hello@abotcompany.com for help with accounts, dashboards, connected workspaces, directory sync, source evidence or your context gateway. Include your organisation name and a short description of the problem.

For an existing issue, reply to the same email thread so we can keep the details together. Any support hours, response commitments or escalation arrangements in your customer agreement apply.

Tell us the affected feature and page URL, what you expected, what happened, and the steps needed to reproduce it. Include the date, time and time zone, plus a request, sync or run identifier if one is available.

A redacted screenshot, browser version and the affected provider or workspace name can help. For a sync issue, include the visible connection status and the time of the last successful sync.

Do not email passwords, API keys, OAuth client secrets, access tokens, recovery codes or confidential source documents. Redact personal and confidential details from screenshots and error messages. We will discuss an appropriate method if additional diagnostic information is needed.

Use the admin console sign-in page and the email address associated with your organisation. If an email verification code does not arrive, check spam and confirm that the address is correct before requesting another code.

Your organisation administrator manages membership and roles. Contact them first if your organisation or project is missing, or if your account no longer has access. Do not create a second organisation to work around an access problem.

A workspace connection requires authorisation through the provider. The provider may require an administrator to approve the app or requested permissions. Confirm that you are authorising the intended workspace and that your organisation permits the connection.

After a directory connection is authorised, directory sync runs automatically. Knowledge access depends on directory sync completing successfully. Connecting a workspace for directory sync does not automatically import every message or document; content ingestion is managed separately.

If sync fails or remains pending, check the connection status and any visible error. Tell us the workspace, failure time and run identifier. Do not send the token or reconnect repeatedly to try to bypass an unresolved error.

Check that you are in the intended organisation and project, that the source has been connected and ingested, and that your account is permitted to access the original information. A directory connection alone does not make all source content available.

Review the last successful sync and any linked source evidence. If information appears outdated or a generated answer is wrong, include the source link and a description of the discrepancy, with private content removed.

For a context gateway or customer-cloud deployment, include the deployment or endpoint identifier and the affected operation. Never include gateway credentials or cloud access keys.

For billing questions, email hello@abotcompany.com with your organisation and invoice or subscription reference. Do not include payment card details.

An authorised organisation administrator should request subscription changes or organisation closure. Cancellation, renewal, refunds and data handling follow your accepted plan or agreement and applicable law. Ask about any required export before closing the organisation.

Email hello@abotcompany.com with the subject “Privacy request”. Describe whether you need access, correction, export, deletion or another privacy-related action. We may verify your identity or authority before making changes.

For organisation-controlled content, contact your organisation’s administrator first. Disconnecting a provider stops future access using that authorisation and does not by itself erase previously imported information. Our Privacy policy explains roles, retention and your rights.

Email hello@abotcompany.com with the subject “Security report”. Include the affected service, time, potential impact and safe reproduction details. Keep the report private and omit live credentials and other people’s information.

If you suspect a connected credential has been compromised, use the provider’s controls to revoke it and notify your organisation administrator. Preserve relevant identifiers and timestamps so the incident can be investigated.

Read our Terms of service for responsibilities when using connected sources and AI features.