How to choose
a Votel snapshot.

Start with a specific journey: a repair inquiry becomes an assigned service request; a prospect books a discovery call; or an estimate receives a recorded decision. “Automate the business” is too broad to guide the build.

Write down the starting event, the person responsible and the successful end state. An appointment request and a confirmed appointment are different states. A form submission alone should not imply availability or acceptance.

Capture only the context the next person needs. An HVAC dispatcher needs request type and service location. A restaurant coordinator needs date, party size and whether the inquiry is for a table or an event. An agency needs project scope and whether the requester is an existing client.

For each question, identify where the answer will be stored and who uses it. If the answer does not affect routing, scheduling or the handoff, reconsider whether it belongs in the first form.

HVAC intake guide → · Restaurant intake guide → · Agency intake guide →

A page layout helps a visitor understand the offer. The complete journey also needs a destination for form answers, a responsible team member, a booking or callback path, and an exit from follow-up.

• Page or funnel: what the visitor sees and which action it asks them to take.
• Intake and CRM: where the inquiry and required context are recorded.
• Routing: who receives each type of request, including exceptions.
• Scheduling: how availability is checked and confirmations are issued.
• Follow-up: what happens next and what stops it.

Plan the website-to-workflow connection →

List what should happen when a request is outside the service area, the team is unavailable, a required answer is missing or someone submits twice. Decide who reviews requests that cannot follow the normal path.

For appointments, cover rescheduling and cancellation. For sales follow-up, cover replies, acceptance, decline and requests to stop. These cases tell you more about the required build than a list of automation names.

Use the proposed HVAC setup checklist or Solar Lead Engine planning guide as an example. Both snapshots are still coming soon.

Before choosing a planned build, answer these questions with the team that will operate it:

1. What starts the journey, and what counts as a successful outcome?
2. Which request types, locations and business hours are supported?
3. Which intake fields are required, and where should each answer go?
4. Who owns each request type, and who handles unassigned requests?
5. Which calendar or callback process controls availability?
6. What starts follow-up, and which events stop it?
7. Which account-specific connections and settings will need configuration?
8. Which normal and exception paths must pass a test before launch?

If you are moving an existing HighLevel setup, document its current behavior first. A matching template name is not evidence that every asset or integration transfers. Use the migration planning guide →