Meeting Bots
In brief: Meeting Bots bring TestChimp’s product and QA context into live calls on Meet, Zoom, Teams, and Webex—capture tribal knowledge, answer with product awareness, assign work, and turn conversations into workflows (QA and beyond).
Most meeting bots only record what was said. TestChimp Meeting Bots join the call with the complete product context and QA posture TestChimp already builds across your SDLC—user stories, scenarios, tests, executions, releases, knowledge bases, issues, observability metrics, API schemas, and the rest of the knowledge graph.
That means the agent in the room is not a generic note-taker. It can capture what your team knows, answer product questions, create follow-ups, and turn discussion into governed work—without re-explaining your stack every time.
Supported platforms
Meeting Bots join Google Meet, Zoom, Microsoft Teams, and Webex—paste a meeting URL or pick a calendar event that already has a conferencing link.




Core capabilities
- Capture tribal knowledge — Detailed meeting notes are organized and retained in TestChimp, so the knowledge your team shares in conversations can be captured, codified, and fed into later workflows—not left in someone’s head or a forgotten recording.
- Get product-aware assistance — Team members
@mentionTestChimp (or a named bot) in chat—or just ask for help. Answers use the product and SDLC context TestChimp maintains. Assign tasks and create work directly from the discussion. - Turn conversations into QA workflows — After the call, hand the transcript to ChimpHands / catalog workflows—for example generating user stories and test scenarios from what the team agreed on, scoping tests, or filing issues from decisions made live.
- Transcribe once, with privacy controls — Meetings are transcribed and stored in the cloud, with optional PII redaction and summarization.
Core concepts
Meeting Bots are organized around three ideas:
| Concept | What it is |
|---|---|
| Bots | Named personalities (job role + policy)—e.g. QABot, SalesBot, or a custom FDE / support / PM critique bot. They define how the agent should behave when mentioned. |
| Meetings | A joined call (Meet / Zoom / Teams / Webex URL or calendar event). One cloud join produces one transcript for the meeting; attached bots share that session. |
| Calendars | Connected Google or Outlook calendars that power the upcoming-meeting list and enable reliable @mention team guards when participant emails are available. |
In the product, open Meeting Bots in the sidebar:
- Bots — create and edit personalities and policies
- Calendars — connect team calendars
- Meetings — browse transcripts, re-process (redact / summarize), and hand off to ChimpHands
New projects seed default bots (QABot, SalesBot). You can add more anytime.
How a join works
- Connect a calendar (recommended) or paste a meeting URL.
- From Bots, choose a personality and Join Meeting.
- A single visible TestChimp Agent joins the call, transcribes, and listens for chat mentions.
- Org members
@testchimpor@BotNameto invoke LLM answers (externals are denied). - When the meeting ends, the transcript lands under Meetings—ready to redact, summarize, or drive a post-meeting workflow.
Transcription is per meeting, not per personality. Attaching multiple bots does not double transcription cost—see Billing.
Beyond QA: your meetings, your product intelligence
Use cases go well beyond QA. The same deep product-context awareness that powers TestChimp in the SDLC is available in any live conversation:
| Context | What a Meeting Bot can do |
|---|---|
| Pre-sales | Answer with product truth—coverage, capabilities, known gaps—without derailing the call |
| Customer support | Ground troubleshooting in real scenarios, releases, and issues your team already tracks |
| FDE / implementation | Unblock questions against plans, APIs, and coverage instead of guessing from memory |
| Product / planning | Capture decisions, pressure-test acceptance criteria, then author stories and scenarios after |
Define custom bots with bespoke personalities and objectives, then bring the right assistant(s) into each meeting. Attach several to the same call for structured brainstorming—everyone still shares one transcript.
Details: Custom bots and policies.
Your meetings—now part of your product intelligence.
Learn more
- Custom bots and policies — personalities, policy files, best practices
- Calendars — Google and Outlook connect
- Meetings, PII, and follow-ups — tribal knowledge, transcripts, redact / summarize, ChimpHands handoff
- Billing — hourly join rate + ChimpHands credits for LLM invokes
FAQ
How are Meeting Bots different from a generic note-taker?
They join with TestChimp’s product and QA context—stories, coverage, issues, releases, KBs, and more—so answers and follow-ups use product intelligence, and meeting knowledge is retained for workflows.
Which meeting platforms do Meeting Bots support?
Google Meet, Zoom, Microsoft Teams, and Webex—join from a calendar event with a conferencing link or paste a meeting URL.
What is tribal knowledge capture?
Meetings are transcribed, organized, and retained so knowledge shared in conversation can be codified and fed into later workflows instead of living only in people’s heads.
Are Meeting Bots only for QA?
No. The same product context helps in pre-sales, customer support, and FDE calls. Define custom bots with bespoke personalities for each context.
Can I attach multiple personalities to one call?
Yes. Multiple custom bots can share one join and one transcript—transcription is per meeting, not per bot.