Skip to content

Forward an email

Every Product has an auto-provisioned inbox at fwd+{product_id}@inbox.withherald.co. Forward any email — a support ticket, a feature request, a competitor mention, a partner intro — and Herald classifies, summarizes, and files it into the right section of your next briefing. No OAuth, no webhook setup.

Every Product gets an auto-provisioned address the moment it’s created:

fwd+{product_id}@inbox.withherald.co

The exact address is visible in Settings → Integrations → Email and on the onboarding checklist.

Anything useful Herald couldn’t reach through an integration:

  • Sales-call transcripts from Fathom, Fireflies, Otter, Grain, or Zoom’s native transcript email. Herald detects the format (VTT, SRT, “Speaker: text”, Fathom, Fireflies) and routes to the sales-call pipeline.
  • Support escalations a customer emailed directly to support@ or to you personally.
  • Review screenshots or emails from G2, Capterra, App Store, Play Store.
  • Angry emails — the ones that never make it into Intercom.
  • Internal notes — changelogs, standup summaries, “we decided X” threads. These feed agent memory without becoming feedback.

Herald classifies each message on arrival: feedback, sales, internal_note, newsletter, or spam. Newsletters and spam are dropped; everything else lands in the right table in your Durable Object’s SQLite.

Your forwarded email lands in the right section of next Monday’s briefing — Feedback themes if it’s a customer complaint, a People row if the sender is someone you should talk to, or the Sales pipeline if it’s a call transcript. It also becomes searchable in chat the moment it arrives: ask “what complaints came up in this week’s forwards?” and Herald pulls it back with context.

Every attachment is kept and scoped to your Product; nothing crosses tenants.

  • Plain billing notifications. Herald already reads Stripe.
  • Two-factor codes or password resets. We don’t need them and we’d rather not store them.
  • Newsletters. Herald will classify and drop them, but forwarding them wastes your attention at the top of the forward queue.

Attachments and bodies live in R2, keyed by your product_id. Nothing cross-tenant. If you delete the Product, every forwarded email goes with it. See Where your data lives.