---
title: "How to choose a good booking link name"
url: https://meet.barq.dev/guides/choose-booking-link-name
updated: 2026-11-17
author: "Hammad Ali"
---

# How to choose a good booking link name

> **Short answer:** Choose a stable name for your personal booking page and a short, purpose-based slug for each appointment. A pattern such as /[username]/project-review is easier to recognize than a string of dates or initials. Keep client details out of the URL, and test the full destination before putting it in public profiles.


## Which booking link name ideas stay clear over time?

Names based on a person and a meeting purpose tend to stay understandable as your offers change. Use an address you can say aloud, then put details that change often, such as price or a campaign deadline, into the page copy.


Keep it readable. A URL copied into plain text has no button label to explain it, so the final words should tell the recipient what kind of appointment opens.


| Illustrative pattern | When to use it | What to avoid |
| --- | --- | --- |
| /[username]/intro | A first conversation | Promising detailed consulting in the description |
| /[username]/project-review | Discussing existing work | Naming a confidential client |
| /[username]/office-hours | Scheduled access to one host | Implying a shared team rota |
| /[username]/portfolio-review | Reviewing material supplied beforehand | Adding a year that will soon be stale |
| /[username]/handover | Finishing an engagement | Internal project codes visitors won't recognize |

These are naming examples, not live addresses. Replace the bracketed username with your saved public username and use a slug that meets the editor's validation.


If the difference between an appointment address and a video-room address is still unclear, start with [what a booking link opens](https://meet.barq.dev/guides/what-is-a-booking-link). Naming a booking page "meeting-room" can send the wrong signal.


## How is a scheduling link URL built in the app?

In Barq Meet, an event URL uses the host's username followed by the event slug. We show that full address beside the event editor's Link field, so you can inspect the destination while choosing the final part.


Read both parts. A [vanity URL](https://meet.barq.dev/glossary/vanity-url) uses recognizable words; in this two-part address, the username identifies the host and the event slug identifies the conversation.


We expose the public username as Username in Settings and the appointment slug as Link in the event editor. Those are different fields, so changing a visible event title doesn't give you permission to assume the saved URL changed too.


The current validation accepts lowercase letters, numbers and hyphens, with a maximum of 60 characters for each of those two name fields. Reserved names are rejected, and a username must be available. These are acceptance rules, not a recommendation to use all sixty characters.


For a worked example, the event slug "project-review" is 14 characters: seven in "project", one hyphen and six in "review". That's enough to name the purpose without carrying the whole appointment description.


We also show the saved public URL in the sharing controls. Copy that address after saving instead of reconstructing it from memory.


## Should a booking URL include the duration?

Include a duration only if the link will keep offering that same length. If guests can choose several lengths, a purpose such as "review" stays accurate when a number like "30-min-review" would describe only one of the choices.


Think past launch day. A short introduction may start at fifteen minutes and later need twenty, while the reason someone books it remains unchanged.


We allow multiple durations on an event in Barq Meet. A link named "intro" can therefore offer the lengths you've configured, with the event description explaining which length to select.


If you choose a numbered slug anyway, test the booking page against it whenever you edit duration settings. Don't leave a thirty-minute promise in the address while the event offers only sixty-minute appointments.


A [booking page's title and description](https://meet.barq.dev/features/booking-pages) can carry more context than its URL. Use them for preparation instructions and the outcome a guest can expect.


## What should you avoid in a Calendly link name or another booking URL?

Avoid confidential information, ambiguous abbreviations and promises that the appointment page can't keep. A name should help someone recognize a destination; it shouldn't expose a client relationship or require the recipient to decode your internal naming system.


Keep secrets elsewhere. "Intro" is a purpose; a client name paired with a sensitive topic is information that can travel with a forwarded email or copied URL.


The phrase "Calendly link name" is often used for the same naming problem, but this guide doesn't document Calendly's editor or its URL validation. The examples are naming advice; the field names and rules above describe Barq Meet.


Also avoid naming one host's page as though it distributes appointments across a whole department. We don't offer round-robin or collective scheduling, so "team-demo" needs an explanation if it actually books one person's calendar.


Don't use tracking labels as the event name. Source tags can identify a placement without making every visitor's appointment URL a different public offer.


## How do you check a booking name before sharing it?

Open the saved URL as someone who hasn't used your dashboard, then compare the visible host and appointment with the words in the address. Say the URL aloud once; unexplained initials are easier to catch when you hear them.


Test the whole path. An attractive final slug can't repair a wrong username or an address copied from the editing screen.


| Naming problem | What a guest may think | Better next step |
| --- | --- | --- |
| Old date in slug | Offer has expired | Choose a stable purpose |
| Duration differs from page | Appointment length is uncertain | Align slug or duration |
| Internal acronym | Link's purpose is unknown | Use recognizable words |
| Previous username in a signature | Destination may no longer work | Replace and reopen the saved URL |

We haven't established an old-URL redirect guarantee here. After any rename, check the actual old and new destinations and update [the places you share your booking address](https://meet.barq.dev/guides/where-to-share-your-booking-link). 


Check [what a booking account includes](https://meet.barq.dev/pricing), then [choose a public name for your appointments](https://meet.barq.dev/app/sign-in).

## Steps

1. **Choose a stable public username**: Use a name you expect to keep using in signatures and profiles. Check that it identifies the person guests expect to meet.
2. **Name the appointment by its purpose**: Give the event a readable name that describes the conversation. Keep the URL slug short enough to recognize when copied as plain text.
3. **Edit Username and the event Link**: Review Username in Settings and Link in the event editor. Use the URL preview to check both parts before saving.
4. **Open the saved public destination**: Test the complete link in a private browser window. Confirm the host, appointment and offered durations before adding it to public profiles.
5. **Record where you share the URL**: Keep a list of signatures and pages carrying the link. If you rename it later, revisit each placement and retest the destination.

## Frequently asked questions

### Should I put the price in the URL?

Usually leave prices in the appointment description, where they can be explained and updated. A URL is harder to replace once it appears in old emails, and a price alone tells readers little about the conversation they're reserving. Keep changing commercial details in the description when the address needs to remain stable in signatures, proposals and documents you've already sent to clients.

### Can two appointments have similar names?

They can describe related conversations, but guests should still understand the difference. Use a purpose qualifier such as introduction or project review in the title and URL, then explain the scope beside the booking control. Use the purpose and expected length to distinguish them, and preview the public menu to check that a first-time guest can choose without guessing.

### Is a hard-to-guess link private?

No. A name that is difficult to guess doesn't establish access control. Anyone receiving or forwarding a working URL may share it further, so keep confidential client details out of the address and use the right sharing method. Share it selectively and review requests where needed, instead of treating an unusual path as authentication for anyone who obtains or forwards the address.

## Related pages

- [What is a booking link?](https://meet.barq.dev/guides/what-is-a-booking-link)
- [What is a vanity booking URL?](https://meet.barq.dev/glossary/vanity-url)
- [Booking pages that ask the questions you need answered](https://meet.barq.dev/features/booking-pages)
- [Where to share your booking link: 25 places that work](https://meet.barq.dev/guides/where-to-share-your-booking-link)
- [CST vs CDT: what's the difference?](https://meet.barq.dev/glossary/cst-vs-cdt)

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