Skip to main content
We have made task-agent email easier to use in operational workflows and added guidance for connecting TextMine to Microsoft Copilot Studio.

​
Task-agent email for operational requests

Organizations can now route more task-agent work through email once task-agent email has been activated for that organization. This is useful for shared service accounts, intake inboxes, ticketing systems, Zapier automations, and connected operational channels such as ServiceNow. A team can send a request to its TextMine task-agent address, then continue the same work by replying to the thread. Task-agent email must be activated before incoming emails can create or update task-agent work. If it has not been activated, TextMine does not create the task and the requester receives a clear message explaining that the email route needs to be enabled first.

​
More useful email replies

Task-agent emails now read more like a working conversation. When TextMine receives a task, the acknowledgement tells the requester that the work has started and that they can reply with extra context. If the task agent needs clarification, the email includes the question and explains that a reply will resume the task. When a task completes, the result is included directly in the completion email where available, so users do not need to hunt for the outcome in another screen.

​
Copilot Studio setup guide

We have added a Copilot Studio setup guide for teams that want a Microsoft Copilot Studio agent to use TextMine. The guide walks through the recommended setup, the custom connector fallback, and the first checks to run after connecting an agent.

​
Document intake reliability

Document intake is more reliable for automated and service-account-driven flows. This helps requests that arrive from shared inboxes, workflow-generated emails, Zapier automations, ServiceNow-backed processes, and other non-interactive routes.