Consultation Booking Form Template

For advisors whose first meeting is the product — topic, format, time windows, and pre-reading documents collected before the clock starts.

Free · copies into your editor in one click
Live preview — try it, nothing is saved

Book a consultation with us. The more context you share now, the more of our time together goes to answers instead of background.

We reply confirming one of them — or the nearest thing the calendar allows.

Contracts, statements, reports — whatever the conversation will lean on.

A consultation has a strange economics: the meeting is billed by the hour, but its value is decided by what happened before it started. An advisor who walks in cold spends the first twenty minutes on background — a fifth of the engagement gone to throat-clearing. This form is the anti-cold-start: topic, format, timing, context, and the documents themselves, all collected while the calendar question is being settled anyway.

Why these fields. The time-windows question does scheduling the way professionals actually do it — the client offers two or three ranges, the advisor confirms one, done in a single reply. A slot grid would promise availability this form cannot verify, and precision here is false precision anyway: nobody's Thursday is bookable to the minute three days out. The background field is the highest-leverage 200 words a client will ever write; its placeholder steers them toward the three things every advisor needs (current state, attempts so far, desired outcome). The document upload turns "can you send that over before we talk?" — the email nobody sends in time — into a step inside the booking itself. Topic and format are short but structural: a second opinion prepares differently from a new matter, and in-person meetings need a room booked, not just an hour.

What we left out. Fee and retainer questions — money talk belongs in the confirmation reply, where you can frame it against what the person actually needs. Also identity documents and case numbers: ask for those once the engagement is real, not at the door.

Who uses this. Solicitors and accountants running paid initial consultations, financial planners and mortgage advisors, independent consultants whose discovery call is the funnel, and clinics offering assessment appointments — any professional whose hour is the product. Firms where several advisors share one intake filter the responses view by topic, so second opinions and new matters queue to the right desk without a triage meeting.

Make it yours. Rename the topic lanes to your practice areas, and consider password-protecting the form if it is meant only for referred clients — the password gate lives in Settings. Notifications matter more here than on most forms because consults are often urgent; switch them on so requests reach you the hour they arrive. Uploaded files are content-verified before download and stay attached to the response, so the brief and its documents never separate. If your intake grows, a webhook can hand each request to your practice-management tool the moment it lands.

Preparation is the differentiator. Two advisors of equal skill are separated by which one read the documents on Tuesday night. The ending promises exactly that — make it true, and referrals do your marketing from there.

Frequently asked questions

Why ask for windows instead of showing open slots?

Because this form does not hold your calendar — you do. Windows let the client state flexibility once, and your confirming reply picks the slot. One round-trip, no double-booking risk.

Is it safe to receive contracts and statements this way?

Files are validated against their declared type before you download them, delivered as attachments rather than rendered in the browser, and capped at 10MB each — a deliberately careful default.

Can we keep this form to referred clients only?

Yes — set a password in Settings and share it with the referral. The link stays private in practice, and everyone else meets a lock instead of your calendar.

Can requests flow into our practice-management system?

Add a webhook and every completed request POSTs to your endpoint in real time, signed so you can verify origin, with automatic retries if your system is briefly down.