afka uses analytics cookies to see how visitors use the site, and a service that can identify the company a visitor works for. We do not sell your data. Decline and none of it loads.
It joins the call and answers in the room.
afka sits in your Zoom, Google Meet and Microsoft Teams calls as itself. It says who it is, it answers when someone asks it something out loud, and what was decided is written down and turned into work before anyone has closed the tab.
@afka join this one in ten minutes — https://meet.google.com/wks-wqmx-knr
I'll be there. I'll introduce myself when I join, and anyone in the room can ask me something out loud. Notes, the transcript and anything you commit to come back here under your name when the call ends.
A colleague you can invite, not a recorder you have to configure.
A notetaker is a setting somebody turns on once. This is a coworker anyone on the team can pull into a room, that talks back when it is spoken to, and that leaves the work behind rather than a file.
Whoever has the link invites it. Not only the owner, not only an admin, and not only from the web app.
Five members of the same workspace can put it in five different calls at the same time, and it is in all five.
The same colleague on all three. You paste a link; it works out where the call is and turns up.
The call, and everything the call was supposed to produce.
Four jobs. Three of them are the ones nobody on the call wants, and the fourth is the one a recorder cannot do at all.
It takes part
Ask it something out loud and it answers out loud. Who is here. What did we agree last time. What is that number. It speaks when it is spoken to and stays quiet the rest of the time.
Notes and a transcript, not a recording to re-watch
What was decided, who was there, and what is still open — as a short structured note, with the full transcript beside it. afka is never listed as a participant of your meeting, because it was not one.
What was promised becomes work
A commitment said out loud becomes a task, and a time said out loud becomes a calendar event. The follow-up email is drafted and waiting — addressed to the other side, never to you.
It comes back to the person who invited it
Five calls in one workspace do not become one pile. Each one is filed under the member who sent the link, in their account, with their notes and their tasks.
Paste a link. That is the whole setup.
No plugin in the meeting app, no calendar to hand over, and nothing for an admin to approve first.
Send the link where you already are
Paste the call link at afka in Slack or Microsoft Teams — or in the app, if that is where you are. Any member of the workspace can do this.
It joins and says who it is
afka appears in the call under its own name and introduces itself, so nobody in the room is unclear about what just joined.
It listens, and answers when asked
It follows the conversation across several speakers and answers out loud when someone puts a question to it. It does not interrupt and it does not narrate.
The work lands under your name
Notes, transcript, tasks, calendar events and a drafted follow-up — in your account, in your workspace, in the channel you asked in.
It never joins a call nobody invited it to, and it never joins silently.
Somebody asks it a question. It answers.
This is the line between a coworker and a recorder. A recorder is something you review afterwards. This one is in the conversation while the conversation is still worth having.
Its own turns go into the transcript from what it said, not by transcribing its own audio back.
afka, who is here, and what did we agree on pricing last week?
I'm afka, the assistant Marcus invited. There are three of you in the room. Last Tuesday you agreed to hold the Team plan at its current price until the annual toggle ships, and to revisit the overage rate after the first ten paying workspaces.
Four things land, and none of them is a recording.
They arrive in the channel you asked from, under your name, within minutes of the call ending.
The note
What was decided, who was there, what is still open. Short enough that somebody who missed the call actually reads it.
The transcript
Speaker by speaker, including afka’s own turns. Wordless segments are not turns and are not shown.
The tasks and the calendar
Every commitment spoken out loud, as a task with an owner. Every time agreed out loud, as an event in the calendar.
The follow-up, drafted
Written to the other side of the call, not to you, and left for you to read before anything is sent.
Where the call happens, and where the work lands.
Invited from Slack, Microsoft Teams or the app. Tasks and events land in the tools your workspace already uses.
One hire does not mean one call at a time.
A workspace is a team, not a queue. Five members can each send a different link in the same ten minutes, and none of them waits for the others.
Anyone sends it
Every member of the workspace can invite it from Slack, from Microsoft Teams, or from the app. There is no admin step and no seat to assign first.
It runs them in parallel
Five calls at the same time is not a special case. Each one is its own session with its own room, its own transcript and its own set of actions.
Each one comes back to its own person
The record is filed under the member who invited it and surfaced in their account. Your call is your call, even when four colleagues are on four others.
What it will not do, stated plainly.
A colleague in your meetings is only worth having if the limits are written down before you invite it.
It will not join a call nobody invited it to
There is no scanning of your calendar looking for rooms to enter. A person sends a link, and consent is recorded against that person before it joins.
It will not sit in the room silently
It introduces itself when it arrives. If a room does not want it, remove it — from the meeting or from afka — and the session closes.
It will not write itself into your meeting
The attendee list of your meeting is the humans who were there. afka is not one of them and does not appear as one in the record.
It will not send the follow-up for you
The draft is written and left for you. Anything that touches money stays inside the caps you set, on this surface exactly as on every other.
The call is not a separate product.
It is the same colleague that already answers in your channels, and it remembers the call the same way it remembers everything else.
It knew the context before the call
Whatever your workspace has already told afka is in the room with it — the decisions, the numbers, the way your team words things.
The call is context afterwards
Ask a week later what you agreed and it answers from the call, in the channel, without you finding the note.
The work goes where work goes
Tasks, events and drafts from a call land in the same places as the ones from a message. There is no second inbox to check.
One bill, one log
Meetings are metered like everything else, and every action taken from a call is written to the same append-only log as the rest.
Before you put it in a room.
Do I have to be an owner or an admin to invite it?+
No. Any member of the workspace can send a call link at afka from Slack, from Microsoft Teams, or from the app, and it joins that call. This was a real limit and it was removed.
Can it be in more than one call at a time?+
Yes. Five members of the same workspace can put it in five different calls simultaneously. Each call is a separate session and each record is filed under the person who invited it.
Does it actually speak, or does it only listen?+
It speaks. It introduces itself when it joins, and it answers out loud when someone in the room puts a question to it. It does not volunteer commentary and it does not interrupt.
Who knows it is there?+
Everyone. It joins under its own name and says what it is. Consent is recorded against the member who invited it before it joins, and there is no silent mode.
Put it in your next call.
Paste the link in Slack and see what comes back when the call ends. No card, no sales call.