Skip to content
Menu

For your company

Avna TeammateA colleague who reads your meetings, docs and tasksTeam operationsBriefs, standups, reply-to-actMeeting intelligenceRecaps that assign their own tasksCustomer answersAnswers from your own dataEverything for businessThe teammate, customer answers and the API, on one pageWhat we keepWhat is stored, what is deleted, and who can open itSecurityWhat is in place, and what is not

For you

Goals & coachingPlans that adjust, not diePersonal AIEvery model, one subscriptionPricing
Start free

Solutions · For your team

Meetings that finish their own follow-up

Persian and English in the same sentence, six voices, nobody taking notes, and owned, dated work at the end of it. Watch the whole thing below before you sign up for anything.

Start with Avna TeammateSee a meeting

From the first hello to a ticket in Jira

Avna offers to record, follows a sentence that starts in Persian and ends in English, names the voices it can, and turns the decisions into owned, dated work. It plays on its own; press Replay to watch it again.

The recorder in the corner is Avna's Chrome extension: it sits inside the call, so there is no share picker to get wrong. Without it, Avna records from the browser tab you share.

No recording at all? Paste the notes and get the same write-up.

avna: follow-up
  1. Record
  2. Transcript
  3. Recap
  4. Tasks
  • Reza: wire the payment webhook before Thursday's QA window.
Wire the payment webhookThursday
Reza · from product syncBoardJiraTelegram
JiraPAY-142

The owner and the date come from the sentence that created them. One task, in every place the team already looks, not three copies to keep in step.

Explore the console

If you would rather drive: the same meeting across four tabs, with the switches live. Turn speaker naming off, drop to captions only, change the kind of meeting, and watch the result get worse.

The minutes

The document you were going to write up on Thursday

Not a wall of transcript and not a paragraph of prose: a page with four headings, written to a contract, in the panel you read and edit it in.

  • Four headings, always the same four: decisions, actions, numbers and dates, open questions.
  • A heading with nothing under it is left out, never written empty.
  • Every action is “Owner, the commitment”, one deliverable a line. Nobody named? It says Unassigned.
  • Yours to edit, and yours to take away, markdown or PDF, for the people who were not in the room.
MINUTES
Markdown

Decisions

  • Billing v2 will ship behind a feature flag rather than waiting for the wallet work.
  • QA takes Thursday and tests against production data.
  • Wallet pricing is deferred until the flag is live.

Actions

  • Reza: wire the payment webhook before Thursday's QA window.
  • Sara: load-test wallet top-up at three times current peak.
  • Unassigned: decide wallet pricing once the flag is live.

Numbers and dates

  • Thursday: the QA window for billing v2, against production data.
  • Three times current peak: the load-test target for wallet top-up.

Open questions

  • Whether wallet pricing changes before or after the flag is removed.
Last written by Avna · todayDownload as MarkdownSave as PDF

Ask every meeting at once and get the meeting back

Nobody remembers which call a decision was made on. That is the question people actually bring, so it is answered from the whole history, with the meetings it came from attached.

  • Every meeting you attended is searchable, not only the last one.
  • The answer carries the meetings it came from, so you can open them.
  • Only meetings you were in. Owners and admins get no override.
  • Ask in Persian about a meeting held in English. The answer comes back in the language you asked.
avna: ask
Where did we decide to ship billing behind a flag?

In the product sync on 12 August. Reza proposed it, Sara agreed on the condition that QA gets a Thursday window against production data. It has not been revisited since.

From

Product sync · 12 AugBilling v2 kickoff · 4 Aug

Answers come from meetings, not from a model's memory. Nothing found means nothing found.

Walk in already knowing what last time left open

The recap is written after. This arrives before, assembled from the last meeting with these people, and from what they owe each other right now.

  • It lands before the meeting, not in a summary afterwards.
  • Only work this meeting is about. A true but unrelated line is how people learn to stop reading briefs.
  • First meeting with these people? It still has something to say.
Product sync
Tomorrow, 10:00 · 6 people
Pre-brief

Agenda

  • Billing v2: go or no-go
  • Wallet pricing

Left open last time

  • Reza: wire the payment webhook
  • Nobody: decide wallet pricing

Decided last time

  • Ship billing v2 behind a feature flag
  • QA window on Thursday, against production data

Due from people in this meeting

  • Sara: load-test wallet top-up, due Thursday

Carrying the most

  • Sara: four open items this week

Assembled from your own meetings and tasks. No line here is invented, and a section with nothing in it is left out rather than padded.

Around the recap

A recorder inside the call

The Chrome extension records from the meeting itself (no share picker, no wrong tab) and brings the platform's captions with it to name the voices.

It offers to record

When a meeting with colleagues starts, a card asks whether to record it. Record-now is there too, for the call nobody put in the calendar.

Minutes you can ship

An editable minutes doc under every meeting, with print and markdown export for the people who were not in the room.

One task, three places

A task from a meeting lands on the board, in Jira if you use it, and in its owner's Telegram. The same task, not three copies to reconcile.

You can see what it cost

Every transcription and every recap is metered against the workspace wallet, itemised by meeting. No per-seat guessing.

Audio doesn't linger

Recordings are transcribed, then permanently deleted, within the hour even if transcription fails. Meetings stay attendee-only, with no owner override.

Decide in the meeting. Ship after it.

Start with Avna TeammateSee a meeting

Free to start, no card · Telegram, Jira, Google Calendar · what we keep and throw away →