Set up, test, then launch

Email sending guides

Choose the path that matches the email you want to send. Prepare the audience, understand the delivery route, and check a controlled result before launch.

Open the pre-send checklist Find setup help

Four paths to a prepared send

A campaign for subscribers

Start with the audience, then prepare the message.

Confirm the active audience and preserve all exclusions. Use the migration preflight if you are preparing an export from another platform.
Review the sending domain, template, personalization and selected route. Compare the active audience and required features with your plan.
Use a mailbox you control for the test. Check the saved content and the actual delivery result before the final authorized campaign.

Review campaign setup

Email from your application

Make one traceable request before routing real traffic.

Create a key with the required scopes and keep it on your backend. Follow the API quickstart, including its idempotency and error guidance.
For an SMTP client, check TLS, authentication, sender restrictions and the currently published size and attachment support. Your domain route still matters.
Follow the message result, verify signed webhooks and handle retries using event identities. A successful API response is not an inbox-placement guarantee.

Explore API and SMTP

Delivery through your own VPS

Confirm the network before paying for infrastructure.

Confirm your provider permits outbound port 25 for your exact account, product and region. Check the public IP and reverse-DNS options.
Choose an eligible plan, add the server, and install and pair the agent using the dashboard instructions. Review current heartbeat, DNS and IP-identity observations.
Select server only or hybrid deliberately. Review warm-up limits, hosted-fallback behavior and the full VPS estimate, then trace a controlled test.

Follow the server guide

Customer replies in Inbox

Prepare receiving before relying on a conversation.

Configure supported receiving and reply capture for future supported sends. Confirm the sender and reply identity you intend to use.
Send and reply using controlled mailboxes. Check that the reply reaches the intended conversation and that your team has the appropriate access.
For an application integration, map the thread to your own reference and verify the incoming-message event and repeated-event behavior before rollout.

Review Inbox and reply capture

Switching platforms?

Keep the original status, exclusion and consent records. Prepare the subscribed-only audience separately, inspect a small import, and test the rebuilt workflows before switching traffic. Provider-specific templates, reports and automation behavior do not transfer automatically.

Choose a migration guide Explore editable template briefs

Read the result at the right level

Queued

The platform has work waiting to run. Review the route, agent and any hold or allowance condition; queued does not mean delivered.

Destination accepted

A receiving mail server has accepted the message. Its own filtering and mailbox rules still decide placement.

Tracked activity

Opens and clicks are tracking observations. Automated clients can generate activity, and privacy controls can prevent it from being measured.

Bring the setup and estimate together

Review subscribers, connected servers and planned hosted sends separately from your total VPS cost. The estimate does not determine safe server throughput.

Estimate your cost Understand the data flow