Forwarded enquiries: who should inbox automation reply to?
Keep the forwarder, prospective customer and approved reply recipient separate when an enquiry reaches your shared inbox through someone else.
For a forwarded enquiry, record who sent the message to your inbox separately from who appears to need help. Keep the reply recipient unconfirmed until a person checks the intended conversation. A useful summary can be ready before a safe external reply is ready. This guide gives small agencies an intake pattern for that gap.
Separate the message envelope from the business request
An account manager forwards a prospect’s question with “Can we help with this?” The incoming message is from the account manager, while the quoted text describes another person’s needs. Croissant recommends keeping three distinct fields: received-message author, proposed enquiry contact and approved reply recipient. Do not make one generic email field serve all three jobs.
RFC 5322 distinguishes the author in From, the transmitting agent in Sender, and the suggested reply destination in Reply-To. Those fields describe message roles; they do not decide who your business should contact about a forwarded request. [1]
Microsoft Graph exposes from, sender and replyTo as separate message properties. An Outlook integration should inspect the relevant properties rather than treating the visible display name as the whole routing decision. This is a provider-specific data model, not a guarantee about every inbox connector. [2]
A worked example: an internal forward becomes a review item
This is a synthetic example, not a customer story. Casey, an agency account manager, forwards a message to the operations inbox. The new text says, “Please assess this enquiry; I will introduce you if it fits.” The quoted message from Morgan asks whether the agency can prepare a weekly campaign summary. A signature below it belongs to a third person copied into an earlier conversation.
The intake produces case ENQ-17 with Casey as the forwarder, Morgan as a proposed enquiry contact, weekly reporting as the topic, and the operations lead as the review owner. The recipient field stays unconfirmed. The signature is retained only as source context where necessary; its presence does not make its owner a lead.
The proposed next action is an internal assessment for Casey. The workflow does not create an external acknowledgement to Morgan: Casey asked to arrange an introduction first. The reviewer can approve that internal handoff, request clarification or close the assessment. None of those decisions silently authorizes external contact.
If an introduction later arrives, link it to ENQ-17 and review the current participants and wording. Preserve the earlier forward as evidence of how the case began. Do not treat the old quoted text as a fresh direct message from Morgan.
Build an intake record a reviewer can inspect
Start with the received message reference, permitted conversation context, mailbox, received time and assigned owner. Show the new covering text separately from quoted material. If your connector cannot reliably distinguish them, label the boundary uncertain and let the reviewer open the original message.
For every proposed contact, retain a short reason: “named in quoted request,” “sent the covering message,” or “appears only in signature.” Keep a source reference beside the proposal. Extract only what the assessment needs; copying an entire forwarded chain into a broadly visible CRM note can expose unrelated correspondence.
Use statuses such as needs identity review, internal assessment ready and recipient confirmed. Keep these separate from draft approved and sent. The existing shared inbox triage guide explains category and queue ownership; this extra identity check belongs before contact creation or reply preparation.
Choose the next action before choosing an address
Ask the owner which conversation is needed now. An internal request for assessment may require an answer to the colleague. A permitted introduction may support preparing a draft for the introduced contact. A forward without enough explanation needs clarification. The model can suggest these paths, but a name or address extracted from the body is not authority to send.
For the pilot, require a person to confirm the intended To recipient and the exact draft. Start with no automatic CC or BCC. A change to the recipient, included quotation or attachment returns the draft to review. Keep pricing, contracts, delivery commitments and other commercial decisions with the authorized person.
Headers and quoted text can disagree, and neither a confident extraction nor a familiar display name settles identity. If the reviewer cannot establish the right participant, keep the case in the internal queue. Follow your organization’s approved verification process for suspicious messages instead of asking the model to improvise one.
Test the confusing cases before connecting CRM writes
Create fictional test messages for a direct enquiry, an internal forward asking for advice, a forward inviting an introduction, and a chain with several signatures. Add a message whose reply destination differs from its author and a forwarded message with missing context. These are acceptance scenarios, not claims that any particular provider misroutes them.
Inspect the proposed contact, reason, source excerpt, next action and recipient status for each case. The internal-advice example should stay internal. The ambiguous chain should pause. A repeated delivery should return to the same case rather than generate another lead. No test should produce an external send without the required review.
When identity is confirmed, apply your existing CRM handoff rules for matching and field updates. Keep unconfirmed people out of automatic contact creation. If the connector cannot preserve the evidence or enforce the review boundary, retain manual intake while the defect is repaired.
Keep the pilot narrow enough to learn from
Try one approved inbox and one internal review queue first. Track incorrect proposed contacts, recipient changes made by reviewers, cases waiting for clarification and the effort needed to resolve them. Review the underlying examples before expanding; a neatly filled CRM is not evidence that the right people were identified.
Ordinary mailbox rules and a manual review form may be enough for a low-volume queue. A custom workflow becomes worth considering when repeated forwarding patterns require interpretation and the evidence must reach an existing task system. Explore the inbox-to-CRM demo for context. To discuss a scoped build, describe the forwarding pattern and review owner through the contact form, using a fictional example rather than private correspondence.
Implementation checklist
- Separate forwarder, proposed enquiry contact and approved reply recipient.
- Show covering text separately from quoted material, with uncertainty visible.
- Attach source references to proposed identities and next actions.
- Confirm the intended conversation before creating a CRM contact.
- Require recipient and draft review; leave automatic CC and BCC off.
- Test internal forwards, introductions, multiple signatures and conflicting fields.
- Keep an internal clarification queue and manual intake path.
The sources behind the sauce.
Primary research and official documentation behind the cited points. The workflow examples and checklists are Croissant’s own guidance.