A customer books a time with your team. The appointment is on the calendar. Then someone has to call back because the details needed to do the job never made it into the booking.

That's a small gap with a cost: another interruption, another handoff, and a customer repeating themselves.

If your team creates service or rental bookings inside HighLevel or Wolf Pack Mentors CRM, today's update gives them a better way to capture those details when they make the booking. HighLevel's booking-form announcement explains the change.

The booking is only useful if the next person has the information

Online booking pages can ask customers to complete a form, but a booking made by a staff member in the app could follow a different path. The time might be reserved while the answers sit in a notebook, an email, or somebody's memory.

HighLevel now lets your team attach and fill out a form while creating a service or rental booking in the app.

The form configured for that booking is selected automatically, though staff can choose another available form.

The customer's basic contact details are prefilled from the contact record, and the completed form can be viewed from the appointment details afterward. Those are the functions HighLevel describes.

This does not mean that every calendar appointment now has the same option. The release names service and rental bookings specifically. If your business only uses other appointment types, ask your CRM support person to confirm whether this update applies before changing your process.

Make the intake useful, not longer

The point is not to turn a quick booking call into an interrogation. Ask for the few details the next person genuinely needs to prepare for the meeting and serve the customer well.

For a service appointment, that might mean the type of work requested, a useful location detail, or a note about access. For a rental, it might mean the item and timing requirements. These are examples, not new fields HighLevel created for you. Your business decides what belongs in its form.

Give the person who owns your booking process one clear question:

When we book a customer on their behalf, does the person doing the work get the same essential information as they would from an online booking?

If the answer is no, this update is worth a controlled test.

Test the handoff before changing the live routine

Ask your CRM person to create a test service or rental booking for a test contact.

Have them complete a short intake form, then open the appointment and confirm that the answers are visible to the right team member.

Check the customer name and contact details, too. They are prefilled, but a wrong contact record can still create a wrong handoff.

There are two limits worth knowing. HighLevel says the form can be attached only when the booking is created; staff cannot add or edit it afterward through this flow.

HighLevel also says CAPTCHA, product-selling, and payment elements do not appear in the in-app form. If your booking depends on a payment step, confirm that your existing payment process still happens separately. See the release details.

Have the team decide who checks the information, where corrections go, and which questions should stay off the form for privacy. Do not collect sensitive details just because a field is available.

Then ask for the result.

Did the right person receive what they needed without needing to chase down more info?

That's the standard that matters to your customer and your team.

Other updates from October 22, 2026

Filter HubSpot Records Before You Import lets a business moving from HubSpot preview and filter Contacts, Deals, Companies, and Tasks by created or last-modified date before import.

It only matters if you're planning a migration; if not, you can set it aside.

HighLevel notes that “In the last” excludes today, so a migration test should check its date range before anyone imports live data.

A booking on the calendar is a start. Make sure the next person has what they need to keep the promise behind it.