Email support
Email 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.
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. |