Jiminny

The product is model output end to end and the removal test fails cleanly. Transcription across more than sixty languages, automatic notes and summaries, scoring against coaching frameworks, a question answering interface across calls and deals, and automatic population of customer record fields from conversation content are all model dependent, and stripping them leaves a call recorder with a playlist feature. That is not a diminished version of the same product.

The company has operated this way since 2016, so this is a long standing speech product rather than a recent repositioning. Held below the top band because the transcription layer that everything rests on is licensed from a third party engine rather than built, so the vendor's own modelling contribution sits in the scoring and coaching layer above it, and because the coaching workflow, playlists, snippets and manager tooling around the intelligence are conventional software that carries real weight in what buyers describe choosing it for. Ask which capabilities are the vendor's own models rather than the licensed engine, and what remains if the speech provider is unavailable.

The platform writes into the system of record on its own and no boundary is published. Automatic population of customer record fields, tasks and events from conversation content means the product reads what was said on a call and creates or changes records that pipeline reporting and forecasting then depend on, without a person entering them.

Nothing published describes which fields it may write, whether it overwrites values a person entered, whether any approval step precedes a write, or what an administrator can constrain by field or role. Separately the silent call attendance capability is an autonomy question of a different kind, since it is a human action rather than a machine one but is equally unbounded in what the public record describes: nothing states who may use it, whether its use is logged, or whether the representative being coached is told. Ask which fields automatic record filling can write and whether it overwrites human entries, and whether silent attendance is logged and visible to the representative.

The speech engine is named, which almost nothing in this category does. Independent coverage identifies a specific third party speech to text provider behind transcription, supporting more than sixty languages, and the provider publishes its own account of the relationship, so the disclosure is corroborated from both sides rather than resting on a vendor claim.

That matters more here than a generic model statement would, because transcription is the foundation every other feature reads from, and knowing which engine produces it lets a buyer evaluate that engine's published accuracy independently and ask where audio travels. Two gaps hold it below the top band.

No provider, family or version is named for the layer above transcription, meaning the scoring, the question answering interface and the record filling, which are the features that generate decisions rather than text. And no accuracy figure is published by the vendor for transcription in any language, for call scoring against human reviewers, or for the field values written back into the customer record. Ask which models power scoring and the question answering interface, and for word error rate by language.

Consistent independent placement and no measured outcome from either side. Reviewers converge on a clear qualitative verdict, describing a strong manager experience, effective coaching workflows and good value for the segment, and one directory places the product ninth in its category ranking. Contemporaneous press records roughly sixteen and a half million dollars raised, which evidences the company rather than the product.

What is absent is measurement of the thing being sold: no published study shows ramp time reduction, win rate improvement or quota attainment across a stated customer population over a stated period, and no accuracy figure is offered for the call scoring that managers act on when coaching individuals.

The same review corpus records a specific operational complaint, that data presentation lacks flexibility for tailoring reports to particular measures, which is a usability finding the vendor does not acknowledge. Ask for ramp or win rate improvement measured across a stated cohort and period, and for scoring agreement against human reviewers.

The platform sends internally rather than to prospects, which narrows this axis considerably. Notifications and nudges reach representatives and managers through messaging and email inside the customer's own organisation, and playlists and snippets circulate for training. There is no sequencer, no dialer campaign and no outbound delivery to external contacts, so consent capture and suppression have little to attach to and the axis applies in a limited form.

The one external touch is the call itself, where the obligations are recording and monitoring law rather than messaging law, and those are addressed on a different axis. What is unaddressed here is whether any of the internal notification traffic carries conversation content about external parties outside the platform's access controls, for instance a summary of a customer call pushed into a general messaging channel. Ask what conversation content the messaging notifications carry and which channels they can be directed to.

A European base and a data protection positioning that reviewers rely on, with none of the instruments reached on this pass. Independent coverage points European buyers with data protection requirements toward this vendor in preference to American alternatives and refers to its United Kingdom footing as part of the reason, which indicates the vendor makes a case somewhere.

What could not be established on the routes taken is any of the substance: no privacy policy contents, processing agreement, subprocessor list, transfer mechanism, retention period or data protection officer was located. The stakes are set by the corpus rather than by company size, since the platform holds recorded audio and transcripts of conversations with named external participants who never contracted with either party, and the speech engine is a third party processor handling that audio.

