Review a forwarded inquiry before creating a client lead

Open CRM → Review forwarded inquiries. Paste the forwarded text or upload an original .eml email, then choose Save original for review. Saving only retains an encrypted original. It does not create a contact, verify an email address, subscribe anyone to messaging, send a reply, charge anything, or start a workflow.

Manual uploads remain available independently of the separate received inquiry email workflow. When receiving is configured and activated, provider-retrieved originals enter this same review queue. Neither path authenticates a marketplace named inside a forward, and neither automatically creates contacts or starts workflows.

Check the original before deciding

The parser can suggest clearly labeled fields from material asserting The Knot, WeddingWire or Zola. Familiar branding and quoted From headers are still operator-supplied assertions. They do not prove the material came from that marketplace or contact. Unknown formats remain available for manual review.

A received original additionally shows its verified provider receipt, address label and generation, and provider-supplied SPF, DKIM and DMARC observations (or their absence). Signed and retrieved destination fields must match one private address; this routing check is not independent proof of the SMTP envelope. A passing authentication result belongs to the email the provider handled, not every quoted sender or marketplace named inside it. These observations never establish customer identity or messaging consent. Manual originals retain their original operator-supplied evidence label.

The review page shows inert body text, selected header assertions, parser warnings, and the original line behind each suggested field. HTML scripts and remote images are never displayed or loaded. Attachments stay inside the retained original; this feature neither imports nor downloads their contents. Excessive MIME structures, malformed bodies, ambiguous numeric dates and conflicting values require manual review. The extracted text preview is limited to 100,000 characters; the complete admitted original stays encrypted.

For example, Budget: $425.50 appears as $425.50 USD (stored as exactly 42,550 cents), while Budget: EUR 900–1,200 remains unresolved. October 25, 2026 becomes 2026-10-25. A date such as 10/11/2026 is not guessed. Correct the values explicitly before previewing.

Choose one decision

• Create a separate new inquiry: check name, email, phone, date, location, guest count, USD budget and message. Optionally select a current project type and answer its private fields. Required conditional fields appear when applicable; hidden and unknown answers are discarded. Numeric zero and an unchecked optional checkbox remain real answers.
• Attach evidence to an existing inquiry: search active inquiries by name or email, select the intended record and write a reason. Its contact details and original acquisition source remain unchanged. This attachment counts as additional evidence, never as a new acquired inquiry.
• Dismiss and retain original: record a reason. No lead or acquisition source is created. The original and review remain available.

For a new inquiry, the saved review lists up to 20 exact name, email or normalized phone matches, including archived or merged records. This is a duplicate warning, not fuzzy identity matching. If matches exist, approval requires your explicit confirmation that this is a separate inquiry. When there are more matches, the review says so; inspect your records before proceeding. Nothing is merged automatically.

Preview and approve exact values

Preview exact decision saves the original parser output, corrected decision, selected project-type definition, current duplicate evidence and named operator together. Approve exact decision applies that saved review. Changing an editor field clears its prior review. Reviews expire after 24 hours and only their original named operator can apply them.

A changed contact, project type, capture revision or duplicate set requires a new preview. For received originals, acceptance also requires the same active receiving-address generation. Renaming, disabling or rotating that address prevents old originals from being accepted; they remain readable and can still be dismissed with a retained reason. Pausing new receiving or removing download credentials does not block decisions on already captured originals. Completed acceptance receipts and their sources remain valid after address changes. Access is checked again after waiting for record locks, including retries. Full current workspace members may use intake; contractors, shared-wedding collaborators and anonymous users cannot read its originals or apply decisions.

If a response is interrupted, use Retry the same original, Retry the same preview, or Retry the same approved decision. The frozen request returns its existing receipt instead of creating another item. A changed payload cannot reuse the same request. After a completed acceptance, open the linked inquiry and its original source receipt. The original, accepted review and corrected fields remain available even if the contact’s current details later change.

Acceptance emits an IDs-only intake.accepted domain event. It has no automatic workflow enrollment. An independently configured signed webhook can receive that event; it contains references, not the original email or contact message. Public-form and Radar conversion automation behavior is separate.

Limits, history and recovery

Each .eml original is limited to 1 MiB. Pasted text is limited to 100,000 characters. Intake admits at most 10 new originals per named operator per minute, and at most 1,000 originals or 128 MiB of original bytes per workspace. Encrypted encoding and retained reviews take additional database space. Each original admits at most 25 saved reviews, and each named operator may save 20 new reviews per minute. Existing exact review receipts and approval of a still-valid saved review remain available after these limits; the history offers an approval control for your own reviews. These are fixed admission bounds, not an overage charge; exact retries remain available after a limit is reached. Originals with decoding problems still count and remain available for manual decisions.

The accepted decision stays pinned beside the original, independently of review-history pagination. The library pages through 20 originals. Review history pages through five immutable saved reviews. Completed decisions cannot be reopened, silently reassigned or deleted here. Dismissing an item does not free storage.

If original or review verification fails, reading or applying it stops. Preserve backups and ask support to investigate; creating a replacement does not repair the original evidence. This increment has no original-file export, purge or erasure workflow. Retention, export, deletion and support policy must be completed during coordinated activation before live receiving is offered. Keep an independent original in your own archive while using manual intake.

A retained acquisition source can later be explicitly assigned to a project for invoice-principal attribution. Creating or attaching an inquiry does not make that project assignment, inherit it across clients, or claim collected revenue.