Welcome a new salon guest
A copyable first reply that gathers the details you need from a guest before the next conversation.
Email copyMake it yours
Salon consultation request page
An editable HTML landing page for guests to understand the next step and request a conversation.
Standalone HTML design. Use the custom-code version inside a page, or the full file on your own host. This is not a native funnel or snapshot import.
From template to useful
Put it to work.
Personalize the content, add it to your account, and test the complete experience before a customer sees it.
Read the setup guide- 1
Personalize the business name, service, and real booking URL.
- 2
Use the HTML as a standalone page or adapt its body/styles in a custom-code element.
- 3
Test the link and phone layout before publishing; this is not a native funnel snapshot.
A clear starting point
Before you use this.
Use standalone HTML or a scoped Custom Code block.
You’ll need
- Your existing booking/contact page URL.
- A page host, or access to a HighLevel page where you can add Custom Code. For HighLevel, add a section and row, insert a Code element, then paste the scoped Custom Code export.
Make it work for your business
- This design links to your existing booking process. It does not collect requests or include a form/calendar backend.
- This is HTML, not a native drag-and-drop funnel or snapshot. Use Preview Custom Codes and the page preview to inspect it, then save and reopen the same page. Check the layout and booking link before publishing.
What has been checked?
The generated files for this version passed local content and personalization checks on . These checks cover the file output; they do not verify an import, a sent email, or a business result.
Full HighLevel account testing is incomplete.
- HighLevel: custom page codeSource reviewed
Original content, ready to adapt.
You may customize these free resources for your own business or client work. Do not resell the original files as a competing template library. Illustrations and copy are examples, not promises of results. Account behavior and email rendering still need testing.
How we create and check resources