Work with Neil by email.

Start with the result you need.

1. Use your Seal email address.

   Put Neil@seal.run in the To field. Sending from an alias or a different account does not identify you as the same member. You do not need to connect your personal inbox to send a request.

2. Describe the task.

   Say what you want back, name the relevant records, and attach supporting files if needed. Neil imports supported attachments into the private conversation.

3. Continue in email or Seal.

   A new email thread normally starts a private Neil chat. The first reply confirms when Neil starts working. The completion email includes Neil’s answer and a link to that chat, where you can inspect the work, download files, answer questions, and complete any required reviews.

Keep the thread going.

Reply in the same email thread to give Neil another instruction. It stays in the same Seal conversation.

To continue one of your existing chats from a new email thread, begin the message with its full, unique title:

In the "Deviation review" chat, add the attached supplier response to the evidence summary.

Use the exact chat title and put it in quotes. If the title is missing or ambiguous, Neil does not guess. Replies keep their original destination even if you rename the chat.

Belong to more than one organisation?

Choose the workspace in the subject of a new thread with [org:workspace-slug]. Find the slug in your Seal address after /o/. For example, a workspace at /o/acme-quality uses:

Without a unique destination, the request waits without starting work. Existing email threads keep their workspace; start a new thread to choose another.

Your conversation. Your permissions.

Neil uses your active membership and existing access to work in Seal. Email does not grant extra access or replace a required review, signature, or approval. If a task needs your input, open the conversation in Seal.

The automatic reply goes only to your registered address. Adding someone on CC does not invite them into the chat or send them the result. Messages addressed to Neil only on CC, automated mail, authentication messages, and mail that fails sender checks do not start work.

If your address is not connected to an organisation with Neil enabled, you receive an automated access notice. Send from the address you use to sign in to Seal, or ask your organisation’s administrator to invite you and check that Neil is enabled. The notice starts no chat and uses no AI allowance. Once you have access, send a new email to Neil. Automatic or unauthenticated mail receives no notice.

If you receive no answer, check your sending address, the To field, your workspace selection, and your active Seal membership. Look in Neil’s session list for work waiting on your input. Your administrator can check whether Neil is enabled and ask Seal support to inspect mailbox intake.