Meetings and calls. Clear next steps.
Every business conversation, ready for the work that follows
Mesakem is an AI meeting assistant for video meetings, uploaded recordings and recorded phone calls from the supported LINK connector. It turns conversations into searchable transcripts, concise summaries, decisions, tasks and owners, then keeps the result available in one workspace.
What does Mesakem do?
Mesakem documents Zoom, Microsoft Teams and Google Meet sessions through a visible meeting bot, processes recordings uploaded to the dashboard, and summarizes recorded phone calls available through its supported LINK connector. The output highlights context, decisions, tasks, owners and open questions instead of leaving the team with a recording or transcript alone.
One workflow for live meetings and existing recordings
Choose the collection method that matches the conversation rather than forcing every source through the same entry point.
For online meetings, invite Mesakem through a connected Google or Microsoft calendar, add the bot to an event, or provide a supported Zoom, Teams or Google Meet link from the dashboard. The bot joins as an identified participant, and the host retains control over admission.
For a conversation that has already happened, upload a recording to the dashboard. Phone calls use a separate post-call flow: Mesakem processes recordings that are available through the supported LINK connector. It does not claim to connect to every PBX or join every phone call live.
- Visible participation for supported online meeting platforms
- Manual upload for an existing recording
- Recorded-call processing through the supported LINK provider connector
- Calendar detection with read-only Google Calendar or Microsoft Calendar access
Move from a conversation to a shared version of what happened
A useful meeting record has to support both verification and action.
Mesakem keeps the detailed record available while creating a shorter layer for day-to-day work. Teams can review the source when wording, a name, a figure or context matters, without reading the entire transcript every time.
Summary templates let teams emphasize the information that fits a sales call, client review, leadership session, weekly sync or another recurring format. Important details should still be reviewed before a sensitive decision or external share.
- Executive context and key topics
- Decisions separated from suggestions
- Tasks with owners and due dates when stated
- Open questions, blockers and dependencies
- Transcript and recording access for verification where available
Keep follow-up close to the people doing the work
A summary is more useful when it reaches the team's existing routine.
Results are available in the dashboard and can be delivered to verified email recipients. The personal Telegram agent supports meeting answers, tasks, status updates and reminders from a phone, using the linked user's workspace permissions.
Mesakem has a documented read-only MCP implementation for Claude and Codex. Confirm availability for your account and environment before configuring it. It lets an authenticated user ask an assistant about summaries, decisions, search results and meeting-derived tasks without exposing recordings, video or full transcripts through that connector.
- Dashboard history for meetings, calls, summaries and tasks
- Delivery only to configured, verified email recipients
- Telegram tasks, updates and reminders
- Read-only MCP tools scoped to the signed-in Mesakem account
Visible capture and reviewable output
Automation should not remove the people responsible for admission, notice and review.
The meeting bot is designed to appear with a clear identity. Platform waiting rooms, guest rules and organization policies can require a host or administrator to approve its entry. Teams remain responsible for participant notice and any consent required by their policy or applicable law.
AI output can misunderstand names, numbers, dates or intent. Review consequential details against the available source before sending a summary widely or acting on a sensitive item.
- Host-controlled admission on video platforms
- Verified recipients for email delivery
- Workspace- and user-scoped access
- Human review for sensitive facts and commitments
Documented MCP implementation; broader developer interfaces remain roadmap items
Review the documented MCP implementation separately from live rollout and planned interfaces.
Mesakem documents an MCP connector configuration for Claude and Codex. The connector is read-only and uses browser-based Mesakem sign-in rather than asking users to paste a Mesakem password or API key into an assistant.
A public REST API and outbound customer webhooks are on the roadmap, not present-tense product capabilities. Teams with those requirements can discuss early-access needs with Mesakem, but should not plan a production integration on them yet.
- MCP: documented authenticated, read-only implementation; confirm account availability
- Public REST API: roadmap
- Outbound customer webhooks: roadmap
- Inbound service webhooks are internal integration mechanisms, not a public outbound product
Questions and answers
Which meeting platforms does Mesakem support?
The visible meeting-bot workflow supports Zoom, Microsoft Teams and Google Meet. Admission can depend on the host's waiting-room, guest and organization settings.
Can Mesakem summarize a recording I already have?
Yes. Existing recordings can be uploaded through the dashboard. This is separate from the live meeting-bot workflow.
Does Mesakem connect to every business phone system?
No universal PBX support is claimed. The current call-recording connector in the product is LINK, and Mesakem processes a call only after an accessible recording is available.
Can I ask an AI assistant about my meetings?
The documented read-only MCP implementation describes Claude and Codex configuration and data access within the signed-in user's Mesakem permissions. Confirm availability for your account and environment first. It exposes summaries, decisions, search and meeting-derived tasks, not audio, video or full transcripts.
Does Mesakem have a public API or outbound webhooks?
A public REST API and outbound customer webhooks are roadmap items. They should not be treated as available product interfaces today.
Turn the next conversation into clear follow-through
Use Mesakem for a supported meeting, uploaded recording or LINK call recording, then review the resulting decisions and tasks with your team.
Get started