An automated inquiry reply should confirm what was received, explain what happens next, and give a real route for help. Identify it as automated, and only promise a reply time your business can meet.
A request for a quote isn’t a confirmed booking. A completed poll isn’t permission for every future promotion. The message should match the action the person just took.
1. A service inquiry acknowledgment
Template to adapt to your actual process:
This is an automated confirmation from [business]. We’ve received your inquiry about [service]. [Team or person] will review it during [working hours], and we aim to reply by [realistic time]. To correct your details or add information, [working contact route]. This message doesn’t confirm a booking or price.
Keep personal information out of the message unless it’s needed to identify the request. Don’t echo private form answers into an email unnecessarily.
2. A poll confirmation
Thanks for answering our question about [topic]. This is an automated confirmation. Voting closes [date]. [Explain where the result will appear, or the update they specifically requested]. Your response doesn’t reserve a place or order an item.
Use only the update route the form actually offers. If there is no email update system connected, direct people to the page where you’ll publish the result.
3. An optional newsletter confirmation
You asked to receive [newsletter name] from [business], covering [subjects] about [frequency]. Confirm that choice at [confirmation link]. If you didn’t request it, you can ignore this message.
Use this only with a working confirmation flow. Send the ongoing newsletter after confirmation, and keep a record of the person’s choice. A poll submission alone shouldn’t trigger this message unless the person also selected the newsletter option.
4. A request received outside working hours
This is an automated reply from [business]. Our team checks inquiries during [days and hours]. We’ve received your message and will [actual next step]. If you need to change or withdraw the request, [contact route]. [Relevant alternative contact, only if you provide one].
Avoid “someone is looking at this now” if nobody is. If the business has no urgent service, leave urgent-response promises out of the template.
Test the whole route
Submit a test inquiry from a phone. Check that one acknowledgment arrives, its links work, the reply reaches a monitored inbox, and staff can find the request. Submit twice to see whether the same person could enter a duplicate follow-up sequence.
Change the owner, hours, or reply estimate in one maintained place so old promises don’t stay in a forgotten message. Keep approvals in a short review process when changing public copy.
Follow-up questions
How quickly should the automated message arrive?
Send it after the action is successfully recorded. Don’t confirm receipt before the submission succeeds.
Can the reply offer another service?
Keep the acknowledgment focused on the request. If you offer marketing updates, make the choice clear and respect it in the follow-up process.
Does a confirmation replace a staff reply?
Only when the person’s task is complete. An inquiry that needs a quote, appointment, or explanation still needs the next step you described.
