Docs Examples
From a meeting to the actions
The recording of a meeting becomes a transcript, the actions are found, and each person gets theirs by email.
- The meeting endsYour meeting app sends the recording to the link of the transcription service.
- The devices transcribe it in partsThe audio is split, the parts are transcribed at the same time, and they are joined without losing or repeating a word.
- The transcript comes backWith the time of each line, to your app or to the next service.
- A function of yours finds the actionsWritten by your team, in your language, it reads the transcript and pulls out each action, with owner and deadline.
- Each person gets their actionThe same function sends the email through your company's email provider.
A meeting ends, and a few minutes later each person has in their inbox what they took on. The heavy part, transcribing, runs on the company’s idle devices.
What each part uses
- The transcription service, the same one behind Conversation Intelligence, called by the meeting app.
- A function written by your team, in your language, published with the Claro CLI. It reads the transcript, finds the actions and calls your email provider. Functions only reach the addresses you declare. See Distributed functions.
On the screen, even more
Whoever sends the recording through the service page also gets who said what, a summary per person, and the decisions, separated from the conversation.
Where the savings are
Transcribing hours of audio is heavy work. Done on devices that were idle, it costs no new server and no per-minute fee to an outside service, and the recording never leaves the company.