Early Adopter Access  —  Be one of our first accounts. Full platform, no charge up front.
Private staff chat

Everything a new hire
has to ask somebody

Where things are. How things are made. What's in the special and what pours with it. Put it in a private chat only your team can reach and stop being the only copy of it.

On their own phone · No account · Nobody outside your staff gets in
The first week

A new server's whole shift
is finding someone to ask

It seems like the real cost of turnover isn't hiring it's the two weeks after. Where are the backup linens. Which walk-in has the dressings. How is the burger actually built. Is the special still on. What do we pour with the rib-eye. Every one of those is a question they have to interrupt someone to ask, and the someone is usually your best person mid-service.

So they guess, or they wait, or they tell a guest something that isn't true. And in six weeks, when they're the one being asked, they pass along the version they guessed.

The knowledge doesn't need to live in a person. It needs to live somewhere everyone can reach.

What goes in it

The things nobody writes down

Upload it the same way you upload a menu photos, documents, or typed straight in. It only ever answers from what you put there.

Where things are

The map of the building

Which walk-in holds the dressings. Where the backup linens live. Which key opens the dry storage, where the spare fryer baskets are, what's on the top shelf in the basement. The stuff that takes a month to learn by wandering.

How things are made

The build, the prep, the plate

How the burger is stacked. How much dressing goes on the wedge. Prep steps for the soup, the portion on the rib-eye, which sauce goes under and which goes over. Your standard, written once, so it doesn't drift by cook.

Food, specials & wine

Notes worth a real answer

What the special is tonight and what's in it. Which wines pour by the glass, what they taste like, what they go with. Why the chef put the dish on. A server can answer a pairing question at the table instead of finding you.

If you've explained it more than twice, it belongs in here.

How they get in

A private code, and that's it

No logins to hand out, no accounts to deactivate when someone leaves, no tablet to buy.

For your team only

Reached by code

Staff get in with a private code you control. Guests never see this chat, and it isn't linked from anywhere a guest can reach.

On their own phone

Nothing to install

They open it in a browser, the same way a guest opens the menu chat. No app store, no company device, no IT.

One source

Same truth as the guest chat

The staff chat and the guest chat draw from the same place. What a server learns is exactly what a guest is being told because it's the same sentence.

That last one is the whole point. The guest chat standardizes what customers hear. The staff chat standardizes what your team knows. Same source, both directions.
What changes

The benefit is invisible on day one
and obvious by week three

New hires ramp in hours, not days

They learn the operation from your own words instead of from whoever happened to be free. Nobody shadows for a week just to find out where things are kept.

You get interrupted less

The questions that used to walk into your office get answered where they're asked. You stop being the lookup table for your own restaurant during the busiest hour of the night.

Veterans stop working from memory

Your ten-year server remembers the menu from last spring. When the recipe changes, the reference changes with it, so experience stops quietly turning into misinformation.

Allergen answers stop being a guess

A server who isn't sure has somewhere to check in ten seconds instead of walking to the kitchen and relaying an answer they half heard. That's the one that ends careers when it goes wrong.

Say it once.
Have it stay said.

Start with the five things you're tired of repeating. Add to it whenever you catch yourself explaining something twice. It builds itself out of your own shifts.

Free to start · No card · Your team, nobody else
Also worth a look

Two other ways it runs