Receive inquiry emails for review

Open CRM → Review forwarded inquiries → Receiving addresses. A private receiving address puts an original email in your intake queue so a named workspace operator can review it. Receiving an email does not create a contact, reply to the sender, subscribe a phone number, start a workflow, or assign a source to a project.

Live receiving remains unavailable until the coordinated activation checks pass. A configured address or a successful local demonstration is not evidence that real mail is being received. The dashboard identifies inactive configuration. You can continue to save a pasted forward or original .eml manually.

Address access and changes

Only current workspace owners and administrators can create, reveal, or change receiving addresses. Full workspace staff may inspect the safe address labels and their workspace’s delivery records. Contractors, shared-wedding participants, and members of another business cannot use these private records.

Treat the complete address as a private receiving capability. Share it only with the systems or people you deliberately want to forward into your workspace. Address labels and delivery summaries do not disclose its secret token. Revealing the address is a separate authorized action; it is not included in source summaries or analytics.

Disabling or rotating an address stops unfinished receipt work and new acceptance for its previous generation. Re-enabling it does not revive old work. Originals already retained remain visible as evidence, including those that need attention. Accepted sources and their financial attribution remain readable after the address changes.

Receipt, original, and accepted inquiry

These are separate milestones:

1. A receipt is recorded. A verified callback identifies an email received by the configured provider account. It is not yet a retained original or an accepted inquiry.
2. The original is retrieved. The worker checks the complete destination evidence and retrieves the provider’s exact original email within the size limit. When successful, the delivery links to a retained original in the review queue.
3. An operator accepts a decision. Open the original, check the extracted suggestions, and explicitly create a separate inquiry, attach evidence to an existing inquiry, or dismiss it while retaining the original. Preview and approve the exact decision through the existing review flow.

An email addressed to different private conversations, households, or intake addresses is rejected rather than copied between them. A receipt cannot be routed into multiple private workspaces. The provider’s received_for field is treated as header-derived conflict evidence; it does not independently prove the SMTP recipient. Unknown or malformed reserved destinations do not fall through to another private inbox.

What provider evidence proves

The receipt and original are tied to the configured receiving account. That establishes how the material entered this workspace; it does not authenticate an embedded marketplace, couple, quoted sender, or phone number. Provider authentication observations, when available and supported, are shown separately. Unknown observations remain unknown. A forwarded Authentication-Results, From, SPF, or DKIM header is not promoted to trusted evidence.

For example, a received email may contain The Knot inquiry, Name: Inez Hart, and Budget: $650. The review can suggest Inez and 65,000 cents, but a person must still confirm the details and choose how to use the message. Forwarding the same email twice is not proof that two separate clients exist. Delivery retries for the same provider email reuse their existing receipt; a genuinely different provider email remains a separate original that can be reviewed for duplication.

Recovery without duplicate originals

The delivery page shows whether it is waiting, retrieving, retained, held, or rejected, together with the available next step. A provider outage or expired temporary download address can be retried against the same received-email identity. A conflicting original, invalid destination, revoked address generation, or exhausted admission limit must not silently become a different delivery.

If an action’s response is interrupted, use its Retry the same request control. The original command stays frozen while its result is uncertain. A successful retry returns the durable result rather than creating another address or original. Reloading a delivery shows the committed worker result after a lost response.

When the provider no longer supplies the exact original, save a copy from your own archive through manual intake. That is separately labeled operator-supplied evidence; it does not repair or impersonate the provider receipt. No email links or remote images are followed, and attachments remain inside the original rather than becoming public downloads.

An outage can also hold a receipt before its private destination is classified. It will not yet appear as a workspace delivery. After support resolves the configuration, outage, or capacity problem, an authorized provider operator can replay the exact original email.received event from Resend’s webhook dashboard. Wait at least 60 seconds after the hold, keep the webhook enabled, and use an event still within the provider’s retained replay window. An eligible replay reopens the same receipt while preserving its original account, evidence, and attempt history; it does not require another email or a manual database reset. Conflicting source evidence and invalid destinations cannot be reopened this way. Resend supports replaying both successful and failed webhook deliveries. Provider replay documentation, replay API and retention requirements.

Limits and retained evidence

Original emails are limited to 1 MiB each. Manual and provider intake share the workspace cap of 1,000 retained originals or 128 MiB of original bytes. Dismissing an original does not free that retained capacity. Arrival limits and provider failures can hold or reject new retrieval; they do not authorize paid overages.

Originals, saved reviews, and accepted source evidence remain retained under the intake policy. Cleanup of unfinished jobs or temporary receipt details is not complete erasure of an accepted original. The current intake workflow has no original-file export, purge, or erasure command. Retention and support policy, receiving-domain configuration, account and signing-key bindings, provider download behavior, workers, and recovery rehearsals must pass during final activation before live receiving is offered.

Selecting a questionnaire or starting a follow-up workflow is a separate product workflow. This receiving flow sends no automatic response or questionnaire. Project attribution still requires its own explicit source assignment.