Discord Meeting Bot for Game Studios
Playtest debriefs, design reviews, and team syncs all happen in Discord voice. NotesBot records them, posts an AI recap in your channel, and keeps a word-for-word transcript so player feedback never depends on anyone's memory.
Where Studio Conversations Go Missing
Most small studios already live in Discord. The daily sync happens in voice, the playtest debrief happens in voice, and the heated argument about whether the dodge roll needs i-frames definitely happens in voice. Then the call ends, everyone goes back to their branch, and the details start to evaporate.
A week later someone remembers that a tester "said something about the camera," but nobody wrote down what, or where in the level it happened. A design decision gets relitigated because half the team recalls agreeing to the opposite. The bug a tester described in perfect detail on the call gets logged from memory, minus the reproduction steps that made it useful.
Assigning someone to take notes helps a little and costs a lot: that person stops contributing to the discussion, and their notes capture what they found interesting rather than what was actually said. What a studio needs is a record that writes itself while the whole team stays in the conversation.
How NotesBot Fits Into a Studio Call
Under the hood NotesBot is a Discord meeting bot, and the flow is the same whether you are debriefing a playtest or walking through a design doc:
Start the Recording With /join
Once the team is in the voice channel, anyone types /join in a text channel. NotesBot joins the voice channel as a visible member and starts recording each speaker individually.
Run Your Playtest or Review
Walk testers through the build, let them think out loud, debate the balance change, disagree about the art direction. NotesBot never speaks, plays a sound, or alters what anyone hears; it just listens.
Type /leave When You Wrap
Ending the recording is one command. NotesBot leaves the voice channel and processes the audio into a transcript with speaker labels and a structured AI summary.
The Recap Lands in Your Channel
A few minutes later the recap is posted in the channel your server sends notes to. By default the notes arrive in a thread under the text channel they post in rather than as loose messages, and /config switches that to plain messages. The transcript comes with it as a timestamped .txt file in Discord, and the whole call is archived on your dashboard at notesbot.io.
What Your Playtest Notes Look Like
Here is the kind of recap NotesBot posts after a debrief. The section headers come from the AI summary, and a custom focus prompt shapes what gets pulled out first:
NotesBotBotToday
Playtest Debrief Recap: Build 0.4.2
🎮 Playtester Feedback
- Both testers stalled at the water temple door puzzle; neither noticed the torch hint on the left wall
- Combat pacing felt better after the dodge cooldown change, though one tester asked for a clearer parry timing cue
- The new inventory sorting got unprompted praise as a big step up from build 0.4.1
🐛 Bugs Reported
- Player falls through the floor after fast traveling from the mines to the harbor, reproduced twice
- Boss health bar stays on screen after leaving the arena
- Audio crackle when three or more ability sounds trigger at once
📌 Decisions
- Ship the checkpoint spacing change in 0.4.3, revisit the difficulty curve after the next test
- Art will mock up two versions of the torch hint before Friday
✅ Action Items
- Dana: file the fast travel floor bug with the repro steps from the transcript
- Marco: schedule Thursday's playtest with two fresh testers
Built for How Studios Actually Work
AI Meeting Recaps
Every call ends with a structured summary posted right in your Discord channel: feedback, bugs, decisions, and action items grouped under clear headers.
Word-for-Word Transcripts
The complete transcript sits behind every recap. When the summary says a tester disliked the boss fight, the transcript tells you exactly why, in their words.
Bug-Focused Summaries
Set a custom focus prompt with /config so the AI leads with bug reports, repro steps, and scope decisions. On a studio plan, settings come from whoever's plan pays for the recording.
Speaker Labels
Each voice in the channel is recorded individually and labeled in the transcript, so you know which tester hit the crash and which designer proposed the fix.
Searchable Studio Archive
Recordings, transcripts, and summaries are stored in your dashboard at notesbot.io. Look up what was said about the tutorial three builds ago in seconds.
80+ Languages
Distributed team, or localization playtests in other markets? NotesBot transcribes conversations in more than 80 languages, detected automatically.
Playtest Feedback, Word for Word
The most useful playtest feedback is rarely the answer to a direct question. It is the offhand remark: "oh, I thought that door was decoration," or "I kept waiting for the game to tell me I could climb." Those lines reveal exactly how a player reads your game, and they are the first thing memory throws away.
By the time a debrief gets summarized from memory, "the tutorial felt like homework, I just wanted to touch the grappling hook" has flattened into "tester found the tutorial slow." The first version tells you what to fix. The second one starts an argument.
NotesBot keeps the first version. Its transcription engine produces a full word-for-word transcript with speaker labels, so you can paste a tester's exact sentence into the ticket, the design doc, or the publisher update. And because NotesBot listens to each person in the channel separately, reactions that land on top of each other still come through in the transcript instead of cancelling each other out.
Design Decisions With a Paper Trail
Six weeks from now, someone new to the project will ask why the stamina system changed. Without notes, the answer is a shrug and a half-remembered call. With NotesBot, the answer is the recap from that review: what was proposed, what was decided, and who took the follow-up.
Because the recap posts in the text channel where the call was recorded, your channel history becomes a running decision log that nobody had to maintain. Teammates in other timezones catch up by reading the recap instead of booking a second meeting to re-explain the first one.
And when the summary is not enough, the dashboard archive holds the transcript and the audio of every recorded session. Disagreements about what was agreed stop being debates and become lookups.
/config is your own panel, and the settings that apply to a recording come from whoever's plan pays for it. On a server where one plan covers everyone, that is the account holder.
Set the Studio Server Up Once
Two settings make NotesBot a studio tool rather than one producer's: one plan covering everyone who runs a call, and each recurring meeting posting its notes where that team already reads. An admin sets both from /setup in Discord.
One plan covers the server
One plan can cover the whole server. An admin opens /setup, goes to Team & billing, names the account holder and an optional role, and the account holder accepts by DM unless they set it up themselves. Leave the role empty and only the account holder can record.
Nothing is billed until the account holder says yes, and ending it later leaves their own plan and hours untouched. How team billing works.
Notes land where you want them
An admin can send every call to one channel from /setup, under Where notes go, and give a single voice channel or a whole category a place of its own.
The closest match wins, so a voice channel beats its category, and Preview shows you the answer before a single call is recorded. Where notes go.
Parallel Playtests, Recorded in Parallel
Two testers in two rooms, a design review running while a build triage carries on next door: a studio rarely has just one call worth recording at a time.
NotesBot itself records one call at a time. Each assistant bot you invite to the server adds one more, up to 7. The assistants join the voice channel and record; they never post, so the notes always come back from NotesBot in the channel you expect.
Every call running at the same time draws on the same hour balance, so two recordings for an hour spend two hours. Invite as many or as few as you need:
The invite asks for View Channel and Connect, the two permissions that matter, and never Speak. More on recording several calls at once.
Frequently Asked Questions
Can NotesBot capture what playtesters actually said, word for word?
Yes. Alongside the AI recap, NotesBot produces a full word-for-word transcript of the call with speaker labels. When a tester says the tutorial 'felt like homework' or describes exactly where the camera lost them, that phrasing is preserved in the transcript rather than filtered through whoever was taking notes. Transcripts are stored with the recording and summary in your dashboard at notesbot.io, so you can pull the exact quote into a ticket or a design doc.
We often have six or more people on a design call. Can NotesBot keep up?
NotesBot records each speaker in the voice channel individually, so the transcript labels who said what even when the room is crowded. That per-speaker capture also means a lively debrief where testers and devs react over each other still reads back cleanly: overlapping remarks do not cancel each other out, and quick interjections stay attributed to the person who made them. No special settings are needed for larger calls.
Can I make the summary focus on bugs and player feedback?
Yes. The /config command lets you set a custom focus prompt that steers what the AI pulls out of the conversation. A studio might use something like 'Prioritize bug reports with reproduction steps, direct playtester feedback, and any decisions about scope or priorities.' The recap will then lead with those details instead of a generic meeting summary, which makes it much easier to turn a debrief into a task list. One thing to set up right: settings come from whoever's plan pays for the recording, so on a studio plan the producer who holds it sets the prompt once for everyone.
Where do old debriefs and meeting notes live?
Each recorded session lands in your notesbot.io dashboard, where the audio, the full transcript, and the AI summary live side by side. When someone asks what testers said about the inventory screen three builds ago, you open the archive and check instead of relying on memory. The recap also stays in Discord, in the channel your server routes notes to. By default the notes arrive in a thread under the text channel they post in rather than as loose messages, and /config switches that to plain messages. The transcript comes with it as a timestamped .txt file in Discord, and the whole call is archived on your dashboard at notesbot.io.
How do plans work for a studio?
One plan can cover the studio. An admin opens /setup, goes to Team & billing, names the account holder, usually a producer or a lead, and picks the role allowed to record; the account holder accepts by DM unless they set it up themselves. After that anyone with that role runs /join and every recording is billed to the one plan. Leave the role empty and only the account holder can record. Paid plans run from $3 to $40 per month, 5 to 100 hours of recording. There is also Annual at $96 a year: 240 hours for the year, granted up front. Hours reset each cycle and do not roll over. That covers anything from a weekly sync to a heavy playtest schedule. Each Discord account gets a one-time 30-minute free trial with no credit card, and it does not renew.
Each Discord account gets a one-time 30-minute free trial with no credit card, and it does not renew. Trials are also capped per server: three people and an hour and a half of trial time in total, and a server covered by team billing skips trials altogether. Paid plans run from $3 to $40 per month, 5 to 100 hours of recording. There is also Annual at $96 a year: 240 hours for the year, granted up front. Hours reset each cycle and do not roll over. See every plan.