> For the complete documentation index, see [llms.txt](https://docs.innova-drilling.com/introduction/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.innova-drilling.com/introduction/technical-notes/low-priority/ws-new-outlook-email-automation-unavailable.md).
# WS - New Outlook Email Automation Unavailable
## Introduction
Well Seeker has been able to automatically generate emails using Classic Outlook for many years, for example the Morning Report, RTAC and Survey Update features. This feature continues to function and Microsoft are supporting Classic Outlook until 2029.
Microsoft also has New Outlook available. Unfortunately, New Outlook does not fully support email automation features yet and as such we are unable to support the email automation features for any New Outlook users.
## Problem
Users with New Outlook attempt to generate an automated email via Well Seeker. They receive the below warning message
### Solution
If you wish to use the email automation features within Well Seeker, you will have to have Classic Outlook installed on the PC in question.
Innova will continue to monitor Microsoft’s development of New Outlook and will implement the email automation features if Microsoft make the necessary changes.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.innova-drilling.com/introduction/technical-notes/low-priority/ws-new-outlook-email-automation-unavailable.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
