Samva and AgentMail, compared.

What each one ships.

Moving from AgentMail.

1. 01

   Add your domain and publish the DKIM and SPF records Samva generates next to the old provider's. Both can send while you switch.

2. 02

   Swap the send call.

   import { AgentMailClient } from "agentmail";
   
   const client = new AgentMailClient({
     apiKey: process.env.AGENTMAIL_API_KEY,
   });
   
   const inbox = await client.inboxes.create();
   
   await client.inboxes.messages.send(inbox.inboxId, {
     to: "ada@example.com",
     subject: "Your receipt",
     text: "Thanks for your order.",
   });
   

   const mailbox = await samva.mailboxes.create({
     endpoint: { channel: "email", address: "orders@acme.samva.email" },
     name: "Orders",
   });
   
   await samva.mailboxes.sendMessage({
     id: mailbox.id,
     to: ["ada@example.com"],
     subject: "Your receipt",
     text: "Thanks for your order.",
   });
   

3. 03

   Map webhooks. Samva sends signed events for sent, delivered, bounced, complained, failed, and received, with received going to the endpoint your domain's receiving route names. Opens and clicks arrive as message.opened and message.clicked, and unsubscribes as contact.unsubscribed.

   AgentMail event	Samva event
   message.received	message.received
   message.sent	message.sent
   message.delivered	message.delivered
   message.bounced	message.bounced
   message.complained	message.complained
   message.opened	message.opened

4. 04

   Recreate templates as versioned templates, or send your existing HTML inline while you move.

5. 05

   Keep the old provider's suppression list in your app and filter against it. Samva cannot import it.

6. 06

   Turn on receiving if you want replies back.

What does not move: templates, the suppression list, and message history.