VesselCheck recipients, connection, and content before delivery.
Prepare a deliberate send
Open the email and choose Review & send. Check the sender and connection, recipients, subject, preview text and message. Use a test or preview available in your delivery setup to inspect links, images and formatting before a wider send.
Connect the supported delivery service through the connection flow if prompted. Follow the provider’s setup and verification instructions; a connection is separate from writing the draft. Do not assume a message was sent just because it was saved or exported.
After sending
Use EmailAI’s delivery or activity view to inspect the state shown for the send. If a connection or delivery fails, read the displayed error, verify the sender and provider setup, and retry only after checking whether the earlier attempt was accepted. For a one-off external mailing workflow, Options also offers HTML and plain-text export.
For list-based campaigns, see Prepare an Outreach campaign.
The review dialog also shows recent submissions and offers connection setup when a sender is not configured.
Test the reader’s journey
For a sample Harbor update, send a test to an address your team can open. Check the sender name and subject in the inbox, then open every link on a phone. If a video is hosted elsewhere, test it while signed out of the hosting account. Check that any missing personalization has an understandable fallback.
In Outreach, preparing a review creates an unsent provider draft; sending a test contacts only the specified test address. The final confirmation is a separate step. If the saved message changes after preparation, update the review before confirming. See Outreach campaigns for list and scheduling checks.
Understand the handoff
Writing, exporting, preparing a provider draft, sending a test and sending to an audience are separate actions. Confirm which action has happened by checking the status shown in EmailAI and, when needed, the connected provider. Keep the message and audience review together so a teammate can see what was approved.
If the send is delayed or its state is unclear, avoid repeatedly submitting it. Check the provider’s activity and the recipient or campaign status first. A provider may accept a message before the workspace refreshes; use the displayed status and provider details to decide whether a retry is needed.
Was this a useful next step?
Take the idea into the workspace.
Keep this guide nearby. Start small, review the result, and make it your own.
Try it in Vessel