Skip to main content

Meetings, PII, and follow-ups

In brief: View and retain cloud meeting transcripts as tribal knowledge, auto or manually redact PII and summarize, then hand the discussion to ChimpHands to run workflows from what the team agreed.

Every joined call produces a meeting record with a transcript—the durable place where tribal knowledge from the conversation is organized and retained. Live sessions appear while a bot is in the call; after the meeting ends and finalizes, open the meeting for the full markdown transcript, participants, and follow-up actions.

View meetings​

  1. Open Meeting Bots → Meetings.
  2. Browse the list (title, start time, labels, participants).
  3. Open a meeting to read the transcript body.

From the meeting detail title pane you can:

  • ChimpHands — open a follow-up draft that references this meeting as context
  • Re-sync / process — re-run PII redaction and summarization on the transcript
  • Delete — remove the cloud transcript

PII redaction and summarization​

Transcripts can be processed for privacy and readability.

Project defaults (auto on meeting end)​

Under Project Settings → Meeting Bots:

SettingPurpose
Days to retain cloud transcriptsRetention window (default 90 days; 0 keeps indefinitely).
Auto-redact PII when a meeting endsOn by default—strip personal data when the session finalizes.
Auto-summarize on meeting endNone / Low / Medium / High compression of the transcript.

Tune these once for the project’s default posture.

Manual re-process​

On a meeting detail page, use Re-sync / process transcript to:

  • Toggle Redact PII
  • Choose a summarization level
  • Overwrite the stored cloud transcript with the processed version

PII redaction and summarization use ChimpHands credits when LLM processing runs (same metering as other agent LLM work)—see Billing.

Ask and act during the meeting​

While the bot is in the call, org members chat:

@testchimp what scenarios already cover checkout retry?
@QABot file an issue for the flaky mobile auth we just discussed
@PMCritique what’s missing from the acceptance criteria we agreed?

Answers and actions use TestChimp’s product / SDLC context—not a blank LLM. Task and issue creation follow whatever your bot policy allows (Custom bots).

Post-meeting workflows​

After the call, turn the conversation into governed work—especially QA workflows built from what the team agreed:

  1. Open the meeting → ChimpHands.
  2. Replace the objective placeholder with what you want done, for example:
/testchimp referring the meeting <meeting-id> as context, do the following :
author user stories for the checkout retry behaviour we agreed, with scenarios

Typical follow-ups:

  • Author agreed user stories / scenarios (author plans)
  • File or refine issues from decisions
  • Scope tests or upkeep against what changed in the call
  • Draft release notes or risk callouts tied to the discussion
  • Codify decisions and domain nuance from support, pre-sales, or planning calls into plans / KB

The transcript is durable product memory for the agent—so you are not re-pasting hour-long notes into a chat window.

See also​

FAQ

Where do I configure auto-redact and summarize?

Project Settings → Meeting Bots: retain days, auto-redact PII, and auto-summarize level on meeting end.

How do post-meeting workflows start?

From meeting detail → ChimpHands, with a draft that references the meeting id as context for catalog workflows.

Does redact/summarize use ChimpHands credits?

Yes when LLM processing runs—same metering as other agent LLM work.

Related documentation