During a cost-reduction exercise, inquiry delivery was temporarily consolidated. A later task restored each site's previous configuration.

The September 7 follow-up recorded that all ten targets matched their original settings. The lesson was practical: where an inquiry goes belongs to the service contract, not merely to infrastructure cleanup.

I look again from the person's side of the inquiry

I expect an inquiry about my business to reach the right recipient. That ordinary expectation should survive an infrastructure change. I preserve the relationship before simplifying the connection.

Restoring an address was not enough

For dedicated Workers, the destination allowlist and recipient setting were compared together. Some older Workers also embedded the temporary address in source, so those specific Workers were redeployed from preserved code and configuration. Pages service bindings and secret bindings were kept.

I now expect one record to explain the site identifier, endpoint, email Worker, destination policy and sender verification. A public contact link and server-sent email are different mechanisms.

A non-sending diagnostic checklist

  1. Confirm that the form targets the intended site's server endpoint.
  2. Check that its service binding points to an existing email Worker.
  3. Compare destination configuration and the allowlist.
  4. Start with non-sending conditions such as GET, unauthorized requests or malformed input.
  5. When a live send is authorized, perform one clearly identified test and verify server acceptance separately from inbox arrival.

Keep historical configuration distinct from today's API

This case describes the configuration used at the time. Current Email Service documentation describes Workers bindings and sender/recipient restrictions. A new implementation should use current documentation rather than copying an old calling convention blindly.

Explore the implementation

Non-sending endpoint check

curl.exe -i -X GET ($siteUrl + '/api/register')
# Expect a clear 405 response for a POST-only endpoint.
# This does not prove that an email reached an inbox.

The limit of the recorded result

The restoration passed 46 automated tests, pre-deployment and binding checks, and non-sending live-path checks. No real test message was sent. Configuration restoration and non-sending validation are therefore the established outcomes.

A useful handover explains why inquiries cannot silently cross site boundaries and where to look when delivery fails.