An agency's onboarding form asks for a company name and website, then leaves the engineer to guess what the receptionist may book, quote, or promise. Those guesses become configuration and are difficult to recognise later.
A useful GoHighLevel onboarding form collects decisions the implementation actually needs, with an owner who can approve them.
Organise questions around one customer journey
Ask the client to describe a normal enquiry, the intended saved result, and the exceptions staff handle today. Request a few redacted or fictional examples rather than a large export of customer data.
| Form area | Decision to capture |
|---|---|
| Services | What the receptionist may explain or book |
| Calendars | Approved types, durations, staff, and fallback |
| Fields | Required facts and missing-data handling |
| Escalation | Destinations, hours, and no-answer policy |
| Approval | Named owner of wording and business rules |
Include explicit exclusions. “Answer customer questions” does not authorise invented prices, technical diagnosis, refunds, or unsupervised account changes.
Capture source ownership, not just source URLs
A website may be outdated. Ask which document or employee approves hours, fees, coverage, and cancellation wording, and who updates the source when those rules change.
Store a configuration version or review date for meaningful changes. That makes a later failed test traceable to the rules that were active at the time.
Do not ask clients to paste privileged credentials into a general onboarding form. Use the approved access process and record only the responsible administrator and connection status.
Turn answers into testable rules
“Usually book with the nearest available employee” needs clarification about location, eligibility, and exceptions. “Always pass urgent calls to a person” needs a destination and a policy for when nobody answers.
Return unresolved questions to the authorised client before treating the form as approved configuration. A submitted questionnaire is not equivalent to launch sign-off.
HighLevel's Voice AI setup guidance is useful for checking configuration requirements. Keep your form aligned with the current capabilities you actually plan to use.
Review the completed form through fictional calls
Run a normal booking, ambiguous request, missing field, failed transfer, and unavailable integration. Let the client inspect the resulting records and wording.
If a question on the form never affects a decision, consider removing it. If staff repeatedly need an answer the form never collected, add that question with a clear purpose.
Onboarding-form questions
Is the client's website sufficient approval?
Confirm the authoritative source and responsible decision-maker.
Should every field be mandatory?
Require only information necessary to define or operate the agreed scope.
What should the engineer receive?
Provide approved rules, open decisions, access owners, and acceptance examples in the project pack.