NearSync Help

Booking Engine

Sharing and Embedding The link, three ways to put it on a website, and where it actually gets used.

A meeting type is useless until somebody can reach it. There are two ways: a link, and an embed.

Every meeting type has a public address built from its slug. Short, readable, and safe to put anywhere.

Choose the slug carefully and then leave it alone. It appears in the link, so changing it breaks every copy already in circulation: in signatures, in old emails, on printed material. Renaming the meeting type is fine; renaming the slug is not.

In rough order of how much work each does.

Your email signature. The highest-value placement by a distance. Every email you send becomes a way to book, at no cost and with no maintenance.

Directly in conversation. "Here is my calendar" ends a scheduling exchange that would otherwise take four messages.

On your website, though usually as an embed rather than a link.

In a campaign, with attribution set on the meeting type so bookings count toward it.

Embedding

The booking page can sit on your own website in three shapes, each a snippet you copy and paste.

Inline

The booking page appears in the page itself, as part of the content.

Best for a dedicated booking page. The visitor arrived intending to book, and putting anything between them and the slots is friction.

A button opens the booking page over the page.

Best for a page with another job. A pricing page or a product page where booking is one option among several.

Bubble

A floating control in the corner, present on every page it is added to.

Best as a persistent offer, and the easiest to overuse. A site with a chat widget, a cookie banner and a booking bubble has three things competing before the visitor has read anything.

Choosing

One embed per page. Two ways to book the same meeting on one page is a decision the visitor did not need.

Inline where booking is the point. Popup or bubble where it is an option.

Test on a phone. A bubble that covers the navigation on a small screen is worse than no bubble.

Removing an embed

Deleting the snippet from your page removes the widget. Nothing is left behind and the meeting type keeps working through its direct link.

Worth knowing before a website redesign: the embed is a few lines of markup rather than an integration, so it can be moved, duplicated across pages, or dropped without touching anything in the platform.

Which to reach for

A short decision, because most people over-think it.

One page whose job is booking? Inline.

A page with another job? Popup.

Every page, as a standing offer? Bubble, sparingly.

Not sure? The link. It works everywhere, needs no page changes, and outperforms a poorly placed embed.

What the visitor sees

The meeting type's title and description, the context questions if you configured them, your real availability in their time zone, and a short form.

They do not see your calendar, your other meetings, or anything about the rest of your organisation. Availability is exposed as free slots and nothing else, which is the same boundary applied everywhere else in the platform.

Internal meeting types

A meeting type marked internal is kept off any public listing while its link keeps working.

Right for something you share deliberately rather than publish: an escalation slot for existing customers, an interview link. Anybody with the link can still book, so treat it as tidiness rather than privacy.

Worth its own note because it is the highest-return placement available and almost nobody sets it up.

Every email your team sends carries it. There is no page to build, no campaign to run and nothing to maintain. A team of ten sending forty emails a day is four hundred daily opportunities to book, at a one-time cost of two minutes each.

The wording matters slightly. "Book a 30-minute call" performs better than "My calendar", because it says what is being offered and how much it costs.

Where the page lives

The public booking page is served from your organisation's website domain rather than from inside the application, and the embed script comes from the same place.

That matters for two reasons. It looks like you rather than like a third-party tool, and a visitor who inspects the link before clicking sees a familiar address, which measurably affects whether they click at all.

Attribution

Where a meeting type is tied to a campaign, bookings through it are counted toward that campaign.

Worth doing whenever a link exists because of a campaign, because it closes the loop that most marketing measurement leaves open: not clicks, not visits, but meetings.

Testing an embed

Two checks, both quick, and both catching things that are invisible from the editor.

Load the page on a phone. Bubbles and popups behave differently on small screens, and a control covering the navigation is worse than no control.

Book a slot yourself, all the way through, from the embedded version rather than the direct link. Embeds sit inside your site's own styling, and occasionally something in that styling interferes.

Do it once when you add the embed, and again if your website is redesigned.

Do not gate it

A booking link behind a form asks somebody to do two things where one would do, and the form loses more people than it qualifies.

If you need to know something, ask it in the context step, after they have decided to book. That is the same information at a fraction of the cost, and it is the whole reason the context step sits where it does.

Making it work

One link, everywhere. A single well-placed link outperforms an elaborate embed on a page with little traffic.

Say what it is. "Book a 30-minute intro call" converts better than "Schedule".

Check it yourself, in a private window, after any change. It is thirty seconds and it catches the slug you renamed and forgot about.

Do not gate it. A booking page behind a form asks somebody to do two things where one would have done.

5 minUpdated 28 July 2026

Did this answer your question?

No, ask a person