Skip to content
nofeb

Solutions / AI SDR

Outbound and reply handling for AI SDRs

For teams running ai sales development agents

An AI SDR is a long series of threads, each at a stage, each with a next step. The risk is not writing the email; it is sending too much, to the wrong people, from a domain everyone else is also burning.

The problem

Shared sending domains lose their reputation through the actions of their noisiest tenant, and mailbox providers now reject non-compliant bulk senders outright. A sales team needs its own domains and its own reputation, and a hard stop on what an agent may send without review.

How it runs on nofeb

  1. Add your sending domains; nofeb publishes the DKIM, MAIL FROM and DMARC records through your DNS host's API where it can, or gives instructions for that host, verifies them, and each organization can send on its own isolated reputation.
  2. A new domain follows a daily warm-up ramp: sends over the day's cap wait for the next day instead of being dropped. If the organization's bounce or complaint rate crosses its threshold, sending pauses automatically, sending.paused tells your webhooks, and a person resumes it once the list is fixed.
  3. Give each persona or campaign its own inbox and its own budget: sends per hour and per day, recipients per message, and new recipients per day, per inbox or per API key. First contact is throttled per inbox by default, so a new agent cannot open hundreds of cold threads on its first morning.
  4. Put competitors, existing customers and anyone who asked to be left alone on a recipient blocklist at the organization or pod. A blocked recipient is refused on every autonomy tier, and a check call tells the agent before it drafts.
  5. Run new agents at send_with_approval, and let a person approve held sends until the agent has earned a more autonomous tier.
  6. Each reply arrives with typed decisions (intent, needs-reply, automated, requires-human) and a probability for each, so out-of-office notices and real objections are told apart before the agent writes. Query threads across inboxes by stage and by how long the last outbound message has gone unanswered.
  7. Keep the pipeline on the thread: stage, owner agent, follow_up_at and deal value as typed metadata. When follow_up_at passes, a thread.due event wakes the agent to follow up, and send_at schedules the message itself.
  8. Turn on AI disclosure for the campaign's inboxes so agent-written mail carries AI-Generated headers and an optional footer, and register each agent so its mail is signed and anyone can verify which agent sent it.
  9. If your sequencer only speaks SMTP, point it at nofeb's submission port with a per-inbox app password; its messages meet the same tiers, caps and lists as an API send.

Where nofeb stops

  • nofeb will not help you mail people who did not ask to hear from you at volume. Unsolicited outreach must follow the law where the recipient lives and the terms of the mailbox providers you send to.
  • It is not a sequencer or a CRM: it holds the mail, the thread state and the sending policy, and your agent decides what to write.

Status of everything this relies on

CapabilityWhat it doesStatus
Unlimited inboxes Create as many inboxes as the work needs, with a generated or chosen address and an idempotent client reference. Shipped
Send, reply, reply-all and forward Threading headers are set for you, replies default to the original sender, and forwards carry the original attachments. Shipped
Scheduled send Give any send a future send_at time. Shipped
Typed metadata on messages, threads and inboxes Merge-patch keys onto a message, a thread or an inbox, and declare a key's type so every write to it is validated. Shipped
Follow-up timers Set follow_up_at on a thread and, when that time passes, a thread.due event carrying the thread's metadata goes to your webhooks and the event feed, so agents need no scheduler of their own. Shipped
Autonomy tiers enforced by the server Every inbox carries a sending policy, from read-only to autonomous, enforced on the server for every surface that sends, so switching from the API to MCP cannot bypass it. Shipped
Human approval of held sends A held send waits with status awaiting_approval until a human approves or rejects it; both steps emit events. The approval queue lists every held send with its recipients (each marked if new to the conversation), the reasons it was held and who submitted it. Approving needs the separate send:approve scope, which keys from agent self-signup never hold, so an agent cannot approve its own send. Shipped
Custom domains Add a domain and nofeb returns its DKIM, custom MAIL FROM and DMARC records, plus an inbound MX if you want nofeb to receive its mail, checks them, and emits domain.verified when they pass. Shipped
DNS setup made easy nofeb detects who hosts your domain's DNS and gives you the shortest path for that host. It can publish the records through the Cloudflare, DigitalOcean, Hetzner DNS, Vercel, Porkbun or Gandi API with a token used for that one call and never stored, and it never deletes a record. Every other host gets step-by-step instructions in its own terms, plus zone-file, Route 53 and Terraform exports. A live check shows each record's status, what was found and the likely mistake. Pointing your MX at nofeb is a separate choice, so publishing sending records never moves your mail. Shipped
Managed sending with per-tenant reputation isolation nofeb sends on your behalf from your verified domain, and each organization can send with its own isolated reputation, so one sender's behaviour cannot damage another's. Shipped
Delivery events and automatic suppression Delivery, bounce and complaint reports arrive as events, and hard-bounced or complaining recipients are suppressed automatically. Shipped
Automatic pausing and warm-up New custom domains follow a daily warm-up ramp; sends over the day's cap wait for the next day instead of being dropped. If an organization's bounce or complaint rate crosses its threshold, sending pauses automatically and an event says so; resume it by API or in the console. First contact per inbox is throttled by default. Shipped
Per-agent rate and recipient caps Limits per inbox and per API key on sends per hour and per day, distinct recipients per day, recipients per message and new recipients per day, checked and charged in one step so concurrent sends cannot overshoot. A usage call shows the budget left, and you choose whether an exhausted cap holds a send for approval or refuses it. Shipped
Recipient and sender allowlists and blocklists Lists of addresses, domains or wildcards per organization, pod or inbox: who an agent may write to, and whose mail it reads. A blocked recipient is refused on every autonomy tier, a blocked sender's mail is rejected or quarantined, and you choose whether a send outside the allowlist is held for approval or refused. A check call predicts what a send or an inbound message would meet before it happens. Shipped
Decisions on every message A default set of typed decisions on every inbound email (intent, urgency, needs-reply, automated, verification email, phishing, injection risk, requires-human and language) with a probability each, your own decision schemas beside them, human relabels that correct and retrain it, per-question accuracy and calibration stats, and confidence-gated sending for the send_when_confident tier. Decisions run without leaving nofeb by default; a third-party model sees mail only if you opt in. Shipped
Queries across threads by metadata Find threads across inboxes and pods by typed metadata values and ranges, by decision probabilities, and by the direction and age of their last message (every thread at stage quote with no reply for four hours), plus an inbox directory searchable by metadata. Shipped
AI-generated disclosure Per organization, pod or inbox, mail an agent sends carries AI-Generated and AI-Disclosure headers and an optional footer. Mail a person sends from the console or the webmail never does. Shipped
Agent identity and signed mail Register each agent with a name, a human sponsor and the keys it acts through. Its mail carries an agent header and a signature over the sender, recipients, subject and body that anyone can check against your organization's published keys or nofeb's verification call. Revoking an agent stops its keys from sending and marks its mail as revoked. Shipped
SMTP submission Authenticated SMTP submission on ports 587 and 465 for tools that only speak SMTP. Every submitted message meets the same autonomy tiers, approvals, lists, caps and hooks as an API send, and a held message is accepted and reported as held. Shipped