SMeetNew · Secret chats and bots in team rooms
Every meeting your company ever had, answerable in one line.
Calls are recorded, transcribed per speaker and indexed the moment they end. Ask a question in plain language and get the answer with the exact second it was said. Chat and HD video are included, and every AI answer respects the conversations you can already open.
Also on the web and on Android
smeet · meeting memory
Why did we push the migration to next sprint?
Answer
Because the plan needed rewriting before the infra review, and the review lands on Thursday. Decided by Anna Jones on 12 March, in the planning call 1
2 recordings · 1 message · searched 14 calls
“The plan needs rewriting before the infra review, so migration goes to next sprint.”
36:40“Agreed — I will book the room for Thursday morning.”
39:484
private Focus shelves, filled from calls and chats
99
languages transcribed, detected automatically
11
languages your own voice can speak
2 GB
per file, shared directly into a conversation
How the memory gets made
Nobody takes notes. The record stays with the conversation.
01 · The call happens
Recording starts with the first media stream if the group owner turned it on. Nobody has to invite a note-taker or move the conversation into a separate meeting tool.
02 · Every speaker gets a name
Whisper labels each line with the person who said it and timestamps it to the second. Download the result as text or subtitles.
03 · Ask it like a person
Search runs with your access rights, so an answer can never quote a room you were not in. Every claim links back to the second it came from.
When is the migration due, and who owns it?
Anna Jones, Thursday. Agreed at the end of the 12 March planning call.
38:12 Infra & SRE
After the call
The summary writes itself, with the receipts attached.
Decisions, owners and due dates come out of the same transcript, so nothing is invented and everything is quotable. Speaking time is there too, for the meetings where one person did all the talking.
Decisions, not bullet points
Each one carries who decided it and the second it was said, so it can be reopened rather than argued about.
Owners resolved by voice
The assignee comes from the speaker track, and when the name was never said the task asks the room instead of guessing.
Nothing published silently
Below the confidence threshold a summary stays a draft. You confirm it, or it never enters the archive.
Release 4.2 planning
42:18Team agreed to ship 4.2 on Thursday after the infra review. Migration risk moves to next sprint, Anna owns the revised plan.
Action items
- AJRevised migration plan
- DPBook the infra review room
- SKCut the 4.2 release notes
Who spoke
Personal accountability
Nobody has to chase anybody.
Every question put to a person and every promise they made out loud lands on their own Focus screen, with the quote and the second it was said. Nothing is assigned by hand, and nothing is visible to anyone else — there is no dashboard of other people’s lists, on purpose.
- Four shelves, filled from calls and chats: waiting on you, you promised, on you to decide, for your information.
- A line closes itself the moment the person answers in the thread. Nothing has to be reported as done.
- No completion rating and no aggregate of who missed what. A list people distrust is a list people stop opening.
- Handover is the single exception, and an audited one: an admin moves an open list to a successor with the reason recorded before the package is shown, a 15-minute preview, and no access to anybody’s chats.
Waiting on you
3“Are we still doing the migration this sprint?”
Marina asked you · Release 4.2 call · 12:40
You promised
2On you to decide
1For your information
4One optional morning digest per person · counts only, never the text
Institutional memory
The most expensive question in any company, answered in one line.
“Why did we do it this way” normally costs an hour of archaeology across three tools. Here it costs a question: the decision itself, the reason recorded at the time, who owned it, and a button that plays the second it was agreed.
- A decision is a record with an owner, a status and a review date — not a sentence in last quarter’s notes.
- When a new decision contradicts a live one, the thread says so and quotes the old one, before the contradiction ships.
- Superseded decisions stay readable with the chain that replaced them, so a reversal is reopened rather than re-argued.
- A year in, this is the part of the company that cannot be carried over to another chat app. It only accumulates.
This contradicts a decision from 12 March
Billing is calculated on our side
Reason at the time: “we do not want to depend on a payment provider we cannot host.”
Play 41:18Weekly digest · Monday
Store sessions in Redis, not in Postgres
Replaced by “One store, Postgres” · 2 September · Ivan Petrov
4 new · 1 replaced an older one · 2 due for review this week
-
Can you take the infra review?Taking it. Pinned the checklist.
Messaging
AI-assisted drafts, polls, shared checklists, locations, message links, threads, pinned chats and an edit history nobody can quietly rewrite.
-
DPSKAJMR
Calls and conferences
Start from any chat. Screen sharing, blurred backgrounds, per-person network bars, and guest links for people outside the company.
-
0:47
DELass uns das Infra-Review auf Donnerstag verschieben.
Played back in Ivan’s own voice
Voice, in any language
Record your voice once. From then on every voice message can be heard in 11 languages, still sounding like you.
Organisations
Several organisations under one login, without mixing their work.
Each organisation is a space with its own chats, groups, member directory and search. A person belongs to as many as they actually belong to, with a separate profile in each, and one conversation never belongs to two of them at once.
Space
Chats, groups and people belong to one space. The same person is a separate chat in each.
What the product enforces
A clear boundary per space
Chats, groups, the directory and search follow the selected organisation rather than spilling into one global list.
Membership decides visibility
A person is findable by people who share a space with them. The member directory of an organisation is that organisation’s, and stops there.
One conversation, one space
A colleague somebody also knows privately is two separate threads. The work one is the organisation’s; the other one is not.
Nothing is backdated
Joining an organisation never pulls a person’s existing threads, files or recordings into it. Policies apply to what happens after they join.
What the admin does
Creates the organisation
A space starts with an owner, its own member list and its own profile fields.
Binds the domain
Confirming a work address on a domain you own turns into membership automatically, or into a request for an admin to approve.
Hands out invitations
A QR code and link with a role, a lifetime and a use limit. Print it for the onboarding meeting; revoke it and the link and the code die together.
Manages membership
Roles, guests for contractors and clients, and suspension. A suspended membership loses the organisation’s chats, groups and directory; the conversations stay with the company.
What the employee sees
The space is always visible
The switcher above the list and the profile inside each organisation make it clear which working context is open.
Their own switcher
Space above the chat list, account in Settings. Work and personal life in one app without being in one list.
Their own profile per space
Display name, @handle and job title belong to the organisation. The same login, a different presence.
A private Focus
What is on them is theirs. See above: no manager’s view of it exists.
Secret one-to-one conversations
When the platform itself should not be able to read the message.
A secret chat is end-to-end encrypted between two selected protected devices. The service transports ciphertext, while the keys and readable history remain on those devices. That boundary is technical, not an administrator setting.
- Outside server-side intelligenceBecause SMeet cannot read the content, secret chats are not included in Meeting Memory, AI summaries or organisation-wide search.
- A named receiving deviceEach person chooses the protected device that receives secret-chat invitations. Old or lost devices can be revoked independently.
- Expiry after both sides readChoose the lifetime in the composer. A system line tells both people what changed, and expired content disappears without a placeholder.
- More than plain textEncrypted photos, photo sets, video, files, voice, round video, locations, polls and shared lists stay in the same protected conversation.
Bots for organisationsPilot
Put the workflow bot in the room where the team works.
Bots handle support, request status, feeds, lookups and moderation in private chats, groups, topics and channels. Your developers write against the SMeet Bot API and run the program on your servers. The organisation decides whether bots may exist; the owner of each room decides what an installed bot may read and do.
Only addressed commands and replies are delivered
Scenarios
Support desk
A private request becomes a ticket in the operator group, with replies and files travelling through the bot instead of a second helpdesk UI.
Feeds in topics and channels
Release notes, project news and RSS updates arrive in the exact team room that needs them, immediately or as a digest.
Internal lookups
The on-call rota, stock levels or a CRM record, answered when the bot is mentioned in the conversation.
Moderation
A group bot can detect floods and spam, then delete or remove only when those permissions were granted explicitly.
What the admin and owner control
Creating and running bots
Two separate organisation switches. Turning runtime off stops every bot of the organisation at once.
Each installation
The group or channel owner installs the bot and chooses receive-all, send, files, pin, delete, ban and channel-post permissions independently.
Reading all is off
By default the bot sees addressed commands, mentions, replies and button presses, not every human conversation.
No old history
Installing a bot never reveals messages from before it joined the room.
Where the code runs, and what it reaches
Outside SMeet
The bot’s program runs on your servers, or wherever your developers put it. SMeet never runs bot code.
One space per token
A token works only in the organisation where the bot was created and cannot reach chats, people or files anywhere else.
Explicit scope everywhere
Private messages require Start. Group and channel actions require an installation and the matching permission. Revoking either stops access.
Limits and reports
Rate limits per chat, per bot and per owner. People can report a bot, and SMeet administrators can suspend it.
Four SMeet bots
A compact operating layer for the team.
@search_bot
Answers with sources
Research inside the discussion, with links and the time the results were checked.
@feed_bot
Feeds and digests
RSS and Atom updates for private chats, groups, topics and announcement channels.
@helpdesk_bot
Tickets in chat
A clear customer thread on one side and an operator queue in a protected group on the other.
@guard_bot
Group moderation
Rules, flood and spam detection, observation mode and permission-bound actions.
Work in the chat
A rough message can become a decision people can act on.
Polish a draft with AI, ask the room with a poll, turn the outcome into a shared checklist and link back to the exact message. Location cards keep field work in the same conversation. Nothing is sent or decided until a person taps the button.
See one conversation go from question to finished work.
Try the web app now, or bring the native apps to a real meeting. The chat, call, transcript, Focus item and decision stay connected.
macOS
Native app, menu bar, dock badge
iPhone and iPad
CallKit calls, VoIP push, full multitasking
Android
Full-screen call notifications
Web
Chrome, Safari, Firefox, no plugins
Windows
Planned — use the web app