Meeting Templates for Internal Scheduling from Contact Records

HubSpot Ideas
1

When scheduling a meeting internally from a contact record (via the “Schedule a meeting” button), there is currently no option to use pre-configured meeting templates. Every time, the user must manually type the meeting title, set the duration, and fill in location details.

We would love the ability to create and save internal meeting templates that can be selected when booking a meeting from a contact record — similar to how meeting scheduling pages (external links) already have pre-set titles, durations, and locations.

Use case:

Our team frequently books the same types of meetings for clients (e.g., “Orientation Meeting,” “Follow-Up Call,” “In-Person Consultation”). Being able to select a pre-configured template from the contact record would save time and reduce errors.

Requested feature:

When clicking “Schedule a meeting” from a contact record, allow users to:

  1. Select from saved meeting templates
  2. Have the title, duration, location, and description auto-populate
  3. Only need to select the date/time to confirm

This would significantly improve our team’s efficiency when booking meetings on behalf of clients.

Upvote if this would help your team too!

2

This would definitely save time for teams that schedule the same meeting types every day, and it would help keep details consistent as well. I appreciate practical feature ideas like this, much like finding a reliable betqq.com download recommendation.

3

This would remove a surprising amount of manual drift. The template should also store the meeting type as data, not just paste copy: a stable template ID or activity property would let teams report on orientation vs. follow-up vs. implementation, trigger the right prep workflow, and audit changes to duration or location. While waiting for a native option, a CRM sidebar card or shared snippet can standardize the title and description, but reporting still stays fragmented. Native templates tied to activity metadata would solve both speed and downstream automation.

4

Exactly! We really need this feature as well!