Avoma

The base product is the model, which distinguishes this from vendors that layer AI onto working software. Strip transcription, summarisation, topic detection and scoring and what remains is a video recorder and a calendar tool, not a diminished version of the same product.

The entry tier is named for the assistant and consists almost entirely of model output: transcription across a claimed seventy plus languages, generated summary notes, extracted action items and generated follow up emails. That is a genuine removal test failure at the level a buyer actually purchases. Held below the top band by two things.

The platform has accreted conventional components, with a scheduler, round robin routing and a lead router that are ordinary software sold in the same subscription. And the differentiating intelligence, meaning call scoring, deal risk and forecasting, is sold as separately priced add ons, which is the vendor itself demonstrating those layers detach from the base. Ask which capabilities remain if the add on modules lapse, and what the base tier delivers without them.

The system writes into the customer record system on its own and the boundary is not published. Two way field updates from call content are a named capability of the deal intelligence module, meaning the platform reads what was said in a meeting and writes values into opportunity and contact records that forecasting and reporting then depend on. That is autonomous action on the system of record rather than a suggestion surfaced for a human.

Nothing published describes which fields it may write, whether it overwrites values a person entered, whether any review step exists before a write, or what an administrator can constrain by field or by role. The base plans are safer by construction, since they log meetings one way rather than updating fields, so the exposure arrives with the add on rather than with the platform. Generated follow up emails are drafted for a human to send. Ask which fields the two way update can write, whether it overwrites human entered values, and what approval or rollback exists.

Model output drives decisions about people and nothing about the models is published. No provider, family or version is named, no model card exists, and no accuracy figure accompanies any of the three claims that matter most. Transcription is offered across a claimed seventy plus languages with no word error rate published for any of them, which is the foundational measurement for a product whose every downstream feature reads the transcript.

Call scoring against named methodologies produces a number a manager uses to coach an individual, with no published accuracy or inter rater agreement against human scoring. Deal risk scoring drives forecast decisions with no published validation against realised outcomes. Independent review coverage separately reports recurring transcription and recording reliability complaints, which is user reported evidence in the space where vendor measurement is absent. Ask for word error rate by language, scoring agreement against human reviewers, and deal risk accuracy against closed outcomes.

Four quantified outcome claims on the homepage, none carrying a population, a period or a method. The vendor states that customers save more than four hours a week, schedule twice as many qualified meetings, increase win rates by forty percent through automated scoring and coaching, and increase quota attainment by thirty percent through deal risk alerts and win loss analysis.

Those are large numbers presented without a baseline, a cohort or a measurement window, and the two revenue claims in particular assert causation from a coaching tool to quota performance with nothing published behind them. The genuine evidence runs the other way and comes from outside: a review base of roughly thirteen hundred and sixty ratings at four point six out of five is substantial third party corroboration of satisfaction, and the same corpus surfaces a consistent reliability complaint about the recording bot failing to join or capture meetings, which is an operational finding the vendor does not acknowledge. Ask how the win rate and quota attainment figures were measured, across what population and period, and what the recording success rate is.

The platform sends in two narrow ways and neither is described in compliance terms. Generated follow up emails go to meeting participants after a call, which is correspondence within an established conversation rather than cold outreach, and scheduling links go to invitees. A lead router add on distributes inbound leads to representatives, which is internal assignment rather than contact.

So the volume and the consent exposure are both small by comparison with a campaign product, and the axis applies narrowly rather than being penalised. What is unaddressed is the boundary: nothing published states whether an external participant who asks not to be contacted is suppressed from generated follow ups, whether the scheduler honours any preference state, or what governs repeated automated follow up after a meeting. Ask whether suppression or opt out state applies to generated follow up emails, and what limits repeated automated follow up to an external participant.

The instrument a privacy review needs is gated behind the top commercial tier, which is the finding here. Signed processing agreements, health information compliance and data retention policies are all described as top tier capabilities, so a customer on either lower plan records customer conversations without access to a signed agreement governing that processing.

For a product whose entire corpus is recorded conversations with named external participants, making the processing agreement a paid upgrade is a materially different posture from making it standard. Nothing else was established on this pass: no transfer mechanism, no subprocessor list, no stated retention period outside the gated policy capability, and no data protection officer.

What does exist is a clear role model in which viewers and collaborators access recordings without consuming seats, which means access to the corpus is broader than the licence count suggests and the access control question is correspondingly larger. Ask whether a processing agreement is available below the top tier, what retention applies by default, and who can access recordings under the free collaborator role.