This grade records what a buyer could establish before contacting sales rather than asserting the documentation is absent. Ask for the processing agreement, the subprocessor list covering the speech engine, the retention period for recordings, and the residency position for European customer data.

No external corpus is licensed and the provenance question concerns recorded speech. Everything the platform holds originates in the customer's own conversations, so there is no purchased database, cooperative or third party feed to trace. The question that does apply is whether recordings and transcripts contribute to improving the scoring and coaching models the vendor sells, and nothing published answers it either way.

The question is sharpened rather than resolved by the licensed speech engine, since audio leaves the vendor's own systems to reach that provider, and nothing states what the provider may retain or whether customer audio contributes to its models. An external participant on a sales call has their voice recorded, transcribed by a third party and scored, without any published account of what happens to it afterward. Ask whether recordings or transcripts train or tune any model at the vendor or at the speech provider, and what retention applies at each.

Integration runs through sanctioned routes on both estates the product touches. Native applications are published for two major customer record platforms through their own marketplaces rather than built as private connectors, meeting and call recording operates through the conferencing platforms own participant mechanisms, and messaging notifications run through the standard application surface of the messaging platform.

Mobile applications are distributed through the two main application stores, which is a further sanctioned distribution path. Nothing resembling credential storage, stream interception or unsanctioned automation appears in anything located.

Held below the top band because no stated conformance position against any specific platform's terms was found, which is what separates the bands here, and because the silent call attendance capability operates inside conferencing platforms whose own policies on undisclosed participants are not addressed anywhere in what the vendor publishes. Ask whether any named platform conformance commitments exist contractually, and what conferencing platform policies govern the silent attendance feature.

A sensitive corpus, a named external processor and no stewardship position located. The platform holds recorded conversations between a customer's staff and its prospects, derived scoring about individual representatives that managers use in performance coaching, and a question answering interface that reads across all of it. Audio additionally passes to a third party speech provider.

Nothing published states whether that material trains or tunes models at either party, whether prompts and generated output are retained, what retention applies to recordings, or whether anything crosses a tenant boundary. No artificial intelligence governance document, evaluation record, red teaming artifact or independently audited management standard was located.

The employee dimension deserves its own question here, because scoring drives coaching conversations about individuals and nothing describes what recourse a representative has to a score they consider wrong. Ask whether recordings train any model at the vendor or the speech provider, what retention applies, and what recourse exists against an automated score.

A marketed capability places an undisclosed third party inside a live customer conversation. Independent review coverage describes managers joining calls invisibly to send private coaching messages to the representative while the conversation continues, with the other party unaware anyone else is present, and treats that concealment as the platform's principal differentiator rather than as an incidental feature.

Nothing published describes what the external participant is told, whether any announcement covers silent attendance as distinct from recording, or how the capability behaves in jurisdictions requiring every party to a conversation to consent. That is a different exposure from recording. A recorder can be disclosed once at the start and the person can decide whether to continue; a silent listener joining part way through cannot be consented to by someone who does not know they arrived.

This grade rests on the capability itself rather than on the vendor's own framing, which was not verified on this pass, and the architectural reading is what places it: the product is built so that a person on the call cannot know who is listening. Recording, transcription and scoring of that same conversation compound it. Ask what the external party is told about silent attendance, whether the capability can be disabled per jurisdiction or per account, and what consent the vendor considers necessary before it is used.

Functional coverage of the systems that matter, described by reviewers as narrow relative to the category. Native applications exist for two major customer record platforms with field and event write back, messaging notifications run into the standard team messaging platform, meeting and call recording spans the conferencing services, and mobile applications are published for both major phone platforms, which is more than several larger vendors in this index offer.

Against that, independent reviewers name a smaller ecosystem as one of the explicit trade offs against the enterprise alternatives, and no marketplace, partner directory or third party application catalogue was located. No developer documentation, interface reference, authentication model or rate limits were reached on this pass, so whether a programmable surface exists at all could not be established.

For a platform whose output is meant to reach other systems, the absence of a verifiable interface is the material gap. Ask whether an interface and webhooks are available, at which tier, and for the current integration list.

A European base that reviewers treat as a residency answer, without a published one. Independent coverage recommends the platform to European buyers partly on the strength of its United Kingdom footing, which implies a residency position exists, but no hosting provider, region, residency election, tenancy model or recovery objective was located on the routes taken this pass. Company domicile is not the same as data location and should not be read as one.

