> ## Documentation Index
> Fetch the complete documentation index at: https://docs.textmine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Contact support

> How to contact TextMine support and what to include so the team can route product, access, integration, billing, or workflow issues quickly.

Use this page when the Help Center does not answer your question, you need a tenant or feature enabled, or an issue needs TextMine support to investigate.

## Email support

Email [support@textmine.com](mailto:support@textmine.com) for TextMine product, access, configuration, integration, billing, or workflow support.

Use your organization's approved support route if your TextMine deployment has a dedicated customer support process or named TextMine contact.

## What to include

Include enough context for the team to route the request without extra back-and-forth:

* Your organization or tenant name.
* The TextMine area involved, such as Workbench, Vault, Workflows, Records, Integrations, Public API, MCP, or Scribe.
* The page URL, Vault, workflow, record, document type, run, or request ID where relevant.
* What you expected to happen and what happened instead.
* Steps to reproduce the issue, including screenshots when useful.
* Business impact, urgency, and any deadline.
* Whether the issue affects one user, a team, or the whole organization.

Do not send passwords, API keys, authentication tokens, private keys, or other secrets by email. If support needs sensitive configuration, ask for the approved secure handoff route.

## Common support requests

| Request                            | Useful details                                                                            |
| ---------------------------------- | ----------------------------------------------------------------------------------------- |
| Access or permissions              | User email, tenant, team, role needed, and the business reason.                           |
| Feature activation                 | Tenant, feature, deployment type, and who approved the change.                            |
| Workflow or task issue             | Workflow name, run ID, trigger type, inputs, expected output, and error message.          |
| Vault or extraction issue          | Vault name, document type, affected document ID, tags or fields, and expected extraction. |
| Integration or API issue           | Provider, endpoint or tool, request ID, timestamp, status code, and sanitized error text. |
| Billing or third-party agent setup | Billing contact email, organization name, signup route, and provisioning status.          |

## Before sending

Search the Help Center first if the question is about a known workflow, integration, permission, or release note. Good starting points:

* [Quick start](/getting-started/quick-start)
* [Product map](/getting-started/product-map)
* [Permissions](/administration/permissions)
* [Integrations](/integrations/overview)
* [Workflows](/workflows/overview)
* [Release notes](/release-notes)

If you are reporting a docs problem rather than a product issue, use the **Raise issue** link at the bottom of the affected page.