Pre-send policy

Preflight every AI-generated email before it sends.

Score recipient, sender, message, and policy risk in one API call before an AI agent sends outbound email.

What it does

The preflight endpoint combines deliverability, sender health, message claims, recipient context, agent behavior, and workspace policy into one allow, delay, block, or requires_approval decision.

AI agent builderssales automation teamscompliance-sensitive outbound teamsplatform engineering

Best fit

  • One endpoint covers recipient, sender, message, campaign, and agent context.
  • Reason codes explain every non-allow decision.
  • Feedback APIs can update policy from delivered, bounced, complaint, reply, and unsubscribe outcomes.
Capabilities

Signals your workflow can act on.

Each page targets a clear long-tail query while staying tied to the actual SendGuard API surface.

Actionable decisions

Return allow, delay, block, or requires_approval instead of forcing each integration to interpret raw signals.

Message-aware scoring

Consider claims, sensitive industries, unsubscribe language, sequence context, and agent history before approving a send.

Approval routing

Send high-risk outreach to the right queue with a clear reason and complete audit context.

FAQ

Common questions

What decisions can the preflight API return?

The primary decisions are allow, delay, requires_approval, and block. Each response includes a risk score and reason codes.

Can SendGuard be used before Gmail, HubSpot, Apollo, or custom sending code?

Yes. SendGuard sits before the sending layer. Your integration calls SendGuard first, then sends, holds, or blocks based on the decision.

Related products

Continue through the outbound decision layer.