Meeting transcription · Thai & English
Record the meeting.
Get the decisions.
Speaker-separated transcripts, AI summaries and scope-aware answers from your meetings — in Thai and English, in the browser, no install.
Sign-in is restricted to Cleverse accounts. Outside the company and want a look? Talk to us — hello@synogram.app
How it works
Three steps, and the meeting is searchable forever.
Record or drop files
Record in the browser — the waveform draws itself, and you can cut the dead air off either end before it uploads. Or drag a whole batch in: 2 GB a file, settings applied once.
Get a transcript and a summary
Speakers separated with timestamps you can click. The summary picks a shape that fits the meeting rather than filling in a template.
Ask, edit, share
Answers grounded in this meeting and its note. Edit the summary by instruction. Share with two levels of access.
Why this one
The details that make a meeting useful later.
Capture in two clicks
Start now. Clear the backlog later.
Hit New recording to capture audio in the browser, or drop in files you already have. Choose the language, expected speakers and whether Synogram should name the meeting when it is done.
Have a folder of recordings? Drop them together. Every file becomes its own meeting, with one set of settings applied to the batch and clear progress for each upload.
Two share tiers
Send the conclusion, not the recording.
Share by colleague email — never a public link. Full access gets the audio, transcript, note and summary. Summary-only gets the summary and nothing else.
Their Ask still works, but it answers from the summary alone — it can't be talked into reciting a transcript it was never given. Pin a version and they keep seeing that one while you keep editing.
Notes that read images
Bring the context the recording cannot hold.
Keep a rich-text note with the meeting — agenda, links, checklists and the details people say before or after the recording starts. It autosaves and stays alongside the transcript and summary.
Paste or drop in a screenshot and Synogram reads the text inside it. The extracted context reaches both the summary and Ask, so the numbers in a finance table do not disappear from the decision.
File and find
Make a long meeting list answerable.
Tag a meeting by topic, client or project, then combine tags and speakers to narrow a growing archive. Synogram can also suggest tags after transcription, reusing the vocabulary your team already uses.
Search runs across titles, summaries and transcript text, with the matching line visible before you open the meeting.
Transcript that keeps names
Clickable timestamps, named speakers, and a dictionary for the terms that matter.
Summaries with memory
Refine in plain language, restore any version, or turn a summary into an infographic.
Ask with a visible scope
Stay with one meeting or, when enabled, ask across the meetings you can access.
Files and connected context
Notes, documents and connected Notion pages can inform the summary and Ask.
Calendar-aware capture
Optionally match a recording to its Google Calendar event and agenda.
Two intentional share levels
Give a colleague the whole meeting, or only the conclusion.
Trim before upload
The off-the-record part never reaches storage or transcription.
Thai and English
Made for code-switching, loanwords and the names generic tools miss.
Works on your phone
Thumb-first layouts, readable type and a dedicated Ask destination.
Realtime, no refresh
Finished transcripts, summaries and shared meetings appear on their own.
Connect your AI client
Ask Claude about last week's meetings.
Synogram speaks MCP, so an AI client can read your meetings where you already work — with no transcript pasted anywhere.
Add the endpoint in Claude — web, desktop or Claude Code — and approve it once with your company account. Then ask in plain language: "what did we decide about pricing last week?", "summarise every meeting tagged hiring", "who owns the Caltrain integration?"
It's read-only. Nothing you connect can edit a note, rename a speaker, delete a meeting, share one, or spend AI credit.
And it sees exactly what you see: every query runs with your own database permissions, not the app's — your meetings plus the ones shared with you, at the tier each share grants. A summary-only share stays summary-only.
There's no API key to copy around. The connection is OAuth, tokens rotate, and Account → Developers lists every connected client with the date it last made a request — and a Revoke button that takes effect on the next call.
Endpoint
https://cloud.synogram.app/api/mcp
Seven tools, all reads
- search_meetings
- list_meetings
- get_meeting
- get_summary
- get_transcript
- get_note
- list_tags
Any client that speaks Streamable HTTP with OAuth works — the URL is all it needs.
Security
It's your company's conversations.
Access is enforced in the database, not by hiding buttons in the interface.
Company sign-in only
Restricted to your company domain. No personal accounts.
Row-Level Security is the boundary
Every meeting, segment, speaker, note and image is scoped in the database, verified by an automated access-control suite.
Audio is private
Stored in a per-owner private bucket and served only through short-lived signed URLs — never a public path. Audio you trim away never gets there at all: the cut is applied in your browser.
Sharing is explicit and revocable
One named colleague at a time. Unshare and access is gone immediately.
Sensitive material is stored separately
A summary-only reader cannot reach the note or transcript even by querying the database directly.
API keys stay server-side
No provider key ever reaches the browser.
Questions
The objections we actually get.
We already record in Meet or Zoom.
Those give you a file. Synogram gives you a transcript with speakers, a summary you can send, and answers you can quote — and it keeps the recording out of the hands of people who only need the summary.
AI summaries are generic.
This one picks its structure from the content, grounds itself in your note as well as the transcript, and can be edited by instruction — "add action items", "translate to Thai" — with every version kept.
Our meetings are in Thai.
So are the ones this was built for. Thai and English in the same sentence, Thai summaries, and a dictionary that fixes the names your transcriber gets wrong — in the transcript itself, not just the summary.
Part of that meeting shouldn't be stored at all.
Then cut it before it uploads and it never becomes a file — not stored, not transcribed, not sent anywhere. Already uploaded? Trim it and the transcript is rebuilt from what's left.
We can't share recordings outside the team.
Then don't. Summary-only sharing sends the conclusion and nothing else, and their Ask can't reach the transcript either.
Another tool, another tab.
Connect it to Claude instead and ask from there — same meetings, read-only, and the connection is one click to cut from the account menu. A connected client can't write anything: no edits, no deletions, no sharing.
What are the honest limits?
Transcription is one pass, not live captions. Google Calendar is optional and read-only; Synogram does not join or record a video call for you. Cross-meeting Ask is an organization setting. Automatic speaker naming is deliberately off, because a confidently wrong name spreads everywhere; renaming once takes seconds. And trimming a transcribed meeting cannot be undone.
Try it with your last meeting.
Upload a recording and see the summary in minutes.