Office hours fail in one of two opposite ways: nobody comes, or the same three people come every week and it quietly turns into free consulting held in public. Both are design problems, and both have the same fix. Office hours work when they are a queue rather than a lecture — and when one member's problem, solved in front of others, teaches the people who did not ask.
Here is how to run them so they last longer than the first enthusiastic month.
A queue, not a lecture
Office hours are the one live format where the members set the agenda. You do not prepare material; you prepare by reading what people are stuck on. That is what makes them cheap to run every week, and it is also why they go wrong when they drift into something else.
| Office hours | AMA | Workshop | |
|---|---|---|---|
| Who sets the agenda | Members, one problem each | A subject you chose | You |
| Who answers | You, and more and more the room | A guest | You |
| What you prepare | Reading the questions | The guest and the subject | The material |
| How often | Same slot, every week or two | Now and then | When there is something to teach |
If you find yourself making slides, it has stopped being office hours. A guest with a subject is an AMA, and teaching a skill is a workshop. Both are good formats, but they are not this one.
Take the questions before the call
If you only take questions live, the first ten minutes go to whoever speaks first, not to the problem that matters most. Open a question thread a day or two before each session instead, and ask for two sentences: what you are trying to do, and where exactly you are stuck.
That small request does three jobs. It lets you order the call before it starts. It makes people think, and a surprising number solve their own problem while writing it down. And it lets members who cannot attend still get an answer, which matters more than it sounds in a community spread across time zones.
The questions are the attendance list. Whoever posted one gets called on; whoever only wants to listen is welcome to listen.
One person, one problem, ten minutes
Give each person a fixed slice, around ten minutes, and say so at the start. Without it, the first problem expands to fill the hour and everyone else leaves without being heard.
Ask the person to restate the problem in a sentence, then ask what they have already tried — this is where most of the useful answer is hiding. End every slot with a next step the person can name back to you, so they leave with something to do rather than a pleasant conversation.
If a problem needs more than ten minutes, it needs a different format. Say so, and move it to a thread or a follow-up, rather than letting it take everyone else's time.
Answer for the room, not just the asker
The reason to hold office hours in a group rather than one-to-one is that most problems are shared. Before you answer, ask "who else has run into this?" and give the room a moment. Often a member has solved it more recently than you have, and their answer lands better because they were in the same position a month ago.
When you do answer, finish with the general version: the principle behind the fix, not just the fix. That turns one person's slot into something everyone else on the call can use. It is the same habit that gets members talking to each other outside the call — answer the part you are sure of, and hand the rest to the room.
Over time, you should be answering less. Office hours where members answer each other are working; office hours where everyone waits for you are a bottleneck with a calendar invite.
The same three people, every week
Every recurring session grows regulars, and regulars are a good sign until they fill the queue. The newer member with a basic question will not compete with three confident people who have been coming for months; they will simply stop coming.
Two rules handle it. First-timers go first. And nobody asks a second question until everyone who posted has had their turn. Then give the regulars a different job: ask them to answer, not just ask. A regular who helps someone newer is getting more out of the hour than one who asks a fifth question, and is often the person who will run the session when you cannot.
Where office hours end and consulting begins
"Could you look at my whole launch plan?" is not an office-hours question. It is a project, and answering it in a group call is unfair twice over: to the person, who gets ten rushed minutes on something that needed an afternoon, and to everyone else, who waited for their turn.
Draw the line by the question, not by the person. A question has an answer; a project needs work done. When something is a project, say so kindly and say where it belongs — a thread, a paid session, a course module. If you sell coaching, office hours are the shop window for it, not a free version of it. As our coaching guide puts it, the community should answer the questions that never needed you, so the live hour goes to the ones that do.
Saying "that is bigger than ten minutes" is a kindness. It tells the person their problem is real, and it protects the format for everyone else.
The week nobody comes
Some weeks the question thread stays empty. Do not hold a call to an empty room in the hope that people turn up, and do not quietly skip the session without a word.
Cancel the call, not the slot. Post a short note at the usual time — answer a question that came up elsewhere that week, or share one thing you would have said — and run the next session as normal. The warning from building a ritual applies here: a thing that has been interrupted once is now visibly optional. A written week keeps the slot alive; a silent gap tells members it was optional all along. If the thread is empty three times running, that is information: try a different time, or a fortnightly slot, before deciding members do not want it.
A small turnout is not a failure. Four people with real problems is a good session, and apologising for the turnout tells the four who came that they were not enough.
Write the answers down
The call is not the archive. A recording of an hour of office hours is rarely watched — nobody scrubs through sixty minutes for the eight that were about their problem.
What lasts is a short written answer under each question in the thread: two or three lines on what was suggested and why. It takes ten minutes after the call, it helps everyone who could not come, and it is what stops the same question arriving for the fourth time. Next month, when someone asks it again, you can point to the answer instead of giving it again.
Think before recording at all. People describe a real problem differently when they know it is being recorded, and office hours depend on people saying where they are actually stuck.
What the software can and cannot do
You can run office hours in Mateflow without a separate tool for the calendar or the call.
Set the session up as a weekly recurring event, so members can RSVP, get reminders and add it to their calendar. Link a group call to the event and choose who can join — members of the space, or only the people who RSVP'd. A group call has a seat limit set by your plan, and even the smallest is more people than office hours can serve well in an hour. For the questions, a Q&A space fits best: each question is its own post, members can upvote the questions they want answered too, the space can be sorted by Most Voted, and the member who asked — or a moderator — can mark the reply that solved it as the accepted answer. Q&A spaces and events are on every plan, and events are not capped. Live rooms are not recorded unless the host switches recording on, and everyone who joins a recorded room is asked for consent first.
The honest limits are about the queue. There is no booking tool for individual time slots, so the order comes from your question list, not a calendar. And there is no raised-hand queue in a group call — that is a webinar feature — so you call on people from the list you prepared. Treat upvotes the same way: a useful signal of what the room wants, not the running order.
Three things not to do
Do not run office hours without taking questions first. The loudest problem wins, and the person who most needed help sits through an hour of someone else's.
Do not let it become a lecture. If you are presenting, it is a workshop; call it one, and keep a separate slot where members bring the agenda.
Do not answer everything yourself. Ask the room first. A session that only works when you talk will never outgrow your calendar.
The bottom line
Office hours are the cheapest recurring event a community can run, because members bring the agenda and you bring your attention. They fail when nobody asks, when the same few people ask every week, or when the hour becomes unpaid consulting.
So run them as a queue: questions in writing before the call, ten minutes per problem, first-timers first, the room asked before you answer, projects sent somewhere better, and a written answer left behind under every question. Then keep the slot, week after week — even the quiet ones, even when it is only four people — because the reason office hours work is that members know they will be there.