Share your Beacon
Three ways a client can see your availability, all reading the same published snapshot. None of them needs an account to look at.
The page
Your Beacon lives at an address built from your username. It is rendered on the server, so it works with JavaScript switched off, and it can be linked, crawled and previewed like any ordinary web page.
It shows:
- Your published percentage and status, as a ring.
- Your next opening date, when there is one.
- How recently the figure changed.
- Your display name and profile photo.
- Anything you chose to add: a short bio, testimonials you typed in, an accent colour, a call-to-action button, a “currently booking for” banner.
- A waitlist form, if you have one.
Two of those are opt-in and need setting up. The call-to-action button appears only when you have given it both a label and a link, and the link must be an ordinary web address or an email address - nothing else is accepted. The capacity confidence phrase - “Comfortably available”, “Limited availability”, “Nearly full” - is off unless you switch it on, and it carries no numbers.
The badge
A small pill you can paste into your own site, showing the same status and, when there is one, the same next opening date. It is the answer sitting on the page a client already landed on, rather than a link they have to follow.
Work setup has the snippet ready to copy, under the Beacon tab. If somebody else builds your site, Embed the availability badge is the page to send them.
The link preview
When your Beacon URL is pasted into a message, a chat app or a social post, the preview image is generated from your live status - a 1200 by 630 card carrying your name, your status and your next opening date. You do not have to do anything for this; the page already points at it.
All three show the same thing
This is a property rather than a promise. The badge and the share card read the published snapshot through the same code the page does, so the badge can never reveal something your own page does not. There is no configuration that makes one more detailed than another.
There is also no privacy dial. Your Beacon renders one complete public view for everybody who visits it - which is why it matters that the view itself carries no client names, no job titles and no raw hours.
What happens to the people who look
No account is needed to look, and no sign-up wall stands in front of it. There is no view counter anywhere in the product - not for you, not for anyone - so if you want to know whether a client looked, you will have to ask them. Nothing you can see tells you.
The only thing a visit can leave behind is something the visitor did on purpose: joining your waitlist. That reaches you as an entry, and Run a waitlist covers what it holds.
The page is rendered entirely outside the signed-in part of the app, so someone reading it never loads any of the authentication machinery either.