Template-based messaging

Mandrill sends transactional email, such as receipts and password resets, through templates and an API. When a triggering event arrives, the agent reads the payload, selects the template your rule specifies, fills the merge fields from the source record, and hands the message to Mandrill for delivery. Standard, well-formed messages go out immediately. If required fields are missing, the recipient address looks malformed, or the event type is unrecognized, the agent holds the message and notifies the owner, who corrects the data or confirms the template before the email reaches the customer.

Email templates

Templates in Mandrill hold the layout and merge fields for each transactional message. The agent keeps them aligned with your content rules: when a source change calls for a wording or field update, it reads the request, applies the approved edit, and saves the template version. Minor, pre-approved copy changes are applied directly. Structural edits, legal or compliance wording, and anything touching links or unsubscribe handling are routed to a person, who reviews the rendered result across clients before the new version is allowed to reach real recipients.

Delivery event handling

Mandrill reports opens, bounces, spam complaints, and delivery failures back through webhooks. The agent reads each event, applies your rule, and updates the linked customer or order record, suppressing addresses that hard bounce and noting complaints against the contact. Routine events close on their own. A spike in failures, a complaint from an important account, or a bounce on a message that must reach the customer is escalated to the owner, who investigates the cause and decides whether to resend, correct the address, or pause the sending program.