URL Parameters: Prepopulate Booking Page Form with Invitee Information

Modified on Wed, 17 Jul at 10:35 PM

Leadmonk provides a feature that allows you to prepopulate the booking page form with invitee information using URL parameters. This means that when you send your Leadmonk booking link to an invitee, you can have Leadmonk automatically display information that's specific to your invitee on your booking page such as their name, email address, mobile number and pre-populated answers to custom invitee questions. 


Example of something you might add to a link

Example of a pre-populated booking page

 

To prepopulate the booking page form with invitee information, follow these steps:

  • Copy the booking page URL.
  • Add URL parameters (mentioned in the below section) to the end of the booking page URL to prepopulate the form fields. 
  • Send the booking page URL with the added URL parameters to your invitee.

Note: Make sure to use the correct field IDs and format the URL parameters correctly. Also, keep in mind that the prepopulated information will be visible to the invitee on the booking page.


By following these steps, you can prepopulate the booking page form with invitee information using URL parameters on Leadmonk. This can save time and provide a personalized experience for your invitee




Information you can add to your Booking link

Full Name 

Adds the invitee's full name as a single field on the booking page.
E.g.: name=Roger%20Smith

First Name and Last Name

Adds the invitee's first name and last name on the booking page.

E.g.: name=steve&last_name=johnson

 

Email

Adds the invitee's email address.
email=RogerSmith@ldmk.io

Email or Mobile

To choose between email and mobile to book an appointment

option=Mobile to book using just the mobile number

option=Email to book using just the email


Custom question responses

Pre-populates responses to custom questions. Just specify the question number (e.g. "a1", "a2"...) followed by the response. To specify multiple questions, separate the numbers by &.
Ex: a1=melrose%20technologies

Checkboxes and radio buttons

Selects a checkbox as a default value. Specify the question number  (e.g. "a1", "a2"...). To specify multiple checkboxes, separate the numbers with commas.

Ex: a3=2,3


Additional guests

Pre-populates additional guest emails. 

Ex: guests=janedoe@acme.com,johndoe@acme.com,...



Setting Default Month for Booking Page

You can now easily set a default month to be displayed on your booking page whenever it is opened. This feature is particularly useful when you are publishing appointment slots for an event or webinar in the future and want to make it easy for your customers to book an appointment.


To set a default month, you can use URL parameters. At the end of the event type URL, add a string in the format "?start_date=YYYY-MM". For example, if you want to show the availability for June as a default, you can use the URL: https://ldmk.io/steve/webinar?start_date=2023-06.


Note: Replace "ldmk.io/steve/webinar" with your own booking page URL.


By using this URL format, your customers will be directed to your booking page with the specified month set as the default. This will save them time and make it easier for them to book appointments for your event or webinar.




Capturing SDR (Booker) betails in meetings

Make use of parameter ld_ref to capture booker (SDR/BDR) details whenever a meeting is booked by booker(SDR/BDR) for a sales director or an account executive. You can pass any value to this parameter, such as the SDR's name, email address, or any other string that helps identify them.


Here's an example of how to use it: https://demo.ldmk.io/melrose/discoverycall?ld_ref=steve_smith


The SDR details will then be displayed as part of the meeting information within the Leadmonk app. You can easily download this data to Excel and track how many meetings are booked by your SDR team.


image.png


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article