How this community works
It is a room full of people who run kitchens. It works when it reads like one.
Who can read it
Anyone. No account, no email wall. If somebody searches for the problem they are having at 6am, they should find the answer without signing up for anything.
Who can post
CrewByte customers sign in with the account they already use for the app — there is nothing separate to set up. If you own the workspace, you can post straight away. Everyone else on your team can read, and the owner or a moderator can switch posting on for them.
Not a customer? Ask for access and say what you run. We approve people who work in the industry, whether or not they use CrewByte. A community made only of customers is a support queue with extra steps.
What makes a good post
- Say where you are talking from — one site or ten, and what kind.
- Answer with what you actually do, not what the manual says.
- No supplier pitches.
- Nothing that identifies a member of your team.
What gets removed
Supplier pitches. Anything naming a member of your team or a customer. Advice that would put somebody at risk if a reader followed it — this is a food safety community and wrong confident answers do real damage.
Posts are hidden rather than deleted, and the person who wrote it is told why. If a moderator got it wrong, reply to the notification and a person reads it.
New members
The first few posts from a new external member are read before they appear. It is not personal and it does not last long — it exists because the alternative is a forum full of SEO spam within a fortnight.
What CrewByte does here
We read everything, including the feature requests. Replies from us are marked so you can tell the difference between the company answering and another operator answering. We do not delete criticism of the product.