The gap matters because of what is stored: recorded voice and transcripts of identifiable external participants, plus a third party speech provider in the processing path whose own location is equally unstated, so a European buyer cannot establish from the public record where either the recordings or the transcription workload sit. Ask which regions recordings and transcripts are stored in, where the speech provider processes audio, whether European residency is available, and what the recovery objectives are.

No certification, attestation or trust surface was located on the routes taken this pass. No trust centre, service organisation control report, international information security certification, penetration testing statement, vulnerability disclosure route or enumerated control page was reached.

This records what a buyer could establish before contacting sales rather than asserting nothing is held, and a vendor selling into European mid market revenue teams with a data protection positioning very likely holds documentation behind a sales conversation.

The corpus makes the question weightier than the company's size would suggest, since the platform stores recorded customer conversations, routes audio to a third party processor, and offers a capability that places an undisclosed listener on live calls, all of which a security reviewer would want covered by an attestation with a defined scope. Ask which certifications or attestations are held, with audit periods and auditors, and whether a completed security questionnaire is available.

No figure appears on any vendor surface and the purchase path is a demo cycle. No pricing page, no rate, no tier names, no unit of pricing and no contract term is published, and independent reviewers state plainly that being forced into a demo just to obtain a ballpark number is a real problem for anyone building a budget.

What third parties report converges reasonably: roughly eighty three to eighty five dollars per recording seat per month on annual billing, around one hundred on monthly, a twelve month minimum commitment, and a one time setup fee whose amount nobody publishes. Multi year discounts of fifteen to twenty percent are reported.

Two structural points cut in the vendor's favour and are worth recording, because they are the reason reviewers call this the accessible option: there is no mandatory platform fee, which is the charge that makes the enterprise alternatives inaccessible to smaller teams, and a separate lower cost seat exists for people who view recordings without recording their own calls.

Sources disagree on that second seat, one reporting it at roughly forty two dollars monthly and another describing non recording seats as free, which is a material difference for a team where most people only watch. Ask for the recording seat rate, the viewing seat rate or confirmation that it is free, the setup fee, and the minimum term.

A twelve month minimum commitment is the only contractual term established and nothing describes leaving at the end of it. Independent reporting is consistent that most plans require a twelve month term with multi year commitments earning discounts, which tells a buyer how long they are locked in and nothing about what happens afterward.

No statement of export scope or format was located, nothing describes whether recordings, transcripts, scoring history, playlists and coaching records leave in bulk, and no deletion timeline, retention period or renewal notice term appears. The asset is substantial and awkward: years of recorded customer conversations that a buyer may be separately obliged to retain, alongside coaching and scoring history about named employees that carries employment implications of its own.

A one time setup fee at the start with no described exit path at the end makes the switching cost asymmetric. Ask what exports and in what format, whether recordings and transcripts leave in bulk, the deletion timeline after termination, and the renewal notice period.

The platform operates no campaign sending infrastructure. Email and messaging traffic consists of notifications and coaching nudges directed at the customer's own staff rather than at prospects, so there is no pooled sending estate, no shared reputation and none of the warmup, rotation, bounce or complaint machinery this axis normally examines.

Call recording rides on the conferencing platforms rather than on vendor operated telephony, so call completion is not the vendor's to manage either. What is knowable is thin because there is little to know. Nothing published states whether notification mail originates from vendor domains or the customer's own, or who configures authentication, which is a small question given the internal audience but the only one this axis can ask. Ask which domain sends platform notifications and who configures authentication for it.

The served segment is clear, consistently described from outside, and supported by a commercial structure built for it. Independent reviewers place the platform with small and mid market business to business teams with meeting and call heavy motions, one naming teams under twenty representatives specifically, and identify the absence of a mandatory platform fee as the thing that makes conversation intelligence reachable for buyers previously priced out of the category.

That is a segment position expressed through pricing architecture rather than through a marketing page. European coverage is a genuine part of it, with a London base and reviewers pointing European buyers with data protection requirements toward this vendor in preference to the American incumbents. Transcription across more than sixty languages supports international use, and mobile applications on both platforms support field teams.

Held below the top band by limits reviewers state and the vendor does not: revenue intelligence depth and pipeline forecasting are described as thinner than the enterprise alternatives, reporting flexibility is a recurring complaint, and the ecosystem is smaller. Ask what the largest reference deployment is, and what forecasting the platform does not do.