Read meeting transcripts, notes, and scorecards, and submit outside calls for analysis
Connect Avoma and your meeting record becomes something the agent can read. Pull a meeting's processing state, its AI insights and speaker segments, notes for a date range, scorecard evaluations, and per-user engagement metrics. When a call was recorded somewhere else, the agent can submit it to Avoma for processing as an approved step.
16 tools: 15 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Avoma run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as create call. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Avoma — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.