Khulasa for Zoom
How it works
Paste the Zoom invite link
Use the full invitation link with the meeting ID and passcode in it — for example https://us02web.zoom.us/j/1234567890?pwd=… — and paste it into Khulasa. Any zoom.us or zoom.com address is accepted. Choose the language, then start now or set a start time. If you connect your Google or Microsoft calendar, Khulasa can pick up the Zoom links in your events and join on time.
The host lets Khulasa in
Khulasa opens the meeting through the Zoom “Join from browser” flow as a guest named KhulasaBot (Recording), declines microphone and camera, and lands in the waiting room if the host uses one. Admit it within five minutes. If the host has not started the meeting, or nobody admits the bot, the recording stops there — nothing is captured and nothing is billed.
Get the summary when the meeting ends
Recording starts as soon as the bot is admitted and stops when the host ends the meeting, the bot is removed, or everyone else has left. 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.
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
A standard Zoom meeting, on any Zoom plan
Khulasa joins as a browser guest, so it needs neither Zoom cloud recording nor a paid Zoom licence, and it never signs in to a Zoom account. What matters is the meeting itself: a standard Zoom meeting joined from the browser. Webinars, Zoom Rooms, phone dial-in and meetings that require every participant to be signed in to Zoom are not supported.
An invite link with the passcode embedded
Khulasa needs the numeric meeting ID in the link (the /j/…, /wc/… or /s/… form) and carries the ?pwd= passcode along with it. There is no field to type a passcode separately, so if a link has been stripped of its passcode, ask the host for the full invitation. Personal-link addresses (zoom.us/my/…) usually redirect to the desktop app and cannot be used.
A host who admits the bot
If the meeting uses a waiting room, the host or a co-host admits KhulasaBot (Recording) like any other guest — within five minutes. Nothing needs to be changed in the Zoom account settings, but a meeting set so that only authenticated users can join will keep the bot out, because it never signs in. Ask the host to relax that setting for the meeting, or to start the meeting before the bot arrives.
Recording hours on your Khulasa plan
Every Khulasa plan includes Zoom. 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. A meeting nobody joins 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 a guest named KhulasaBot (Recording) — or the name your organisation chose, always followed by “(Recording)” — muted and without 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. 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 Zoom, so the Zoom “Recording…” indicator and its recording-consent prompt are not shown; the named guest and the chat notice 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. The notice is not pinned on Zoom, and if the host has turned off chat for participants the notice cannot be posted, so in that case the host should announce the recording.
Compared with the platform's built-in AI notes
Zoom has its own AI note-taking through Zoom AI Companion, and for teams whose host accounts include it, it may be all they need. The table shows where the two differ so you can choose the right tool for each meeting. The AI Companion column describes the product as Zoom publishes it at the time of writing; check the Zoom documentation for your account.
| Zoom | Khulasa | |
|---|---|---|
| Where it works | Inside Zoom meetings, when the host's Zoom account includes AI Companion. | Zoom, Google Meet and Microsoft Teams meetings, from one workspace, with one set of summaries. |
| Who switches it on | The meeting host, on an eligible Zoom account; participants are shown a disclosure while it is active. | Any member of your Khulasa workspace with the invite link, host or not, on every plan including Free. The host admits the bot. |
| Arabic and English | Supports the languages Zoom publishes for AI Companion; 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 Zoom cloud, under the host's Zoom 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 the host has not started the meeting or nobody admits the bot within 5 minutes, the recording fails without capturing or billing anything; the bot does not keep retrying. If it is removed, the recording ends and it does not rejoin on its own. Meetings that require signed-in Zoom users cannot be joined.
- Webinars, breakout rooms, Zoom Rooms and phone dial-in are not supported, and there is no way to enter a meeting ID or passcode without a link. 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 need Zoom cloud recording or a paid Zoom plan?
No. Khulasa does not use the recording feature built into Zoom at all: it joins the meeting from the browser as a guest participant and records the room's audio itself, so neither Zoom cloud recording nor a paid Zoom licence is involved, and the bot never signs in to a Zoom account. What it needs is a standard Zoom meeting that guests can join from the browser and an invite link that still contains the passcode. The recording hours come from your Khulasa plan, which starts free.
Can I record a Zoom meeting when I'm not the host?
Yes. Khulasa is a separate guest participant, so any member of your workspace who is allowed to record can request a recording of a Zoom meeting they were invited to — you only need the invite link. The host still has to admit the bot from the waiting room and everyone sees it and the recording notice, so the recording is open, not hidden. Check your organisation's policy and local law on recording meetings before you start.
What do participants see when the Khulasa bot joins a Zoom meeting?
A guest named KhulasaBot (Recording) — or the name your organisation set, followed by “(Recording)” — appears in the participant list, muted and without video. As soon as it is admitted 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. It never speaks or shares a screen, and if the host removes it the recording ends at once.
Does Zoom show a recording-consent prompt?
Not for Khulasa. The Zoom consent prompt and the “Recording…” indicator belong to the recording feature built into Zoom, which Khulasa does not use. Instead, the disclosure is the named guest in the participant list and the bilingual notice Khulasa posts in the chat as soon as it is admitted, with a link to the recording notice. If the host has disabled chat for participants the notice cannot be posted, so we recommend the host also announces the recording at the start of the meeting.
How does Khulasa compare with Zoom AI Companion?
They solve the same problem in different places. Zoom AI Companion is switched on by the host, runs inside Zoom meetings on eligible Zoom accounts, and keeps its output in Zoom. Khulasa is requested by any member of your workspace, host or not, works across Zoom, Google Meet and Microsoft Teams from one place, is built for Arabic and English in the same meeting, and can run as a private cloud or on-premise with self-hosted models. Many teams use both for different meetings.
Can I get Arabic meeting minutes from a Zoom call automatically?
Yes. When the recording finishes, Khulasa produces a transcript, a summary, decisions and action items, written in the language that dominated the meeting — so an Arabic meeting yields Arabic minutes, with English terms kept in Latin script. They appear in your dashboard and the summary is emailed to whoever requested the recording. For recurring meetings, schedule them once or connect your calendar with auto-record, and the minutes arrive after every session without anyone starting a recording by hand — the host still admits the bot when it arrives.
Also works with
Khulasa for Google Meet
Joins from its own Google account, asks the host to admit it, and records Google Meet meetings from free accounts and Google Workspace alike.
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.
Zoom is a trademark of Zoom Communications, Inc. 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.