STRUCTAThe room your guests walk into
A booking page of your own, where somebody books in four steps and never makes an account. A one-time link that lets them move or cancel it without calling you. The check on their own phone. A button that reaches your receptionist. Your name and your colour on all of it, and on every email that leaves.
Four steps, and no account at the end of them
One link — app.structainc.com/b/your-name/book — for your Instagram bio, your Google listing, a card, a sticker on the window. It opens in English, Russian or Spanish, whichever the guest picks, and it stays shut until you open it.
What they came for
Your services, in the categories you put them in — a cut and colour, a physio assessment, an hour in the studio — each with how long it takes and what it costs when you have set a price. Amounts render in your currency. Only active services are offered.
Who they want, or nobody in particular
Your active team by name and colour, plus “Anyone available”. Choosing anyone checks no one’s calendar on purpose: the booking lands unassigned and a person at the desk hands it out. Staff emails, usernames and PINs are not part of what this page can see.
A day and a time
Today and the next thirteen days, on a half-hour grid, never closer than fifteen minutes from now. The grid is that person’s published shift for the day — a split shift shows both blocks and nothing in the gap — and runs 10:00 to 20:00 in your timezone when no shift is published.
A name, and one way to reach them
A name, and an email or a phone — either is enough, both is better. Nothing else is asked. No password is created, because there is no account to put one on.
Two guests can want the same time. The database refuses the second one and the page turns that into a refreshed grid with a line of explanation, never an error screen. Someone on approved time off is named as away rather than shown an empty day — that sends the guest to another person instead of to another six days. Ten bookings an hour from one network is the ceiling.
What happens the moment they press Confirm
- The booking is on your calendar and the managers’ phones buzz.
- If they left an email, a confirmation goes out in the language they booked in, carrying a calendar file they can open and a link to their own page.
- It arrives under your name, in your colour, with your logo. Hitting Reply reaches you, not us.
- The success screen offers them their own page — the last time they need the booking page for this visit.
- A guest who left only a phone number gets none of that. Everything after the booking runs on an email address.
They change it themselves, or they call you
app.structainc.com/b/your-name/me. A guest types the address you already have for them and a one-time link arrives. Nothing they do here reaches anything of yours: the page never talks to the database, only to a server that checks their session first.
A link that works once
Single use, fifteen minutes. The answer is identical whether or not the address is on file, so the form cannot be used to find out who your clients are. Once they are in, that browser stays signed in for thirty days.
Cancel, until two hours before
The rule is printed above the button, not discovered by pressing it. Inside two hours the button is gone and the page tells them to call you — by then you have planned the day around that visit.
Move it, without calling
Another day and time for the same service with the same person. The server re-checks the shift, the lead time and the collision on the way in; a slot taken while they were choosing says so and re-draws the day.
Sign what has to be signed
One document you write — a waiver, an intake form, a patch test. They type their full name, and the exact text they agreed to is stored beside the signature. Edit the text and everyone signs the new version.
See what they have
Their next visits, their last ten — cancellations and no-shows included, because a history that flatters is not a history — and any membership they hold, with visits left and the date it runs out.
A cancellation or a move pages the managers too. A business that is told when work arrives and stays silent when it disappears keeps a chair held for somebody who is not coming, and marks a no-show for somebody who cancelled two days ago.
They pay from their own phone
Open the check on your own screen, show the QR, and the camera does the rest. What the guest gets is the live check, not a picture of one.
The check, as it stands right now
Every line, the service charge and the tax when you charge them, anything already paid, and what is left. It re-reads itself every twenty seconds while the page is open, so two phones on one check converge without anybody refreshing.
A tip, or none
Eighteen, twenty, twenty-five, or nothing at all — and the button says the whole amount before they press it.
Card, Apple Pay or Google Pay
Stripe Checkout, card methods only. A bank transfer that clears tomorrow is not a check a guest can walk away from, so it is not offered.
The money is yours on the way in
A destination charge to your own connected Stripe account, with your business’s name on the card statement rather than ours. Structa’s own fee is 0.35% of the check, set per business — and never any part of the tip, which passes through whole.
What stops it going wrong
- The link is signed and dies in six hours. A guessed one is a plain 404 that explains nothing.
- Two taps on Pay reuse the one open Stripe session instead of opening a second; change the tip and a new one starts at the right total.
- If your staff settled the check first, the page says settled instead of taking the money twice.
- A guest who pays a check that was already closed leaves you holding money you do not own. It is written down with the Stripe ids, shown in the Console as an exception, and refunded when a person presses the button. Never automatically: a money move with nobody accountable for it is not an improvement.
- A remainder under Stripe’s minimum charge cannot clear online. Those last cents are settled at the register.
- Currencies whose smallest unit is the whole unit are refused rather than charged a hundred times over.
A button beside the booking page that reaches a voice
One press opens a call in the browser to the same receptionist that answers your phone — carried at 24 kHz instead of over the phone network, with no number to dial and nothing to install.
- The button renders only when the business behind it can actually take the call. A dead button on a public page is worse than no button.
- Your address and your phone sit under your name on the same page when you have filled them in, so a guest who would rather reach a person still can.
- A browser minute is priced exactly like a phone minute: 133 credits.
- Six calls from one network in half an hour is the ceiling.
- It books on your calendar when online booking is on, takes a message when it cannot help, and refuses to invent a price — the rules it follows on the phone, unchanged.
The day before, the day after, and the day you are full
Three emails that go out on their own. Each one is off until you switch it on, each one is sent under your name, and each one is a decision an owner makes rather than a default we chose.
The reminder, the day before
One short note per booking, in the guest’s language, carrying the link to their own page — so a change of plan becomes a freed slot instead of a no-show. A booking is stamped before the send, so nobody is ever reminded twice.
The review ask, the day after
Only guests who were actually checked in — a visit somebody marked as happened, never one you hoped for. One ask per guest per ninety days, so a regular is not asked every month. You paste the address the button points at.
The waitlist, when the day is full
A guest who finds nothing free leaves their details for that day instead of leaving. When a cancellation frees a slot on it, everyone waiting for that day who left an email gets one note — a spot opened, first come, first served — and the desk gets the same list to work by hand.
What none of the three do
- None of them send a thing until an owner turns them on. Reminders, review asks and the address the ask points at are separate switches, all off out of the box.
- None of them reach somebody who unsubscribed, whose address bounced, or who pressed the spam button. Every one carries a one-click unsubscribe.
- The waitlist note goes out once per entry, ever. A day that frees three slots does not write to the same person three times.
- None of them reach a guest with no email address.
- You do not choose the hour. Each runs once a day.
- Nothing goes out on behalf of a business that has closed its account.
The guest is visiting you, not us
Upload a logo, pick an accent, and every surface a guest touches takes them — the booking page, the personal page, the check, and the mail.
- Your logo and your name sit at the top of each page. The accent is the buttons, the chosen chip, the prices and the links.
- The colour is checked before it is used: button text flips to dark ink when white would not be readable on it, and a navy or a slate is lifted step by step until it clears the dark card behind it.
- The emails carry the same logo and the same accent, and the guest reads your name in the From line.
- Install any of those pages and the icon on the phone is your business — your name under it, your colour behind it, opening on your own page rather than on ours.
- Your public address and phone print under your name on the booking page and inside the confirmation, once you fill them in.
Where our name stays, and why
- The web address. Guest pages live at app.structainc.com/b/your-name; we do not put them on a domain of yours.
- One line at the foot of the personal area and the check: Powered by Structa. It does not come off.
- The sender. Guest mail leaves as “Your business via Structa” from our verified domain, because that alignment is what decides between an inbox and a spam folder — and a booking email nobody sees is worse than a branded one. Replies go to you.
- Terms, Privacy, Security, the DPA and a way to contact us, small at the foot of each public page: the documents a person is entitled to be able to find.
What a guest can change, and what they cannot
A buyer who finds the limit himself stops believing the rest of the page, and a guest who finds it stops believing the business. Every line here is a rule in the code, not a habit.
They can, on their own
- Book a visit.
- Cancel one that is more than two hours away.
- Move one to another day or time.
- Sign your form.
- Join the waitlist for a full day.
- Pay a check, and choose the tip.
- Stop the emails, in one click.
They cannot
- Change the service or the person on a booking. A move keeps both; anything else is a new booking.
- Touch a visit that starts in under two hours — neither cancel nor move. The page tells them to call you.
- Edit their own name, email or phone. The client card belongs to the front desk.
- Pay for a booking in advance, or leave a deposit. The check is an open one, settled on the day.
- Split a check between phones. The button is the whole remaining balance; splitting is done on your side.
- See anything that is not theirs: no notes you keep about them, no lifetime spend, no other guest’s anything.
- Reach further than two weeks ahead. The date strip stops there.
- Use the personal page with a phone number alone. It signs in by email.
- Carry one sign-in between businesses. A guest is a separate client at each business they visit, and the session is stored per business.
- Reach a receptionist in the browser at a business that has not got one — the button is simply not there.
What you switch on first
Nothing here speaks to a guest until an owner decides it should. These are the decisions, and the switches are off the day you arrive.
- The Bookings module, and Online booking turned on in Manage business → Integrations. Until it is on, a visitor is told the business does not take online bookings yet.
- Services with a duration, and shifts published for the people who take them. With no shift published, the day runs 10:00 to 20:00.
- Booking reminders: one switch on the same screen, also off out of the box.
- Review asks: the switch, and the https address the button points at.
- The Clients module and a document actually written, before a form appears for anybody to sign.
- The Payments module and Stripe connected — Express onboarding on Stripe’s own pages; your bank details never touch us. The QR lives on an open order in Orders or Tables.
- The AI Receptionist module and a Pro plan, for the call button. A phone line costs money every month whether it rings or not, so it is the one thing Free does not carry.
- A logo and an accent colour in Manage business → Branding, for any of it to look like you.
- Your public address and phone, if you want them printed under your name.
What’s actually true today
- A guest books without making an account, and without a password existing anywhere in it.
- The booking page opens in English, Russian or Spanish, and the emails follow whichever they picked.
- The confirmation carries a calendar file and a link they can manage the booking from.
- A guest cancels or moves a visit themselves up to two hours before it starts, and your phones are told.
- A guest pays a check on their own phone; the money lands in your own connected Stripe account with your name on the statement.
- Paying a closed check is recorded as money you owe back, and nothing is refunded until a person presses the button.
- One press on the booking page opens a call to your AI receptionist in the browser.
- Reminders, review asks and waitlist notes are each off until you turn them on, and each carries an unsubscribe.
- Your logo and your colour are on every page a guest sees and every email they get.
- Your data is yours: a full export any time, and permanent deletion on request.
Questions owners ask
Does a guest have to create an account?
No, and no password exists anywhere in it. Booking asks for a name and either an email or a phone. Their own page signs in with a one-time link sent to the address you already have for them, and that link works once and expires in fifteen minutes.
Can they cancel at the last minute?
Not from their phone. The line is two hours: outside it they cancel or move the visit themselves, inside it the page tells them to call you, because by then you have planned the day around that visit. The rule is printed above the buttons rather than discovered by pressing one.
Where does the money go?
Into your own connected Stripe account. Guest Pay is a destination charge with your business on the card statement. Structa’s own fee is 0.35% of the check, set per business, and never any part of the tip. You connect through Stripe’s own onboarding; your bank details never reach us.
Can they pay for a booking in advance?
No. What a guest pays today is a check — one left open on the Orders or Tables screen, settled on the day from their own phone. There are no deposits and no prepayments on a booking.
Will my customers see Structa?
They see you: your logo, your colour, your name on the page and in the From line. Our name is in three places and stays there — the web address, one line at the foot of the personal area and the check, and the “via Structa” in the sender, which is the part that gets your mail into an inbox rather than a spam folder.
What does the guest side cost?
The software is free. The booking page, the personal page, the reminders, the review asks and the waitlist spend no credits at all. The browser call does: a minute is 133 credits, priced exactly like a phone minute, and the line it runs on comes with Pro, from $49 a month. Card payments carry Stripe’s own processing fee, and ours on top of it is 0.35% of the check — never any part of the tip.
What if two people book the same slot?
The database refuses the second one, and the page turns that refusal into a refreshed grid with a note. A guest is never dropped on an error page, and nobody on your team is double-booked by the internet.
Do you email my guests without asking me?
No. The three emails that go out on a schedule — the day-before reminder, the day-after review ask and the waitlist note — are each off until an owner turns them on. The confirmation is the exception, and it answers a booking the guest just made.
What happens to a booking page if I leave?
It goes quiet the moment you close the account — the catalogue, the calendar and the Book button together, reading as a business that does not take online bookings rather than showing an open door and refusing at the desk. Nothing further goes out to your guests, and you take them with you: a full export any time, and permanent deletion on request.