Mesakem guides
Microsoft Teams summaries with clear decisions and ownership
Mesakem joins a Microsoft Teams meeting as a visible external participant and turns the conversation into a concise, actionable record. The organizer's Microsoft 365 policies still govern whether the bot can enter directly, waits in the lobby, needs verification or is blocked.
How do you summarize a Microsoft Teams meeting automatically?
Invite Mesakem to an event with a Teams link or connect the relevant calendar. It joins as a visible external participant and may wait in the lobby under the organizer's policy. After the meeting, Mesakem organizes the conversation into key topics, decisions, tasks, owners and unresolved items.
Plan for the lobby and external-participant policy
The organizer's tenant controls the route into the meeting.
Microsoft explains that meeting organizers decide who enters directly and who waits in the lobby, within settings their IT administrator may constrain. Organizers, co-organizers and authorized presenters can be notified and admit people from the lobby.
Some meetings prevent unverified participants from joining or require an email one-time passcode or Microsoft account. Test the bot's admission path with the organizer or IT team before a critical recurring session.
- Working Teams event link
- Defined lobby admission owner
- External and unverified participant policy
- Tenant settings reviewed before critical use
Understand what the participant label means
Teams assigns labels according to identity and verification, not according to Mesakem's summary quality.
Microsoft states that a person joining without entering an email can appear as Unverified, a one-time code can result in Email verified, and an outside Microsoft account can appear as External. Exact behavior depends on the join path and current tenant policy.
Mesakem remains a visible participant subject to organizer control. Its presence is separate from Teams' built-in recording and live-transcription features.
- Visible external participant
- Teams-controlled identity label
- Organizer-controlled admission and removal
- Separate from native Teams recording or transcription
Convert the discussion into work the team can track
The summary is organized around meaning and responsibility rather than a stream of sentences.
Mesakem identifies the meeting context, decisions, next actions, owners and remaining questions. The result is stored in the dashboard and can move through configured delivery channels.
Review names, technical terms, figures, dates and commitments against the source before using the summary for a high-impact decision or sending it outside the intended audience.
- Concise meeting context
- Decisions and rationale
- Actions, owners and stated timing
- Blockers and open issues
- Reviewable source context
Structured notes for Microsoft 365 teams
The output should be short enough to read and detailed enough to execute.
Leadership meetings can retain decisions, owners and review dates. Product and engineering teams can preserve technical choices, blockers, priorities and cross-team dependencies.
Customer Success and cross-organization sessions benefit from a shared record, while still respecting the organizer's guest policy and the sensitivity of information exchanged between organizations.
- Leadership and management
- Product and engineering
- Customer Success and service
- Cross-organization collaboration
Run a short preflight before relying on automatic notes
A successful setup proves admission and output separately.
Use a known meeting to verify the invite, lobby behavior, participant label and host controls. Then check that Mesakem creates the expected summary and sends it only to configured recipients.
If the bot cannot enter, fix the meeting access path first. Do not infer that a summary exists or create a partial record that hides the missing beginning.
- Invite and lobby test
- Participant visibility check
- Summary structure review
- Recipient verification
- No misleading output after failed admission
Questions and answers
Why might Teams label Mesakem External or Unverified?
Microsoft Teams assigns participant labels based on identity and verification path. An external Microsoft account, email one-time code and unverified browser join can produce different labels.
What if unverified participants are blocked?
The bot cannot enter through that path. The organizer or Microsoft 365 administrator must review the meeting's external-participant and lobby policy before the session.
Who can admit Mesakem from the lobby?
Microsoft documents that organizers, co-organizers and presenters permitted by the meeting policy can manage lobby admission. Exact rights depend on the tenant and meeting configuration.
Does Mesakem start Teams native recording?
No such claim is made. External participant presence and Teams' native recording or transcription are separate features controlled within Teams.
Sources and further reading
Vendor capabilities can change. Check the linked documentation for the current availability, plan and environment you need.
- Using the lobby in Microsoft Teams meetingsSource checked:
- Join a meeting without an account in Microsoft TeamsSource checked:
Leave Teams with a clear owner for each next step
Verify the organizer's admission policy, run a known test session and review the resulting decisions and tasks.
Get started