Nothing is purchased or resold and the provenance question is entirely about what the vendor does with recorded conversations. There is no contact database, no intent feed and no third party corpus behind this product, so the sourcing questions this axis usually asks have nothing to attach to.

What accumulates instead is recorded audio, transcripts and derived scoring across every customer conversation a team holds, including the speech of external participants who are not the vendor's customers. Whether that material contributes to improving transcription, summarisation or scoring is the obvious commercial question for a speech product and nothing published answers it, in either direction.

No statement was located on training use, on whether transcripts inform models serving other customers, or on what consent basis would cover an external participant's voice being used that way. Ask whether recordings or transcripts train or tune any model, whether that behaviour can be disabled, and what basis covers external participants.

Integration runs through sanctioned mechanisms across two distinct estates. On the meeting side the recorder joins calls as a participant through the conferencing platforms own guest mechanisms rather than by intercepting streams, which is the sanctioned route for this category.

On the data side bidirectional synchronisation runs with six named customer record and support platforms through their own published integration surfaces, alongside dialer integrations and, at the middle tier and above, an interface and webhooks. Nothing resembling credential storage or unsanctioned capture appears anywhere. Two things hold it below the top band.

No stated conformance position against any specific platform's terms was located, which is what separates the bands on this axis. And the recorder's dependence on conferencing platforms is a real exposure the vendor does not address: independent review coverage reports recurring bot join and recording failures, which is a symptom of operating as a guest on infrastructure the vendor does not control, and nothing published describes what happens if a platform changes its guest policy. Ask what the fallback is when the recorder cannot join, and whether any named platform conformance commitments exist.

One of the more sensitive corpora in this index and no stewardship position was located. The platform holds recorded audio and transcripts of a customer's entire meeting history with its own customers and prospects, together with derived scoring about individual representatives that managers use for coaching, and generative features read across all of it.

Nothing published states whether that material trains or tunes models, which providers process it during generation, whether prompts and outputs are retained, or whether anything crosses a tenant boundary. Data retention policy is described as a capability of the top commercial tier rather than as a stated default, which means the answer to how long recordings persist depends on what the customer paid rather than on a published position.

No artificial intelligence governance document, evaluation record or independently audited management standard was located. Ask whether recordings or transcripts train any model, what the default retention is below the top tier, and which providers process generative requests.

The recording mechanism discloses itself by construction, and the consent apparatus around it is not described. A bot joins the meeting as a visible named participant, so every attendee including external customers can see that something is present and recording, which is a materially more honest arrangement than silent capture and is the reason this sits mid band rather than lower. What is absent is everything beyond that visibility.

Nothing published describes whether an announcement is made, whether consent is captured or recorded, or how the platform handles jurisdictions requiring every party to agree before a conversation is recorded, which is the live legal question for a product sold to teams calling customers across many territories. Generated follow up emails are sent under the meeting host's name after the call, and nothing states whether the recipient is told the summary and message were machine written. Ask what recording announcement or consent capture the platform provides, how it varies by jurisdiction, and whether generated follow ups are marked.

Bidirectional depth across an unusually wide set of customer record platforms for a vendor of this size. Two way integration is named with six systems spanning the major platforms plus mid market and support side alternatives, which is broader coverage than most conversation products manage and matters because it lets smaller buyers running less common systems get the same behaviour.

Meetings, recordings, transcripts and generated summaries log automatically to contact and deal records on every tier, with field level write back arriving through the deal intelligence add on. Conferencing platform coverage spans the major services, dialer integrations connect the calling side, and an interface with webhooks is available from the middle tier.

Held below the top band on gating and verification: interface access requires the middle tier so the entry plan is integration limited to prebuilt connectors, no developer documentation or rate limits were reached on this pass, and independent reviewers report intermittent synchronisation failures which is a reliability qualification on the depth rather than on its existence. Ask for the interface documentation and which integrations are available at the tier quoted.

Cloud only with no residency answer and an explicit boundary reported from outside. No hosting provider or region is named, no European or United Kingdom residency election is described, no tenancy model is stated, and no recovery objective is published.

Independent analysis states directly that the platform is not built for organisations requiring on premises deployment or compliance scope beyond health information handling, which is a clearer statement of the limit than the vendor makes and is useful precisely because it comes from a reviewer rather than a sales page.

The residency gap matters in proportion to the corpus, since recorded voice is personal data of external participants who never contracted with either party, and a European customer recording European counterparties needs to know where that audio is stored before deploying. Health information handling is available but gated to the top tier. Ask which regions recordings and transcripts are stored in, whether regional residency is available, and what the recovery objectives are.

