---
title: "Event type names that get booked: examples"
url: https://meet.barq.dev/templates/meeting-name-examples
updated: 2026-11-17
author: "Hammad Ali"
---

# Event type names that get booked: examples

> **Short answer:** Meeting type names should tell guests what they'll do with you, using words they recognize before they book. Put the purpose first and the duration in the duration selector or description. The six examples below pair a copy-paste name with preparation wording; none promises a result you can't guarantee.


## What makes meeting type names clear before someone books?

A clear meeting name identifies the conversation's purpose without making the guest decode an internal label. "Project scope discussion" tells a client more than "Session B", while the description can explain the material to bring and the decision you hope to make during the appointment.


Start with the task. A duration helps people plan, but "30-minute call" still leaves them wondering whether they're booking support, a sales discussion or a project review.


We recommend checking names from the guest's perspective: would they know which appointment to select without asking you? If two options sound interchangeable, describe their different purposes before adding another event.


The [booking page controls](https://meet.barq.dev/features/booking-pages) cover the surrounding description and questions. You can find other ready-to-edit wording in the [template library](https://meet.barq.dev/templates); the names here are a starting point for appointments you already intend to offer.


## Which meeting name examples can I copy?

Copy a name only when it describes what you provide, then replace the bracketed topic and preparation details. These meeting name examples pair a short public label with an email-ready description, so the appointment and the invitation make the same promise to the person booking.


Avoid guaranteed outcomes. A discussion can review options or agree an action; it can't promise a contract, a job offer or a solution before you know the problem.


### Introduction: when the visitor is deciding whether to work with you


```text
Event name: Introduction to [Service or project]
Description: We'll discuss what you need from [Service] and whether a further conversation makes sense.
Preparation: Bring your main question about [Topic].
Email line: You can book an introduction here: [Booking link].
```


Use this before a working relationship exists. "Introduction" keeps the promise modest; replace it with a more detailed label once the visitor is booking work you've already agreed to do.


### Scope discussion: when a project needs a defined next step


```text
Event name: [Project] scope discussion
Description: We'll review [Brief or requirements] and agree the next step for defining the work.
Preparation: Share [Document] before [Deadline].
Email line: Choose a time to discuss the scope: [Booking link].
```


Choose this when scope remains open. It doesn't promise that you'll deliver a full estimate during the call, so add that promise only when you have the information and authority to honor it.


### Progress review: when both sides know the project


```text
Event name: [Project or milestone] progress review
Description: We'll review [Deliverable] against [Agreed criteria] and record the actions needed next.
Preparation: Read [Review document] and add comments before [Deadline].
Email line: Book the progress review using [Booking link].
```


Use this for continuing work. Keep the project placeholder generic on a public page if naming the client or milestone would disclose information to people who receive the URL.


### Technical help: when a visitor has a reproducible problem


```text
Event name: Help with [Product or task]
Description: We'll examine one problem and agree what to try next.
Preparation: Bring the steps you've tried and any non-sensitive error message.
Email line: Reserve a help appointment here: [Booking link].
```


Choose this for troubleshooting you can provide. A label such as "Fix your problem" promises more than a timed conversation can establish; the next-attempt wording gives you an honest stopping point.


### Feedback: when the guest brings something to review


```text
Event name: Feedback on [Work type]
Description: We'll discuss [Selected section] and identify the revisions to attempt next.
Preparation: Send [Work sample] by [Deadline] with the question you want answered.
Email line: Choose a feedback slot: [Booking link].
```


Use this for a draft, portfolio or other work sample. Name the type of feedback you offer so a visitor doesn't mistake an informal review for a formal assessment or approval.


### Planning: when the appointment exists to agree upcoming work


```text
Event name: Plan [Next stage or task]
Description: We'll agree priorities for [Period or stage] and name the next actions.
Preparation: Review [Current plan] and bring any changed constraints.
Email line: Arrange the planning conversation here: [Booking link].
```


Use this when attendees can commit to actions. If the meeting only gathers ideas, call it a discussion and avoid implying that a final plan will exist by the end.


## When should a meeting name include its duration?

Include the duration in the name when it distinguishes two appointments people would otherwise confuse, and keep it consistent with the actual booking options. If a single event offers both 15 and 30 minutes, a title that says "15-minute review" becomes misleading when someone selects the longer choice.


Check every duration choice. We support several durations on one Barq Meet event, which lets you keep "Project review" as the name and describe what each length allows. Check [hidden events and direct-link access](https://meet.barq.dev/glossary/secret-event-type) before using a private client page as though it verifies the visitor's identity.


| Meeting name | What the guest still needs to know |
| --- | --- |
| Introduction to [Service] | Whether this is an initial discussion or paid work |
| Feedback on [Work type] | What to submit and how much you can review |
| [Project] progress review | Which deliverable and decision the review concerns |

For a suggested 30-minute progress review, you might reserve 5 minutes for context, 20 for the deliverable and 5 for actions. That explains the time commitment better than a title padded with several adjectives.


## How do you apply a meeting name template in the editor?

Paste the chosen name into "Event name" and the supporting copy into "Description" in the event editor. Treat the booking link as the next action in an invitation email; once a guest has booked, the confirmation should direct them to the appointment's joining details instead.


The fields do different jobs. We keep "Link" separate from "Event name", so a new title doesn't require you to rewrite the URL field as part of this naming exercise.


1. Pick the name that describes the appointment's actual purpose.
2. Match its description and offered durations to that purpose.
3. Add only the questions needed before you can prepare.
4. Open the guest page and check that a visitor can choose confidently.


The [guide to questions before a meeting](https://meet.barq.dev/guides/ask-questions-before-a-meeting) helps you move preparation requests out of the title. We also let you edit booking email content under "Notifications"; those messages are sent through the platform with the host as Reply-To, so an invitation doesn't need to claim it comes from your mailbox.


Check [the included event settings](https://meet.barq.dev/pricing), then [name and publish an appointment](https://meet.barq.dev/app/sign-in).

## Frequently asked questions

### Should I put a client name in a public event title?

Use a generic appointment purpose for a public booking page. A client name can expose a relationship to anyone who receives the link; put private account context in your normal records or in a message intended for that client. Use a neutral purpose for a publicly listed offer and put client-specific context in the agreed private conversation, instead of exposing the relationship in a title anyone visiting the page can discover.

### Is a creative meeting name better than a descriptive one?

A descriptive name is the safer starting point when visitors don't know you. They need to recognize the appointment before reserving time; a private team nickname can work internally when everyone already understands what happens in that meeting. Choose a name a first-time guest can interpret without help, adding personality only if it doesn't obscure the purpose, expected length or distinction from another appointment in your public menu.

### Can I advertise two lengths under one meeting name?

Yes, when both lengths describe the same kind of conversation and you explain what each allows. Barq Meet supports several durations for an event, so the title can name the purpose while the duration choice carries the time commitment. Keep the duration choices clear when both lengths describe the same conversation, with another event when the longer option requires a different agenda or preparation that the shared name would conceal.

## Related pages

- [Booking pages that ask the questions you need answered](https://meet.barq.dev/features/booking-pages)
- [How to ask guests questions before a meeting](https://meet.barq.dev/guides/ask-questions-before-a-meeting)
- [Free scheduling, with every feature included](https://meet.barq.dev/pricing)
- [What is a secret event type?](https://meet.barq.dev/glossary/secret-event-type)

[Create your free booking link](https://meet.barq.dev/app/sign-in)
