What's inside Pricing FAQ Blog Documentation Sign in

Action items taken from the meeting itself

Almost everything said on a call that sounds like a commitment is not one yet. Whisperer keeps a promise and a task apart on purpose, and only the second one lands on a board — because only you can decide which is which.

Every card carries the meeting it came from

  • Task Ivan — pull the churn numbers by Wednesday Product standup · owner and date agreed out loud
  • Promise Somebody should look at the onboarding drop-off Kept next to the meeting — no owner was named
  • Open question Who takes the new wording to legal Stays open until a person closes it

Distinction

Why not turn every commitment into a ticket

Because a board full of things nobody agreed to track is worse than no board. The moment a tool starts creating a task from every sentence containing a name and a verb, people stop trusting the board, and then they stop looking at it.

A promise Lives next to the meeting
  • Something was said out loud that sounded like a commitment
  • It keeps the meeting and the moment it came from
  • Nobody is being measured against it yet
  • It becomes a task the moment you decide to track it
A task Lives on a board
  • It has an owner, a column and usually a date
  • It sits on the board of the hub that meeting belonged to
  • It still carries the source meeting, so context is one click away
  • You created it, or asked the assistant to

Address

A task needs a place, not a folder called misc

Whisperer works out which piece of work the conversation belonged to before it files anything. If that hub has no board chosen yet, applying a suggestion declines honestly rather than dropping the card into whichever project came first.

  1. MeetingA transcript and a map, with the action items separated out.
  2. HubThe client, project, hire or release the conversation was about.
  3. Your decisionYou apply the suggestion — or leave it as a promise.
  4. BoardA card with an owner, a due date and its source meeting.

Limits

What this will not do for you

Limit one It will not invent an owner or a date

If the call never named who or when, the item stays open. An assistant that fills those blanks confidently is guessing, and a wrong owner costs more than a missing one.

Limit two One recording at a time, not an archive migration

A finished recording can be uploaded: the Meetings section takes one file up to 25 MB — mp3, m4a, wav, ogg, flac, aac, plus mp4 and webm, from which the audio track is used. What is missing is bulk upload of a whole archive; and it spends the same minutes a live call does.

Questions

What people ask first

Do tasks appear automatically after every call?

No. Suggestions appear; you apply the ones worth tracking. This is deliberate — automatic ticket creation is the fastest way to make a board nobody trusts.

Can the assistant create the task for me?

Yes. Leo can create a card, move it between columns and set a date when you ask in plain language. What it cannot do is delete anything without your confirmation.

Where do the cards go?

Onto the board of the hub the meeting belongs to. Until a hub has a board, applying a suggestion declines rather than filing the card somewhere arbitrary.

Can I use my own tracker instead?

Yes — copy the items out of the map, or export the session. There is nothing in the design that requires the built-in board, and Notion, Slack, HubSpot and Zapier connect from your account if you want the handoff automated.

What happens to items nobody picked up?

They stay with the meeting as promises and open questions. The hub page shows what is still unclosed, which is a more useful view than a board of things that were never really agreed.

Watch one meeting turn into work

Take the standup that usually ends with nobody writing anything down, and see how much of it was an actual commitment. Usually less than it felt like at the time.