Named enterprise controls exist and no certification or attestation was located on this pass. What is established is that single sign on through the standard federation protocols, health information compliance, team level access controls and signed processing agreements are all offered, which indicates a security programme capable of supporting regulated buyers. All of it sits at the top commercial tier, so those controls are a purchase decision rather than a baseline.

No trust centre, service organisation control report, international information security certification, penetration testing statement or vulnerability disclosure route was reached on the routes taken. This records what a buyer could establish before contacting sales rather than asserting that nothing is held, and a vendor offering health information compliance almost certainly holds an attestation behind a sales conversation.

The gating is the substantive finding either way: a customer at the entry tier records customer conversations without single sign on or a signed agreement. Ask which certifications are held with audit periods and auditors, and whether single sign on is available below the top tier.

The full ladder is published, which independent reviewers single out as unusual in this category, and the headline understates the working cost by roughly four times. Published: three base tiers per recorder seat in both billing cycles, at nineteen and twenty nine dollars, twenty nine and thirty nine, and thirty nine annually only, with seat caps of twenty five and one hundred and a ten seat minimum on the top tier.

Three add ons are published at per seat rates, covering coaching at twenty nine, deal intelligence at twenty nine and lead routing at nineteen, with a stated bundle discount on the first two. Viewers and collaborators are free and do not consume seats, which is a real and clearly stated accessibility choice. A fourteen day trial of the middle tier runs with every add on enabled and no payment card. Three things hold it below the top band.

The vendor leads with nineteen dollars while a working sales seat carrying both intelligence add ons lands near seventy seven, and the add ons are charged per seat rather than per team, so the gap widens linearly with headcount. Compliance capabilities including single sign on, health information handling and signed processing agreements are hard gated to the top tier regardless of team size, so a small regulated buyer pays enterprise rates for governance rather than features.

And the vendor's own competitor comparison blog states seat caps of twenty and seventy five and a twenty seat minimum, contradicting the caps of twenty five, one hundred and ten that six independent sources take from its pricing page. Ask which seat caps are current, and price the configuration you will actually run rather than the entry tier.

One post contract behaviour is disclosed and the rest is not. The vendor states that after a trial ends an account reverts to a viewer role which retains access to past recordings and notes but cannot record new meetings, which is a clear and unusually specific description of what happens when payment stops, and it tells a buyer that historical material is not immediately withdrawn.

Beyond that the surface is silent: no statement of export scope or format, nothing on whether recordings, transcripts, scoring history and playlists leave in bulk, no deletion timeline after termination, and no notice or renewal terms. Retention policy is a top tier capability rather than a published default, so a departing customer at a lower tier cannot establish from the public record how long their material persists or when it is destroyed.

The asset is substantial, being years of recorded customer conversations that many buyers are separately obliged to retain or to delete. Ask what exports and in what format, whether recordings and transcripts leave in bulk, and what the deletion timeline is at each tier.

Sending is incidental to the product and none of it is described. Generated follow up emails after meetings and scheduling invitations are the only outbound traffic, both directed at people already in a conversation with the sender, so there is no campaign infrastructure, no pooled sending estate and no shared reputation for the vendor to manage.

Nothing published states whether that mail leaves from the user's own connected mailbox or from vendor infrastructure, who configures authentication records, or what happens to bounces on a scheduling invitation. The distinction matters mildly here because follow up volume scales with meeting volume rather than with campaign size, so the risk profile is low, but a buyer whose scheduling links fail to arrive has no published guidance on why. Ask which domain sends follow ups and scheduling invitations, and who configures authentication.

The served segment is stated numerically rather than by adjective, which is rare and genuinely useful. Seat caps and minimums define each tier explicitly, at twenty five seats for the entry plan, one hundred for the middle plan and a ten seat floor for the top plan, so a buyer knows immediately which tier they belong in and when they will be forced to move.

The positioning is equally direct: independent reviewers describe the platform as the consolidated alternative to running four separate point contracts, aimed at smaller and mid market revenue teams rather than at large enterprises, and the review base of roughly thirteen hundred and sixty ratings at four point six out of five supports genuine adoption in that segment. Transcription across a claimed seventy plus languages supports international use. Two limits keep it below the top band.

The compliance gating means a regulated buyer of any size is pushed to the top tier, so the stated segment ladder and the purchasable ladder diverge for that group. And independent analysis states plainly that the platform is not built for on premises deployment or for compliance scope beyond health information, which the vendor does not say itself. Ask what the largest reference deployment is, and what the options are for a small regulated team.