Measure this visit?
Accept allows Google Analytics, Microsoft Clarity and PostHog, including session recording. Reject stops their recording. Cookieless counts and server request logs stay on. What we measure
Growth & Demand
We run the space where your users talk, with a published coverage window and moderation tooling we build. Escalation reaches your product team.
Updated
The decision is not which platform. It is whether the room should exist yet. If it should, one more thing has to be settled first: which of three jobs it is being opened to do. Deflect support tickets. Keep the members who answer each other. Carry product signal back to the people who build the thing. A room opened without that answer gets staffed to look busy.
This page owns what holds wherever the space lives: strategy, staffing, escalation and reporting. Platform mechanics sit on their own pages: Discord servers, Telegram groups and channels, Reddit and public forums. Buying attention to fill the room is media buying. Your repository, issues and release notes are GitHub marketing.
Three outcomes. Each is bought differently, and which one you are after decides the rota more than the platform does.
Support deflection. A question answered once, in public, somewhere searchable, is a question the next person does not raise a ticket about. It has the clearest cost attached to it and it fails fastest when nobody is on duty.
Retention. A member who has answered someone else’s question has a reason to open your product that your roadmap cannot manufacture. That is a mechanism, not a promise, and it only works if there are enough members present for a conversation to start.
Product signal. The complaint that never becomes a ticket, the workaround three people invented independently, the feature request phrased as a joke. It is the most valuable output and the one most often thrown away, because nothing carries it out of the chat.
Because we build software, we write the tooling instead of only configuring it. Onboarding gates, triage bots, escalation hooks into your tracker, digests of recurring questions. Off-the-shelf bots get used where they fit. Whatever is built for a platform is documented on that page, because none of it ports.
In the order they usually happen.
Nobody seeded it. A space opens with rules and no conversation, and the first fifty members find a room where speaking feels loud. Seeding is real work: real questions asked by real people, usually the team, in the first weeks.
Nobody answered. Not slowly. At all. The gap that kills a room is the one between a member posting and the first human reply. It is almost always worst at the hours members are free to type.
Then moderation is absent when it matters. Spam, scams and abuse arrive on their own schedule. A space that is clean during your working day and hostile at midnight is a hostile space. The people who saw the midnight version do not come back to check.
Coverage is priced in staffed hours, and how many you need follows from where your members live. Where we live does not come into it. We write the window down, publish it in the space, and say what happens outside it. A stated window beats an implied always-on that is quietly untrue three nights a week.
Escalation is the other half of the cost. Every space needs an agreed line. What a moderator answers, what goes to your engineers with a name on it, and what gets a public status note. Without that line the moderator becomes a wall, and members work out within a month that posting changes nothing.
Total members only goes up. It counts everyone who joined for a giveaway two years ago and never returned, and it keeps rising while the room dies.
We report retained active members: people who posted or reacted in the window and were still doing it in the next one. Alongside it we report questions answered in public before they became tickets, and first-reply times including the slow tail. We also report the share of answers that came from members and not staff, and the escalations that reached your tracker. Members who went quiet sit in the same table as the ones who arrived.
If you do not have users yet, a community is an empty room. Staffing one so it looks busy is theatre, and it is expensive theatre, because the people you eventually want in there will see the archive. The sequence that works is product, then users, then finding where those users already talk. Open a room only if they are not better served somewhere that already exists.
We will not manufacture activity. No sockpuppet members. No giveaway loops that inflate a number you plan to show an investor. No daily prompt posts written to keep a chart from flattening. A room with a hundred people who mean it beats one with ten thousand who are waiting for a code.
We will not pretend to be someone else. Our moderators are identified, and anything answered by a model says so. Astroturfing somewhere you do not own is dishonest and, on most platforms, a bannable offence. It attaches to your brand, not to ours.
The refusal that costs us the retainer is simpler. Sometimes there are not enough users yet. Sometimes the one place they gather is a forum you should join and not compete with. We say so. We do not open a space and bill you to keep it warm.
The platform rules matter as well as the schedule. Reddit requires authentic participation. Telegram documents its group topics, which we consider when organising a busy group.
First we find where your users already talk. That is often a subreddit, a vendor Slack or somebody else's group, somewhere you do not control. If the honest answer is that there are not enough users yet, we say so before there is a retainer. An empty room is worse than no room.
Purpose, scope, rules and the escalation path get written down before anyone is invited. The structure, onboarding gate and moderation tooling are then built to fit that document, so the room enforces something a member can read. Without it, enforcement is whatever the moderator on duty feels like that day.
Coverage is bought in hours, not in headcount. We agree the window from where your members live. It gets published in the space, so nobody waits on a reply that is not coming. Named people staff it, and they say who they work for.
A bug, an outage or a pricing complaint leaves the chat and enters your tracker with an owner on it. The moderator then reports back in public. Without that loop the community becomes a wall members shout at, which is the state most of them end up in.
Monthly, on retained active members and on questions answered before they became tickets, alongside the members who went quiet. Growth in total signups is not reported as a result, because that number can only go up.
No. They use named accounts, identified in the room as working for a partner agency. Sockpuppets and undisclosed personas are the fastest way to lose a community permanently, and on Reddit they are also against site-wide rules. If you want the cover to look in-house, hire the person yourself. We build the tooling and the escalation path around them.
Usually the hours they cannot work and the software they cannot write. One person covers one timezone and takes holidays, so nights and weekends are where communities quietly fail. We either cover the gap around your person, or build the onboarding, triage and escalation tooling that makes their day smaller. Both are bought separately.
Whichever one your users are already on. Ask them which one that is, and start from the answer. Real-time chat suits products people use daily and have questions about. A public forum suits products with long, searchable problems. Broadcast-plus-group suits audiences on their phones. The three platform pages linked above describe what running each one actually involves, and they differ more than they look.
We remove abuse, spam, scams and anything that breaks the charter. We do not remove criticism, and we will argue with you if you ask. A room where complaints disappear teaches members to complain somewhere you cannot see, and the version of it that reaches a public forum is worse. The right answer to a fair complaint is a reply with a date on it.
You do. Everything runs in accounts your company owns, the code we write is yours, and the handover includes the runbook and whatever credentials were issued. We are not interested in a community that cannot function without our invoice. The reporting is designed so you can tell whether it still works after we leave.
We agree a target before we start and publish it in the space. We will not quote you a number on this page. The honest figure depends on the hours you buy and the volume you get. It also depends on how much of that volume needs an engineer instead of a moderator. What we commit to is that the stated window is real and that the response time is in the monthly report, including the tail.
Start a conversation