Return-Path: <sarah.jenkins@enterprise.com>
Received: from mail-sor-f41.google.com (mail-sor-f41.google.com [209.85.220.41])
by mx.agentsmtp.net with ESMTPS id 4jK9mN2xQ7 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384)
for <you@company.com>; Mon, 24 Mar 2026 09:14:02 +0000 (UTC)
Received: from smtp.enterprise.com (smtp.enterprise.com [203.0.113.88])
by mail-sor-f41.google.com with ESMTPS id abc123.2026.03.24.09.14.01
(version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256)
for <you@company.com>; Mon, 24 Mar 2026 09:14:01 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprise.com; s=mail2024;
h=mime-version:from:date:message-id:subject:to:cc:content-type;
bh=+Y3JkZ...truncated...=;
b=WlRTN...truncated...==
ARC-Seal: i=1; a=rsa-sha256; t=1711271642; cv=none; d=enterprise.com; s=arc;
b=dmFsdW...==
Authentication-Results: mx.agentsmtp.net;
dkim=pass header.d=enterprise.com header.s=mail2024;
spf=pass (mx.agentsmtp.net: domain of sarah@enterprise.com designates 203.0.113.88 as permitted sender)
smtp.mailfrom=sarah.jenkins@enterprise.com;
dmarc=pass (p=REJECT sp=REJECT pct=100) header.from=enterprise.com
X-MS-Exchange-Organization-AuthAs: Internal
X-MS-Exchange-Organization-Network-Message-Id: 08d9a1f2-3c4b-56e7-8901-23456789abcd
X-Mailer: Microsoft Outlook 16.0
Thread-Topic: Integration outage + SLA
Thread-Index: AdZx9y0w8v7u6t5s==
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_982374_87654321.1711271640123"
From: "Sarah Jenkins" <sarah@enterprise.com>
To: "You" <you@company.com>
Cc: legal@enterprise.com, team@company.com
Subject: =?UTF-8?Q?URGENT:_Production_integration_down_=E2=80=94_SLA?=
Message-ID: <CA+xyz=abc987.enterprise.com>
Date: Mon, 24 Mar 2026 09:13:58 +0000
X-Priority: 1 (Highest)
X-MSMail-Priority: High
Importance: high
------=_Part_982374_87654321.1711271640123
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Hey =E2=80=94 the new update broke our integration. Are we still on for th=
e $15k SLA? Fix this ASAP.
------=_Part_982374_87654321.1711271640123
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-mic=
rosoft-com:office:office">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8">
<!--[if gte mso 9]><xml><o:OfficeDocumentSettings><o:AllowPNG/></o:OfficeD=
ocumentSettings></xml><![endif]-->
<style type=3D"text/css">
<!--
.body { font-family: 'Segoe UI', Arial, sans-serif; color: #333333; }
.small { font-size: 11px; color: #888888; }
-->
</style>
</head>
<body class=3D"body">
<table role=3D"presentation" width=3D"100%" cellpadding=3D"0" cellspacing=
=3D"0" style=3D"border-collapse:collapse;mso-table-lspace:0pt;mso-table-rsp=
ace:0pt;">
<tr><td style=3D"padding:12px 0;">
<img src=3D"data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///ywAAAAAAQABAAACAUwAOw=3D=3D" width=3D"1" height=3D"1" alt=3D"" style=3D"display:block;border:0;outline:none;text-decoration:none;">
</td></tr>
<tr><td style=3D"font-size:15px;line-height:22px;">
Hey, the new update broke our integration.
</td></tr>
<tr><td class=3D"small" style=3D"padding-top:8px;">
Are we still on for the $15k SLA? Fix this ASAP.
</td></tr>
<tr><td style=3D"padding-top:24px;font-size:10px;color:#aaaaaa;">
This message may contain confidential information. If you are not the inten=
ded recipient, delete it. Tracking ref: ENT-2026-88421-MSG
</td></tr>
</table>
<!--[if mso]><table role=3D"presentation"><tr><td height=3D"0"><![endif]-->
<div style=3D"font-size:0;line-height:0;max-height:0;overflow:hidden;mso-hi=
de:all;">
<img src=3D"https://track.enterprise.com/pixel.gif?m=3D88421&u=3D9f3e2d1c" width=3D"1" height=3D"1" alt=3D"">
</div>
</body>
</html>
------=_Part_982374_87654321.1711271640123--Agent status
Give your AI its own inbox, or connect it to a human's mail — same pipeline, so your agents stay aligned with real conversations without rebuilding everything twice.
Give your agents their own inboxes at @yourcompany.agentry.to to send and receive email autonomously.
Agentryunderstanding layerEmail is normalized, summarized, and tied to memory graphs your agent can actually use.
Connect your own mailboxes — Gmail via Google sign-in or any standard IMAP server. Now every time a message arrives, your agent gets structured context alongside the cleaned content.
Engineering choices that make email a first-class input for helpful, grounded assistants.
AI on real inboxes touches regulation and trust. We focus on data minimization in what we send to your agents, clear deletion paths, and fewer surprises for your security review.
First-party SDK is on the way. Until then, use the AgentMail-compatible client pointed at Agentry — same patterns, our API.
Predictable pricing — pay for the compute you use, not the spam you don't.