GuideZero-Vendor-Edit & Agency Isolation

60-Second Email Forwarding & Multi-Client Agency Setup

How to connect existing corporate Google Workspace, Microsoft 365, or client accounts to Sentry Relay without changing third-party vendor logins, while isolating each client with Scoped API Keys and The Human-Fallback Safety Bridge™.

The Zero-Vendor-Edit Advantage (Stage 2 Header Unwrapping)

Changing the registered email on 50 existing enterprise portals (Stripe, AWS, GitHub, banks, or healthcare EHRs) to a bot domain creates administrative friction and can trigger account lockouts. By setting a 60-second auto-forwarding rule in Gmail or Outlook to *@in.sentryrelay.com, our Stage 2 parser automatically unwraps Gmail (---------- Forwarded message ---------), Outlook, and Apple Mail headers to recover originalSender and originalSubject—so your agent still queries /wait?sender=stripe.com seamlessly.

Setup in Gmail & Google Workspace

1
Add Forwarding Address: Go to Settings → See all settings → Forwarding and POP/IMAP. Click Add a forwarding address and enter your Identity's inbound address:
your-identity-slug@in.sentryrelay.com
2
Confirm Forwarding: Google will send a confirmation code or link. Sentry Relay's inbound parser automatically extracts the Google verification code! You will see it appear immediately in your Dashboard Overview → Live Feed. Copy and paste it back into Gmail.
3
Create Filter Rule: Navigate to Filters and Blocked Addresses → Create a new filter.
- From: no-reply@*, noreply@*, support@*, security@*
- Has the words: ("verification code" OR "security code" OR "magic link" OR "OTP")
- Action: Check Forward it to: your-identity-slug@in.sentryrelay.com.

Setup in Microsoft 365 & Outlook

1
Open Rules: In Outlook Web, click the gear icon Settings → Mail → Rules → Add new rule.
2
Configure Condition: Select condition Subject or body includes → "verification code" or From contains vendor address.
3
Select Action: Choose Forward to → your-identity-slug@in.sentryrelay.com. Save rule.

Multi-Client Agency Isolation & The Human-Fallback Safety Bridge™

When an AI automation or RPA agency manages 10 to 250+ client accounts, two operational requirements are non-negotiable: (1) clients must never miss human fraud texts or voice calls sent to their bot's phone number, and (2) one client's worker must never be able to read another client's 2FA codes.

import { SentryRelay } from '@sentryrelay/sdk';

const adminRelay = new SentryRelay({ apiKey: process.env.SENTRY_RELAY_API_KEY! });

// Provision an isolated Identity for Client Acme with Human-Fallback Safety Bridge™
const clientIdentity = await adminRelay.identities.create({
  name: 'Client Acme — NetSuite & Chase Bot',
  slug: 'client-acme',
  emailHandle: 'client-acme', // Receives mail at client-acme@in.sentryrelay.com
  fallback: {
    enabled: true,
    // Non-OTP texts (e.g. "Reply YES to authorize $5,000 wire") route here immediately:
    fallbackEmail: 'founder@acme-client.com',
    fallbackWebhookUrl: 'https://hooks.slack.com/services/T000/B000/X000',
    // Inbound voice calls to the Telnyx DID bridge live via TeXML <Dial>:
    voiceForwardToE164: '+14155550199',
  },
});

// Attach a dedicated US Carrier SMS DID in the client's area code
await adminRelay.identities.provisionSmsDid(clientIdentity.id, { areaCode: '415' });

Zero-Retention Privacy Guarantee

Sentry Relay extracts only the numeric OTP passcode or magic authentication link using deterministic heuristics in under 8ms. The email body, sender names, and headers are held exclusively in volatile RAM and completely purged within 60 seconds (or immediately via Burn-After-Read). We never store full emails or SMS bodies in persistent databases.