Work with Neil by email.

Put neil@seal.run in the To field and send from the address on your Seal account. Forward the original request or write your own. Include the files, the result and format you need, and anything Neil must keep unchanged. Check that forwarded attachments are included. You do not need to connect your inbox.

Neil confirms when work starts. The private chat in Seal holds your request, supported attachments, progress and generated files. You can step away while Neil works. If it needs an answer or a required approval, open the chat to continue.

Neil emails back when the work is ready. Check the result against the source files, including calculations, missing evidence and open questions. Reply with changes or continue in Seal. A returned draft still needs your normal review and approval before use.

Send the current files and name what must stay unchanged. Ask Neil to flag missing information rather than fill in gaps. Your team still owns review, approval and release.

1. A colleague emails about a supplier delivery. One material arrived without a certificate of analysis, the other with one attached. Both are in quarantine, and the second is wanted for a run on Tuesday.
2. The email is forwarded to neil@seal.run with the raw material specification, asking Neil to check the certificate against the specification and draft an email to the supplier over lunch.
3. Neil acknowledges the request, then replies with the draft. It finds two discrepancies: endotoxin of 6.8 EU/g against a maximum of 5 EU/g, and 33 days of remaining shelf life at receipt against a requirement of at least 12 months. It also asks for the missing certificate.
4. The sender reads the draft and sends it to the supplier. All names, companies and records in the demo are fictional.

Active members of organisations with Neil enabled. Your usual Seal access and AI settings apply.

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 “Production meeting brief” chat, update the brief with the attached shift notes.

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.

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:

Prepare the production meeting brief [org:acme-quality]

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

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.

For work on records in Seal, name the records and the result you need. Connected systems need the appropriate connection and access. Emailing a task does not give Neil access to other files in your inbox or on your computer.

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.

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.