Khulasa for Google Meet
How it works
Paste the Google Meet link, or schedule it
Paste any link whose address is meet.google.com — for example https://meet.google.com/abc-defg-hij — into Khulasa and choose the language: Auto-detect, Arabic + English, English or Arabic. To record later, set a start time. Or connect your Google Calendar and let Khulasa join the Google Meet meetings on it automatically, following the auto-record rule you choose.
The host admits Khulasa
At the start time Khulasa opens the meeting in a real browser, signed in to its own Google account, with microphone and camera off, and asks to join. Google Meet places that request with the host. Admit it within five minutes; if nobody does, the recording stops there — nothing is captured and nothing is billed. While it waits, your dashboard shows “Waiting to be admitted”.
Read the summary after the meeting
Recording starts the moment the bot is admitted and ends when the meeting ends or the bot is removed. The audio is uploaded, transcribed and analysed, and the transcript, summary, decisions and action items appear in your dashboard. The person who requested the recording also receives the summary by email, and the whole team can be notified in the app.
What you get from every meeting
Transcript
The full text of the meeting with speaker labels and timestamps, in Arabic and English exactly as spoken. Click any line to jump to that moment in the audio.
Summary
A clean, readable account of what was discussed, written in the language that dominated the meeting.
Decisions and risks
What was agreed and what was flagged as a risk, pulled out as their own lists so nothing gets lost in the transcript.
Action items
Who does what, with an owner and a due date where one was mentioned — ready to share, or to turn into Jira issues from the meeting page.
Arabic and English in the same meeting
Most meetings in the region are not held in one language. Khulasa transcribes Arabic and English in the same meeting — even inside the same sentence — and keeps English product names, tools and terms in Latin script instead of rewriting them in Arabic letters. Choose Auto-detect, Arabic + English, English or Arabic when you request the recording; the summary, decisions and action items come back in the language that dominated the conversation. We make no claim for specific dialects or for other languages, and the app itself is fully bilingual with a right-to-left Arabic interface.
Requirements and permissions
Any Google Meet link that opens in a browser
Khulasa works with Google Meet meetings created from a personal Google account as well as from Google Workspace. Nothing has to be installed and no Google Workspace admin setting has to change: the bot goes through the normal Google Meet join flow like any other participant. Dial-in numbers and PINs are not meeting links and cannot be used.
A host who admits the bot
Because Khulasa joins from its own Google account, Google Meet normally shows the host an “Ask to join” request rather than letting the bot straight in. Google Meet may also list join requests from accounts it does not recognise in a separate place for the host to review, so tell the host in advance that Khulasa will ask to join and needs to be admitted within five minutes.
You do not need to be the host
Any member of your Khulasa workspace who is allowed to record can request a recording. Khulasa appears in the meeting as its own participant, so you can record a Google Meet meeting you were invited to, not only the ones you organise — as long as the host admits it. Meetings restricted to a single Google Workspace organisation refuse outside accounts, and those cannot be recorded.
Recording hours on your Khulasa plan
Every Khulasa plan includes Google Meet. Each member has their own monthly allowance of recording hours — 3 on Free, 30 on Team, 120 on Business, unlimited on Private Cloud and On-Premise — and only the minutes the room was actually occupied are counted. If nobody joins the meeting, it costs nothing, and the app warns you when your allowance is running low.
What attendees see
Khulasa never records silently. In the meeting, participants see one extra participant with a clearly identifiable Khulasa name, muted, with no video: it has no microphone and no camera, so it never speaks and never shares a screen. As soon as it is admitted, and before it starts recording, it posts a notice in the meeting chat in English and then in Arabic, saying that the meeting is being recorded to produce a summary and linking to the recording notice on khulasa.ai. On Google Meet the English message is also pinned where the client allows it, so people who join late see it too. Anyone who would rather not be recorded can ask the host to remove the bot, and the recording ends the moment it is removed. Khulasa does not use the recording feature built into Google Meet, so the native Google Meet recording indicator is not shown — the chat notice and the named participant are the disclosure. We recommend that the host also mentions the recording when the meeting opens, and that you check your organisation's policy and local law before recording.
The chat notice reads: “📝 Khulasa Notetaker has joined and is recording this meeting to produce a summary. Details and your rights: https://khulasa.ai/en/legal/recording — ask the host to remove it if you'd prefer not to be recorded.” The same text follows in Arabic. If the host has turned off chat for participants, the notice cannot be posted and the recording continues, so in that case the host should announce it.
Compared with the platform's built-in AI notes
Google Meet has its own AI note-taking through Gemini, and for teams that already have it in Google Workspace it may be all they need. The table shows where the two differ so you can choose the right tool for each meeting. The Gemini column describes the product as Google publishes it at the time of writing; check the Google documentation for your Google Workspace edition.
| Google Meet | Khulasa | |
|---|---|---|
| Where it works | Inside Google Meet, for meetings hosted on an eligible Google Workspace account. | Google Meet, Zoom and Microsoft Teams meetings, from one workspace, with one set of summaries. |
| Who switches it on | Available on eligible Google Workspace editions; an admin enables it and a participant turns it on in the meeting. | Any member of your Khulasa workspace with the meeting link, on every plan including Free. The host admits the bot. |
| Arabic and English | Supports the languages Google publishes for Gemini in Google Meet; refer to that list for Arabic and for meetings that mix languages. | Built for Arabic and English in the same meeting, including sentences that switch mid-way, with English terms kept in Latin script. Summaries follow the dominant language. |
| Where the data lives | In the Google cloud, inside your Google Workspace account. | Your Khulasa workspace in the cloud, or self-hosted models in a private cloud or on your own servers for regulated teams. |
Limits and what is not supported
- A single recording runs for up to 4 hours, or until your remaining monthly hours run out, whichever comes sooner. If it is your allowance that ends the recording, the bot says so in the chat before it leaves.
- Recording is audio-only by default (an .m4a file). An audio + video mode exists as a deployment-level option and is not chosen per recording. Screen shares, chat messages and live captions are not captured as separate files.
- Transcription covers Arabic and English. We make no claim for specific dialects or other languages, and there is no live transcription during the meeting: everything is produced after it ends.
- If no host admits the bot within 5 minutes, the recording fails without capturing or billing anything. If the bot is removed, the recording ends and it does not rejoin on its own. Meetings limited to one Google Workspace organisation cannot be joined.
- Breakout rooms, live streams, companion mode and phone dial-in are not supported. One active recording per meeting: a second request for the same link is rejected while one is already running.
Security and deployment
Recordings, transcripts and summaries are encrypted in transit and at rest, isolated per organisation, and never used to train models unless you opt in. Organisation roles, groups and per-recording sharing decide who sees each meeting; public share links stay off until an admin enables them and expire by default. Retention policies, legal hold and redaction of emails and phone numbers in stored analysis are available. Organisations that cannot send audio to a cloud provider can run Khulasa as a private cloud or on-premise, with self-hosted speech and language models, quoted per organisation.
Pricing
Google Meet, Zoom and Microsoft Teams are included on every plan, starting with Free: three seats and three recording hours per member, per month, with no card required. Team and Business add more hours per member — 30 and 120 — and let you add seats as you grow; Private Cloud and On-Premise are quoted per organisation with unlimited hours. Only the time the room was actually occupied counts against your allowance.
Frequently asked questions
Does Khulasa work with the free Google Meet plan, or do I need Google Workspace?
Both work. Khulasa only needs a Google Meet link that opens in a browser, so meetings created from a personal Google account and meetings hosted on Google Workspace are handled the same way. No Google Workspace licence, admin approval or paid Google Meet recording feature is involved: the bot joins the way an invited person does. The one exception is a meeting restricted to members of a single Google Workspace organisation, which refuses outside accounts and therefore cannot be recorded.
How do I add the Khulasa bot to a Google Meet call?
Copy the meeting link from the invitation, open Khulasa, choose Record a meeting, paste the link, pick the language and press Start recording — or set a start time to record later. Khulasa then asks to join the meeting; once the host admits it, recording begins. If you connect your Google Calendar, Khulasa can join the Google Meet meetings on it automatically, following the auto-record rule you set: all meetings, only the ones you organise, or those matching a keyword.
Do attendees see that the meeting is being recorded?
Yes. Khulasa appears in the participant list under a clearly identifiable Khulasa name, and as soon as it is admitted it posts a notice in the meeting chat, in English and Arabic, with a link to the recording notice. On Google Meet that message is also pinned when the client allows it. The native Google Meet recording indicator does not appear, because Khulasa does not use the recording feature built into Google Meet, so the chat notice is the disclosure — and we recommend the host mentions it as well.
What if Google Meet puts the bot in a review queue, or the host doesn't admit it?
Khulasa waits up to 5 minutes for someone to admit it, and during that time the recording shows “Waiting to be admitted” in your dashboard. If the host has not started the meeting yet, the bot keeps retrying for those 5 minutes. If nobody admits it, the recording fails, nothing is captured and no recording hours are used. Google Meet may show join requests from accounts it does not recognise in a separate list, so ask the host to look for Khulasa there and admit it.
Can I record a Google Meet meeting if I'm not the host?
Yes. Khulasa is a separate participant, so any member of your workspace who is allowed to record can request a recording of a meeting they were invited to. The host still has to admit the bot, and everyone in the meeting sees it and the recording notice, so you are recording openly rather than in the background. Check your organisation's policy and local law on recording meetings before you start; the recording notice explains what is captured and how participants can object.
Does it transcribe Arabic and English in the same meeting?
Yes. Choose Arabic + English, or leave it on Auto-detect, and Khulasa transcribes both languages in one Google Meet meeting — including sentences that start in Arabic and finish in English — while keeping English names and terms in Latin script. The summary, decisions and action items come back in the language that dominated the conversation. We do not claim coverage of specific dialects, and languages other than Arabic and English are not supported.
Also works with
Khulasa for Zoom
Joins from the browser as a guest named KhulasaBot (Recording) — no Zoom cloud recording, no paid Zoom plan, just the invite link with its passcode.
Khulasa for Microsoft Teams
Joins as an anonymous guest from the lobby, with no Microsoft 365 Copilot licence and nothing installed in your tenant.
Integrations
Khulasa joins Google Meet, Zoom and Microsoft Teams meetings as a named participant, records the room, and turns Arabic and English speech into a transcript, a summary, decisions and action items. Nothing to install on the platform side: paste a meeting link, or connect your Google or Microsoft calendar and let it join on time. Action items can be sent to Jira from the meeting page.
Google Meet™ is a trademark of Google LLC. Khulasa is an independent product and is not affiliated with, endorsed by, or sponsored by Google, Zoom, or Microsoft. Product names are used for identification purposes only.