A quick acknowledgment is useful when it tells the customer what happens next. It also needs a real process behind it so their inquiry gets answered.
Before you start
- A form or inbox that collects inquiries
- A realistic response window
- A team member or owner responsible for replies
The process
Collect only what you need.
Ask for the customer’s name, contact details, and the service they are interested in. Explain how you will use the details and collect the appropriate permissions for your contact methods.
Set an honest expectation.
Acknowledge receipt and tell the customer when to expect a personal reply. Use a response window you can meet, including outside working hours.
Assign the conversation.
Create a follow-up task for a named person. Give it a due time and keep unanswered inquiries visible. An automated acknowledgment should not mark the conversation as resolved.
Follow the test inquiry through.
Submit your own form, inspect the customer-facing message, and check that the task reaches the right person. Then test a repeat submission and an inquiry made outside business hours.
Make this your own.
Replace the bracketed details and adapt the wording to your business.
Hi [first name], thanks for contacting [business name] about [service]. We’ve received your message. [Your name or team] will get back to you by [realistic response time]. You can reply here with any extra details.
Test your setup
Use fictional customer details and your own test destinations before enabling a live workflow.
Track the time to a useful personal reply, not just the speed of the automatic acknowledgment.
Keep the details current.
This guide describes a process to adapt to your business. For current product controls, plan availability, and usage costs, consult the HighLevel Help Center and official pricing. This guide has not yet been verified in a live HighLevel account.