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.
No credit card requiredOne-time 30-minute trial
Pick a server where you have Manage Server, approve, then type /join in any text channel while you're in a voice call.
By NotesBot Team · Last reviewed
Maya: Let's ship the beta Friday.
Sam: I'll write the release notes.
Ravi: QA signs off Thursday.

NotesBotBotToday
📋 Product Sync
📌 Next Steps
- Sam: write the release notes before Friday's beta.
- Ravi: QA sign-off by Thursday.
Where Studio Conversations Go Missing
Many 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. For the daily sync, see meeting notes for remote teams.
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.
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 and a structured AI summary.
The Recap Lands in Your Channel
The recap is posted in the channel your server sends notes to, which is the channel you typed /join in until an admin picks one. 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. It is an invented example that shows the format. The section headers come from the AI summary, and a line added to the Meeting template in /config decides what gets pulled out first. /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 someone has shared their plan, that is the account holder.

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
Add a line to the Meeting template in /config so the recap leads with bug reports, repro steps, and scope decisions.
Speaker Labels
In languages with speaker labels, each line of the transcript carries a Discord name, 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.
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, so you can paste a tester's exact sentence into the ticket, the design doc, or the publisher update. Accuracy depends on the language spoken; the languages page lists each one by published word error rate.
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 every recap posts in the channel your server sends notes to, that channel's 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 of every recorded session. Disagreements about what was agreed stop being debates and become lookups.
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.
Share one person's plan with the server
One person can apply their own plan to a server, and there is no separate server plan to buy. An admin opens /setup, goes to Who pays, names the plan holder and an optional role, and the plan holder accepts by DM unless they set it up themselves. Leave the role empty and only the plan holder can record on that plan; everyone else still records on their own plan or trial.
Notes land where you want them
An admin can send every call to one channel from /setup, and give a single voice channel or a whole category its own notes channel with a team. Teams are free to set up. How teams work
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 records one call at a time. Each assistant bot you invite to the server adds one more, up to 7. There are 6 of them, they join and record but never post, and every call running at once draws on the same hour balance. 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 recap, NotesBot produces a full transcript of the call as a timestamped .txt file. When a tester says the tutorial 'felt like homework', that phrasing is in the transcript, not filtered through whoever took notes. The transcript is also on your dashboard at notesbot.io, so you can paste 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?
Yes. Discord sends NotesBot each person's audio separately, so the transcript can put a name on each line however many people are in the channel, in the languages with speaker labels. When several people react at the same instant, some words can be lost and a short interjection can land on the wrong line. No setting changes for larger calls.
Can I make the summary focus on bugs and player feedback?
Yes. Press Customize prompt in /config, pick the Meeting template and add a line such as 'Lead with bug reports and their reproduction steps, then direct playtester feedback.' A custom prompt replaces the default instructions entirely, so add to the template instead of typing one line into an empty box.
Where do old debriefs and meeting notes live?
On your notesbot.io dashboard, where the transcript and the recap of each call sit side by side and can be searched. The recap also stays in Discord, in the channel your server sends notes to. The audio is kept for 14 days and then deleted, so download a recording you want to keep.
How do plans work for a studio?
One person, usually a producer or a lead, applies their own plan to the studio's server; there is no separate server plan to buy. An admin opens /setup, goes to Who pays, names that plan holder and picks the role allowed to record, and the plan holder accepts by DM unless they set it up themselves. Anyone with that role then records on the plan holder's hours.
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 where someone has shared their plan 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.