Two messages from one submission. The prospect's acknowledgement is composed in the same place as every other prospect-facing email so it shares their voice and card layout, and carries the booking reference. The internal notification lists name, company, email, phone and whether SMS and promotional consent were given, with reply-to set to the prospect.
Also called: thanks for your enquiry · auto reply · confirmation email
- 1The acknowledgement copy is built by the shared prospect email module and rendered in the shared appointment chrome.
- 2It is sent through the customer messaging path for the agency organisation.
- 3The internal notification is rendered and sent without blocking the response, to the onboarding notification address.
- 4Both are best-effort — a notification failure must never cost the lead.
- 5The on-screen confirmation changes depending on whether SMS consent was given and a phone number provided.
The copy was moved into the shared module after a concrete formatting failure recorded in the route: "the inline body it replaced wrote its rows as padding:0 0 12px 0 — vertical rhythm, no side padding — so the text ran hard against both edges of the white card." And the overall rule is stated in the same file: "Best-effort — a notification failure must never cost us the lead."
- Enquirers received no confirmation.
- The acknowledgement was formatted separately from every other prospect email and looked it.
- The team had no notification carrying the consent state.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →