Does Reply on a website enquiry email actually reach the customer?

Give each address a distinct responsibility

The sender identifies the source of the notification, the recipient receives it inside the business, and the reply address suggests where an answer should go. RFC 5322 describes Reply-To as the suggested reply destination; without it, the default is From. Read the technical definition. This distinction does not guarantee delivery. Check the actual behaviour in the email application your team uses.

Example: replying to an export enquiry

In an illustrative manufacturer workflow, an authorised website mailbox sends a notification to the sales inbox. The visitor’s submitted email is the reply address. A subject such as “Website enquiry · valve range · EN” provides context. Language, product and the visitor’s message appear separately in the body. When staff open a reply, they check the recipient before sending. An address entered on a form should not be treated as proof of a working mailbox.

Separate the internal notification from customer acknowledgement

The message to your team and the acknowledgement to the customer are different communications. If customers can reply to an acknowledgement, that reply should go to a monitored business inbox. Do not copy internal routing notes or other people’s contact details into the acknowledgement. In both Turkish and English, describe only the service and response timing your team can actually provide. Do not present an automated receipt as a personal assessment.

An acceptance test to give your agency

• Submit enquiries from two separate test addresses that you control.
• Check that each notification reaches the intended business inbox.
• Open Reply and read the destination before sending.
• Verify that the test response reaches the original test inbox.
• If a customer acknowledgement exists, test the reply back to your business too.
• Record mistyped addresses and missing email fields as separate failure cases.

Mask test addresses in shared evidence where appropriate. Do not use real customer correspondence as test material.

Assign responsibility for the conversation

A shared inbox alone does not establish who owns an enquiry. Document who responds, who provides cover and how completed requests are marked. Include the two-way test in launch acceptance, then repeat it when your form provider or mail settings change. We cover duplicate submissions separately in our form confirmation guide. This correspondence check can be an explicit deliverable in a website design project.

Use two rows in the handover note: “Internal notification reply goes to customer” and “Customer acknowledgement reply goes to business”. For each, record the expected inbox, test date and reviewer. This explains the setup when staff change. Receiving a test email and knowing that a real customer read a response are different outcomes; this test establishes only the former.