Internal engagement has a specific failure mode. You ask a room of four hundred employees for questions, three people raise a hand, two of them are the same two as last quarter, and afterwards someone tells you in the corridor what they actually wanted to ask.
The instinct is to reach for a tool. The instinct is right, but most of the tools are built for public events, and a public tool in an internal room makes the problem worse rather than better. Nobody is going to type a real opinion about the reorganisation into anything that might leave the building.
This is what a private wall is genuinely good at, and it is worth doing properly.
Why people say nothing
Three separate blocks are usually operating at once, and they need different fixes.
They think it will be seen outside. If contributing means posting to a social platform, or if nobody has said where the posts go, employees assume the worst and stay quiet. This is the easiest one to fix and the most commonly ignored.
They think it will be attributed and remembered. A message wall with names attached is fine for congratulations and hopeless for honest feedback. Which one you want should be decided before you open the wall, not discovered halfway through.
They think nothing will come of it. If last year’s questions went into a wall and never got answered, this year’s wall is already dead. No feature fixes that. Answering three of the questions live does.
A private wall handles the first one structurally and gives you the tools to handle the second. The third is on you.
Formats that work internally
Not every internal event wants the same wall. These are the ones that reliably earn their place on the screen.
Questions before the all-hands, not during it. Open the wall a day early and put the code in the calendar invite. People write better questions from their desk than from a seat, duplicates cluster so you can see what the room actually cares about, and the exec team gets to prepare instead of improvising. Run it in approval mode and publish the ones you are going to answer.
One word for the quarter. Deceptively good. It takes four seconds, so the participation rate is enormous compared to anything requiring a sentence, and a wall of ninety single words is a more honest temperature reading than any survey. It also produces the occasional word that starts a real conversation.
Credit where it is due. Who on another team made your job easier this year? This is the prompt that consistently produces the most posts at internal events, because it is the one thing everybody has been meaning to say and never had a venue for. It also surfaces the quiet contributors that management genuinely does not see.
The remote-office wave. If you have offices in other time zones, ask each one to post at a set moment in the run of show. A block of messages from the Lisbon team landing while the room in Manchester watches does more for “one company” than any slide about it. Photos work even better than text here.
The offsite photo wall. Two days of people who normally exist as small video squares actually being in a room together. Open a wall for the whole offsite, put the code on the agenda, and let it fill. By the closing session you have a record of the event that nobody had to assign to anyone.
The names question
Decide this deliberately, because it determines what you get.
Names attached produces warmth. Congratulations, credit, thanks, photos, in-jokes — all of it works better with a name on it, because the point is partly the attribution. Use it for celebrations, offsites, milestones, and anything where you want people to feel seen.
Names optional produces honesty. Give people the choice and a meaningful number will still sign their name, while the ones with the uncomfortable question get to ask it. This is usually the right setting for a town hall.
What does not work is pretending. If your wall attaches names, do not ask for candid feedback and then look surprised at the answers you get, which will be diplomatic to the point of uselessness. Ask a question the format can actually support.
Related, and worth saying to the room: a wall where people can post without a name is not an anonymous reporting channel and should never be presented as one. It is a participation tool. Grievances need the real process, and conflating the two does a disservice to people with something serious to raise.
Moderation, staffed properly
Internal events need less aggressive moderation than public ones and more thoughtful moderation.
You are rarely filtering abuse. You are filtering the post that names a customer who should not be named on a screen with contractors in the room, the joke that lands differently written down than it would in the kitchen, and the same question asked eleven times.
Practical setup:
- One moderator with the queue open on a laptop, not on the same machine driving the display.
- A named backup, because the moderator will go and get coffee.
- A rule agreed beforehand about what does not go up, written in one sentence. Nothing naming a customer, nothing about an individual’s performance. Vague rules produce inconsistent decisions and arguments afterwards.
- Publish duplicates as one. Eleven versions of the same question is a signal for the presenter, not eleven posts for the screen.
The moderator should be someone with the standing to make a judgement call, which usually means not the most junior person available. It takes about the same effort as running the slides.
What IT and legal will ask
If your organisation has any review process, you will get some version of these. Have the answers ready and the conversation takes ten minutes instead of three weeks.
Does this post anything to social media? With GuestWalls, no — it does not read from social platforms or write to them. Posts go from an employee’s phone to your event screen and nowhere else.
Who can see the wall? People with the event code. If the session is sensitive, add an event password, and then the code alone is not enough.
Do employees need accounts? No. Guests post from a normal phone browser without signing up, which means there is no employee directory to sync and nothing stored about a person beyond the message they chose to send.
How long is the data kept? Closing the event stops guest posting immediately. The host keeps access to the wall and its playback through a thirty-day retention window, after which everything is deleted automatically. A host can delete it sooner. The privacy page is the document to forward.
What happens on our network? Attendees post over their own mobile connections, so a strained guest network mostly affects the machine driving the display rather than participation. Worth a test in the actual room regardless.
Run of show
A wall that appears on screen with no warning gets ignored. One woven into the agenda does not.
Open it the day before with the code in the calendar invite and one clear prompt. Put the code on a slide during the pre-start loop, not just once at the beginning. When the session starts, show the wall for sixty seconds and read two posts aloud — this is the single highest-impact thing you can do, because it proves that posting has a consequence.
Change the prompt between segments rather than leaving one up all session. Close with the wall on screen while people file out, which is when the last third of the posts arrive.
Afterwards, answer the questions you did not get to. A follow-up message that says here are the eight questions we ran out of time for, and the answers is what makes next quarter’s wall fill up in the first ten minutes.
The part that actually matters
Every mechanism above is in service of one thing: making it safe and quick for the people who do not speak up to say something.
You already know what your loudest employees think. The wall is for the other several hundred, and they will only use it if they believe the room is closed, the screen is moderated by a human, and someone is going to read what they wrote. Get those three right and the rest is choosing a good prompt.