Skip to content
Skip to content
All AI Hub docs

Trust & safety

Power user

Anti-double-send and loop safety

How AI Hub avoids double-emailing a broker or looping — MC-keyed dedupe, one send pipeline, an autonomous lease and action-log, and watchdogs.

3 min read

When the agent is emailing brokers on its own, the thing you most want is for it to never double-send or get stuck in a loop. Here's the plumbing that prevents that.

One broker, one cold email — MC dedupe

  • Numeo dedupes broker outreach by MC number.
  • When it contacts a broker, it records that against the broker's normalized MC. A re-run or a restart won't fire a second cold email at the same broker.
  • That record is what backs the "already contacted" note you'll see on a broker.
  • Brokers with no MC on file still get the email; they just don't get a dedupe record.

One send pipeline

Both ways outreach can go out — a direct send and the agent's own send tool — funnel through a single send pipeline. Because there's one door, the two paths can't double-send the same message.

Autonomous safeguards

Autonomous work adds more guardrails so a re-triggered search or a restart can't re-send:

  • A lease and action-log record what's already gone out, so a repeat trigger doesn't repeat a send.
  • Run gates and active-run tracking stop a second run from stepping on one that's already in flight.
  • A circuit breaker and a loop detector stop the agent if it starts spinning.
  • A manual pause lets you stop processing when you want to.

Dropped-send recovery

If a socket send drops mid-flight, a watchdog recovers it rather than blindly firing again — so a flaky connection doesn't turn into a duplicate email.

Good to know

Need help? Email support@numeo.ai or use Report a problem in the app.

Was this helpful?