scribbl.co

What is Scribbl?

Scribbl is a Chrome-based AI notetaker for online meetings. Its defining feature is that no bot joins the call: instead of a visible participant announcing itself, it records your Meet, Zoom, or Teams calls from your side and turns them into notes. The notes are then connected to ChatGPT and Claude, so you can ask questions about any past meeting rather than just reading a transcript.

What it actually does

• Records meetings without adding a participant to the room.
• Produces notes, including who spoke and when, with a speaker breakdown.
• Connects those notes to ChatGPT and Claude so you can query your meetings.
• Aims at the work after the meeting: follow-up emails drafted in your voice, CRM updates, briefs, and scheduling next steps.

Who it suits

The "no bot" approach matters most for people whose calls involve clients, candidates, or external partners, where a visible recording bot can be awkward or unwelcome. If your meetings are internal and everyone is comfortable with a bot, that advantage shrinks, and a conventional notetaker may be just as good.

Trade-offs to weigh

• Recording is your responsibility. Scribbl's own page notes that recording laws vary by region and that you must have the consent you need from people in your meetings.
• The AI handoff depends on how well your notes capture context; messy audio or overlapping speakers will limit what ChatGPT or Claude can do with them.
• The valuable "do the work" features, like drafting follow-ups or updating a CRM, depend on connecting the AI to the tools you already use, which is more setup than simply taking notes.

A practical next step

Try it on one low-stakes call with a colleague first, then ask ChatGPT or Claude a question about that meeting to see whether the notes carry enough detail. If they do, move to a real client call with consent handled up front. For comparison, meeting-recording approaches from Otter.ai and Fireflies.ai typically do join calls as a visible participant, which is the main difference worth testing against your own meeting culture.

How does Scribbl record meetings without a bot joining the call?

Scribbl records meetings locally through a Chrome extension rather than sending a visible participant into the call. Because the capture happens on your machine, there is no "Scribbl Notetaker" attendee in the participant list, no join notification, and no waiting room prompt. The recording is tied to your browser session, so it captures what your computer hears and shows — your microphone and system audio — instead of connecting to the meeting platform's servers as a separate client.

That design has practical consequences worth weighing:

• No announcement to other attendees. Nothing appears in the participant list or chat, so the meeting flow is undisturbed.
• You are responsible for consent. Because the tool is invisible to others, recording laws in many regions still require you to inform participants and get permission. Scribbl's own page flags this directly.
• Dependence on your device. If your machine sleeps, your browser crashes, or your audio routing is wrong, the capture suffers. A server-side bot is more resilient to local hiccups.
• Platform coverage. The page lists Google Meet, Zoom, and Teams — typically the browser-based versions, since the extension works inside Chrome.

After capture, the transcript is handed to ChatGPT or Claude, which can then draft follow-ups, update a CRM, write a brief, or schedule next steps using the meeting as context.

Next step: before relying on it for a recurring internal meeting, run one test call in each platform you use and check that both your voice and the other participants come through clearly. If your team meets mostly in desktop apps rather than the browser, verify the extension can still capture that audio before committing.

For comparison, bot-based notetakers such as Otter.ai and Fireflies.ai join as visible participants and handle recording server-side, which trades visibility and consent clarity for less dependence on your hardware.

Is Scribbl really free forever, or are there paid plans?

Scribbl is marketed as "free forever" with no credit card required to start, but the site also links to a pricing page. That combination usually signals a freemium model: a genuinely usable free tier alongside paid plans for heavier or team use. The page evidence here only confirms the free-forever claim and the existence of a pricing page; it does not state what the paid tiers include or cost.

What the free claim covers

• Adding Scribbl to Chrome and recording meetings with no bot joining the call.
• Notes from every meeting, plus the ability to query those notes through ChatGPT or Claude.
• No credit card required to begin.

How to decide

If your main need is a bot-free notetaker for individual meetings, the free tier is likely enough to test. If you need shared team libraries, admin controls, or higher usage limits, expect those to sit behind paid plans — check the pricing page directly for the current breakdown.

A practical next step

Run it on one real recurring meeting for a week. Compare the notes against what you'd normally write yourself, and check whether the ChatGPT/Claude handoff actually saves you follow-up work. That tells you whether the free tier is sufficient before you consider paying.

One caveat worth noting: recording consent rules vary by region, and the "no bot" design means other participants may not realize they're being recorded. That's a legal and trust consideration regardless of which plan you choose.

How do I connect Scribbl to ChatGPT and Claude for post-meeting tasks?

Scribbl is built so you don't have to wire up a separate integration yourself: once a meeting is recorded, the notes are handed to ChatGPT and Claude, and you ask those models about the meeting rather than copying transcripts between apps. The connection is the product's core mechanism, not a manual setup step you configure.

What "connected" means in practice

The page describes a three-part chain:

