How it works
Draft, confirm, execute — with an emotion layer in the middle
Five steps take a raw transcript to a ticket in your sprint. Step 02 is what makes Prosody different: the follow-up work is drafted against how the conversation actually felt, not just what was said.
- 01
Import the transcript
Export a meeting transcript from Zoom or Microsoft Teams and upload the file. There is no bot to add to your calls and nothing to install — Prosody works entirely from the transcript you already have.
The file is parsed into clean, timestamped speaker segments: who spoke, when, and for how long. That structure is what everything downstream reads from.
- 02
Score the emotional tone
A RoBERTa model fine-tuned on the EmoBank corpus scores every line on three axes — Valence, Arousal and Dominance. The scores roll up into a mood timeline for the whole meeting.
Where negative valence and high arousal line up, Prosody marks a tense moment. Those stretches are usually where a decision started to slip, and they are what let the drafting step weigh urgency instead of guessing at it.
- 03
Claude drafts the work
Claude reads the transcript and the emotion scores together and drafts action items. Each draft carries a suggested assignee, an AI confidence score, a priority, and a full ticket: description, issue type, story-point estimate, due date and labels.
Transcript content is only ever sent to the Anthropic Claude API, and only for this step. It is never sold and never used to train models.
- 04
A human confirms
Every draft is shown in full — nothing hidden behind a summary. You accept it as-is, rewrite the description, change the assignee, adjust the estimate, or reject it outright.
Confirming means mapping Claude's suggested name to a real account in your Jira or ClickUp workspace. Nothing leaves Prosody until a person has done that, so a ticket never lands on the wrong person.
- 05
Prosody executes
On confirm, Prosody creates the real issue in your Jira or ClickUp and drops it into the right sprint under the right epic, carrying every confirmed field across from the draft.
Creation runs asynchronously, with retries and a per-tenant circuit breaker, so one integration outage never stalls another company's work. Every confirm, edit and reject is recorded and feeds the prediction-accuracy metric on your analytics dashboard.