Khulasa for Microsoft Teams
How it works
Paste the Microsoft Teams meeting link
Copy the “Join the meeting now” link from the invitation — a teams.microsoft.com/l/meetup-join/… address — or a personal Microsoft Teams link of the form teams.live.com/meet/…, and paste it into Khulasa. Choose the language, then start now or set a start time. If you connect your Microsoft or Google calendar, Khulasa can pick up the Microsoft Teams links in your events and join on time.
The organiser admits Khulasa from the lobby
Khulasa opens the link, chooses “Continue on this browser”, declines audio and video, types the name KhulasaBot (Recording) and joins as an anonymous guest. Microsoft Teams normally places guests in the lobby: the organiser or a presenter admits it within five minutes. If nobody does, 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 meeting ends, 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 Microsoft Teams meeting that allows guests
Khulasa joins as an anonymous participant — it never signs in to a Microsoft account — so the meeting has to allow anonymous users to join. That is the usual setting, but a tenant admin can turn it off, and then the join button never appears and the recording fails. Channel meetings limited to organisation members, live events, town halls and webinars with registration are not supported.
An organiser who admits the bot from the lobby
Microsoft Teams normally sends anonymous guests to the lobby, where the organiser or a presenter admits KhulasaBot (Recording) like any other external guest. Some tenants label external meeting bots in the lobby and ask the organiser to confirm before admitting them; whatever the label says, the step is the same — admit it within five minutes, or the recording fails without capturing anything.
No Copilot licence, no Microsoft account for the bot
Khulasa does not use Microsoft Teams transcription, recording or Microsoft 365 Copilot, so nobody in the meeting needs a Copilot or Microsoft Teams Premium licence. Nothing is installed in your tenant and no Microsoft Graph permission is granted to the bot. Signing in to Khulasa with a Microsoft account and syncing your Microsoft calendar are separate, optional features of your own Khulasa account.
Recording hours on your Khulasa plan
Every Khulasa plan includes Microsoft Teams. 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; Microsoft Teams may add its own guest label beside the name. The bot 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 organiser to remove the bot, and the recording ends the moment it is removed. Khulasa does not use Microsoft Teams recording, so the “Recording has started” banner is not shown; the named guest and the chat notice are the disclosure. We recommend that the organiser 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 message is not pinned, and if the tenant has turned off meeting chat for anonymous participants the notice cannot be posted, so in that case the organiser should announce the recording.
Compared with the platform's built-in AI notes
Microsoft Teams has its own transcription and, with a Microsoft 365 Copilot licence, AI meeting notes and recap. For organisations that already license Copilot, that may be all they need. The table shows where the two differ so you can choose the right tool for each meeting. The Copilot column describes the product as Microsoft publishes it at the time of writing; check the Microsoft documentation for your licences.
| Microsoft Teams | Khulasa | |
|---|---|---|
| Where it works | Inside Microsoft Teams, for meetings in your own Microsoft 365 tenant. | Microsoft Teams, Google Meet and Zoom meetings, from one workspace, with one set of summaries. |
| Who switches it on | Licensed per user through Microsoft 365 and assigned by the tenant admin; transcription is started in the meeting. | Any member of your Khulasa workspace with the meeting link, organiser or not, on every plan including Free. The organiser admits the bot. |
| Arabic and English | Supports the languages Microsoft publishes for Microsoft Teams transcription and Copilot; 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 Microsoft cloud, inside your Microsoft 365 tenant. | 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 nobody admits the bot from the lobby within 5 minutes, the recording fails without capturing or billing anything. If it is removed, the recording ends and it does not rejoin on its own. Tenants that block anonymous join cannot be recorded, and there is no signed-in fallback.
- Live events, town halls, webinars with registration, breakout rooms, channel meetings limited to members, phone dial-in and Microsoft Teams Rooms devices 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
Do I need a Microsoft 365 Copilot licence to get Microsoft Teams meeting minutes?
No. Khulasa does not use Microsoft Teams transcription, recording or Copilot: it joins the meeting as a guest, records the room's audio itself and produces the transcript, summary, decisions and action items on its own. Nobody in the meeting needs a Microsoft 365 Copilot or Microsoft Teams Premium licence, and nothing is added to your tenant. The recording hours come from your Khulasa plan, which starts free with three hours per member each month.
How do I add the Khulasa notetaker to a Microsoft Teams meeting?
Copy the “Join the meeting now” 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 joins from the browser as an anonymous guest named KhulasaBot (Recording) and waits in the lobby; once the organiser admits it, recording begins. If you connect your Microsoft calendar, Khulasa can join the Microsoft Teams meetings on it automatically, following the auto-record rule you set.
Microsoft Teams shows the bot in the lobby as an external or unverified guest — what should the organiser do?
Admit it, the same way as any external guest. Because Khulasa joins anonymously rather than from a Microsoft account, Microsoft Teams treats it as a guest, and some tenants now label external meeting bots and show a reminder before the organiser clicks Admit. Look for the name KhulasaBot (Recording) — or your organisation's chosen name followed by “(Recording)” — and admit it within five minutes. If it is left waiting, the recording fails and nothing is captured or billed.
Does our Microsoft Teams admin need to allow external bots?
Usually nothing has to change: Khulasa is an anonymous browser guest, so the only setting that matters is whether anonymous users may join meetings in your tenant, which is allowed by default. If your admin has turned that off, the join button never appears and the recording fails — ask them to allow anonymous join for the meetings you record. Some tenants also apply a policy for external meeting bots that asks the organiser to approve them in the lobby; admitting the bot is enough.
Can Khulasa join a Microsoft Teams meeting hosted by another organisation?
Yes, as long as that organisation allows anonymous guests in its meetings, which is the usual setting. You paste the link you were invited with, Khulasa joins from the browser as a guest and waits in the lobby, and the organiser on their side admits it. Everyone in the meeting sees the named guest and the recording notice, so the recording is open. Tell the organiser in advance that Khulasa will ask to join, and check your own policy on recording meetings with external parties.
Can Microsoft Teams recordings and transcripts stay on-premise?
Yes, on the Private Cloud and On-Premise plans, which run self-hosted speech and language models so your audio does not go to a third-party AI provider. Private Cloud is a dedicated, isolated deployment run for your organisation; On-Premise is the same system installed on your own hardware. Both are quoted per organisation — talk to sales. On the cloud plans, recordings are encrypted in transit and at rest, isolated per organisation and never used to train models unless you opt in.
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 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.
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.
Microsoft and Microsoft Teams are trademarks of the Microsoft group of companies. 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.