• The source — a recorded meeting (Scribbl works with Meet, Zoom and Teams).
• The AI, now connected — ChatGPT or Claude, given the meeting as context.
• The work, done — a follow-up email drafted in your voice, a CRM update, a brief, or a calendar invite for next steps.

So the practical answer is: install the Chrome extension, let it record your calls without a bot joining, then use ChatGPT or Claude on the resulting notes. Scribbl's role is supplying the meeting context; the models do the drafting and the tool actions.

A realistic first run

Take one recurring meeting you already attend. Record it, then ask your model a single concrete question — "draft the follow-up email to the client, in my voice, listing the two decisions and the date we agreed" — and check whether the output is usable before you rely on it for anything outward-facing. That tests the whole chain cheaply.

Trade-offs worth knowing

• No bot in the call means nothing announces itself, which avoids the awkward "who invited the bot?" moment, but it also means the meeting's other participants may not realise it's being recorded. The page itself flags that recording laws vary by region and that you must have the consent you need.
• Model dependency. The quality of post-meeting output depends on ChatGPT or Claude, so your results will track those tools' capabilities and any account limits you have with them.
• Speaker attribution is shown in the interface (who spoke and when, with percentage breakdowns), which matters if you want the AI to attribute a commitment to the right person rather than blurring it into "the team."

Choosing between this and a bot-based notetaker

For a team already living in ChatGPT or Claude, the appeal is not the transcript — it's skipping the copy-paste step between the meeting and the work that follows it.

Next step: check Scribbl for how recording works on your specific platform, and confirm your organisation's consent policy before your first recorded call.

Does recording calls with Scribbl require consent from other participants?

Yes. Scribbl's own page states plainly that recording laws vary by region and that you should make sure you have the consent you need from the people in your meetings. Because Scribbl records without a bot joining the call, nothing announces itself — which removes the social cue that normally prompts a "do you mind if I record this?" moment. That makes consent your responsibility to handle deliberately, not something the tool will prompt for.

What that means in practice

• Consent is a legal question, not a product setting. Scribbl doesn't claim to obtain consent for you; it flags that you need it. Whether it must be explicit or can be implied depends on where you and the other participants are located.
• One-party vs. all-party rules. Some jurisdictions require only one participant (often you) to consent; others require everyone on the call to agree. Multi-region calls can trigger the strictest applicable rule.
• The no-bot design shifts the burden to you. With a visible notetaker, participants see it join and can object. With Scribbl, the record happens quietly, so an unannounced recording is more likely to be a problem.

A concrete scenario

If you're a sales rep in a one-party-consent region calling a prospect in an all-party-consent region, the safer path is to assume all-party consent applies. A short spoken line at the top — "I'll be taking notes for accuracy, is that okay with everyone?" — covers you and takes seconds.

Next step

Before your next call, decide your default disclosure script and where Scribbl fits: full disclosure for external calls, internal team norms documented in writing, and a rule for when to stop recording if someone objects. For the legal specifics, check your own jurisdiction's rules or ask counsel — the product page gives the general warning, not legal advice.

If you want a visible-bot alternative for calls where disclosure matters more than invisibility, compare options such as Otter.ai or Fireflies.ai, both of which join meetings openly.

Can Scribbl update my CRM or send follow-ups automatically after a meeting?

Yes — that is the core promise Scribbl makes. Its page describes an AI notetaker that records your Meet, Zoom, or Teams calls without a bot joining the room, then connects the transcript to ChatGPT or Claude so the AI can act on it. The examples given are follow-up emails drafted in your voice, a CRM deal logged and moved forward, a brief written, and next steps scheduled on your calendar.

The important nuance is how it works. Scribbl is described as the piece in the middle: it supplies the meeting transcript and context, and the connected AI plus your existing tools do the actual work. So "automatic" depends on what you have connected and whether you have set up the workflow. It is not a standalone CRM.

H3 Practical test before relying on it

• Run one real call, then check whether the follow-up draft and CRM entry match what you would have written yourself.
• Confirm which CRM and calendar tools you can connect, and whether the AI has permission to write to them or only to draft.
• Decide who reviews outgoing messages. A drafted follow-up in your voice still needs your sign-off on tone and commitments.

H3 Where the no-bot design matters If your clients or candidates react badly to a visible "Scribbl bot has joined" notice, the invisible approach avoids that social friction. The trade-off is consent: the page itself warns that recording laws vary by region, so you must have the consent you need from everyone in the meeting. That is a legal and trust obligation, not a setting.

For comparison, Otter.ai and Fireflies.ai are well-known notetakers that typically join as a visible participant, while Granola is a note tool built around the user's own device. If bot-free recording is your deciding factor, Scribbl is aimed squarely at that.

Next step: start with one recurring internal meeting where a wrong CRM entry is low-risk, verify the output for a week, then expand to client calls once the drafts consistently sound like you.