Give every message a clear next step.

Keep the message and its next step understandable

Veil places the subject, sender, message body and available actions in distinct parts of the reader. Use it to understand a conversation before deciding what should happen next. The inbox list, reader, composition tools and Settings pane have different jobs, so a settings change does not replace the conversation you were reading.

An email can contain a request, a deadline and background information without making all of them equally reliable. Read the source, confirm the sender and inspect attachments or links carefully before turning extracted information into an action. An assistant’s interpretation remains something you review.

Connect the right mailbox and preserve the source

Create a Veil address or connect an existing mailbox through the supported authorisation flow. Confirm which mailbox and conversation are selected before replying, especially when several identities are available. Provider authorisation can expire or be withdrawn independently of your Patchman sign-in.

Open the original message and check the context around a proposed deadline or commitment. An isolated sentence can omit a correction later in the thread. Keep sensitive information out of unnecessary replies, and confirm both the intended recipient and the identity from which a message will be sent.

Read, filter, compose and review actions separately

• The inbox filter opens a selection dialog so you can choose the view you need. Search and filtering help locate a conversation without turning a label into proof of completion.
• The reader distinguishes the subject, sender, body and footer from reply and action controls. Inspect the content before using the adjacent action.
• Review extracted commitments, reminders and other proposed next steps against the original text. Correct an interpretation rather than silently carrying it into later automation.
• Compose replies or designed email, review secure-link choices and keep settings in their own pane. Mobile message-list navigation remains available without a hidden collapse state trapping the reader.

Example: deliver a document and plan a useful follow-up

1. Prepare and inspect the document in FOLD, upload the intended delivery to Dowe and review the share link as its recipient would.
2. In Veil, choose the correct sender and recipient. State what the link contains, what action is requested and the actual agreed deadline.
3. Review the full message, links and attachments before sending. A preview helps inspect presentation but is not a delivery receipt.
4. Keep any reminder connected to the real conversation. After the deadline, check replies and delivery state before deciding whether a follow-up is still appropriate.

Follow the document handover workflow

Distinguish a draft, a send attempt and delivery

Save the draft and inspect the sender, recipients, subject and attachment state before sending. A request that has an uncertain acknowledgement must be checked against the provider’s Sent or queue state before another submission. Repeated sending can create duplicate messages even when the original response did not reach the browser.

A successful submission is different from a recipient reading or acting on the message. Review the available delivery events and the actual reply. If a connected mailbox needs authorisation again, reconnect through the supported flow instead of sharing a password or token in a support conversation.

Controlled sharing and explicit paid actions

Veil’s secure-link workflows help control access to shared conversation material. Review the permitted recipient, expiry and intended content before sending a link. Revocation governs future access through the service; it cannot remove information a recipient has already copied.

Account supplies identity, access and the common credit wallet. Any paid AI operation must show its request-specific exact or maximum charge before authorisation. Sending or synchronising through an authorised mail provider is a distinct operation from that quote. Include only the message context necessary for a feature you choose, and review any proposed automated reply before relying on it.

Questions about reading and acting on email

Veil walkthrough · Veil guide hub · Delivery and follow-up showcase