Verba

Recording review

See the conversation. Inspect the evidence.

Upload supported media or submit it through the API. Playback, speaker timelines and timestamped dialogue keep the source next to the review.

Speaking turns across the session, by speaker.

Meeting record, participation split and key topics.

Timestamped dialogue, attributed and reviewable.

• Audio-based diarization

  Speakers and speaking turns are detected from mixed audio — no participant list, no separate channel per speaker, no enrolled voice profiles. That is what makes it work on in-person recordings as well as online ones.

• Editable identity and text

  Match detected speakers to company users or external contacts, and correct recognised text or a speaker assignment before the conversation is analysed again.

• Playback and participation

  Review the timestamped dialogue with the recording open beside it. Speaking timelines show how the conversation was actually distributed.

Business-specific analysis

Your methodology. Your business context.

Configure what the system examines, which knowledge it draws on, and how each type of interaction is assessed.

• Several outputs, one conversation

  A single meeting can yield summaries, key topics, actions, recommendations and specialised assessments in the same workflow. Your own instructions — prompts, in the product’s language — decide what is examined and how the findings are presented.

• Reusable company knowledge

  Approved messages, product information and evaluation guidance are maintained centrally and reused through variables. Meeting categories tie each type of interaction to the analyses and scorecards that belong to it.

• Current context from connected systems

  API-backed variables fetch selected information at the moment an analysis is prepared, with controls for authentication, testing, which part of the response to use, and what to do when the information is unavailable. Company secrets keep credentials out of the analysis instructions themselves.

• Model choice and reanalysis

  Models are selected separately for the initial analysis, for additional review and for arbitration. Regenerate an analysis from an existing or corrected transcript, or repeat the whole recording-processing workflow when that is what the case needs.

Company-wide default analysis models, and the supported settings for search-by-meaning models, are configured through the API. These company AI defaults are API-only at present.

Additional quality controls

Review the interpretation. Resolve the disagreement.

Precision review and arbitration add configurable checks, so the most recent model opinion is never the automatic final answer.

• Precision mode: a focused second review

  An optional review checks the first assessment against the transcript and the same company standards. It proposes specific corrections rather than replacing the whole result, and with arbitration disabled those validated corrections apply directly.

• Arbiter mode: resolving a disputed score

  When Precision proposes a different score, the optional arbiter settles it. Candidates are presented without identifying which evaluator produced them and in randomised order, which is what keeps the decision away from model preference and answer-position preference.

• Validation

  Checks completeness, permitted structure and required supporting material.

• Precision

  Checks the initial interpretation against the transcript and the standards.

• Arbitration

  Resolves a proposed score change with one further assessment.

Each evaluation stage can use a separately selected model, and review depth is configured per workflow: a standard assessment where that is appropriate, more review where it is not. The business decision stays with the organisation.

Platform and operations

See the work. Control the access. Connect the result.

Activity and resource use in one workspace, corporate identity behind the permissions, and supported interfaces carrying finished assessments onward.

Dashboard and operations

• A configurable workspace

  Adjust which widgets appear and in what order — recent meetings, live sessions, upcoming events, usage and recent searches in one view.

• Processing status and history

  Task status, recorded resource use and errors distinguish finished work from work that needs attention.

• Usage and capacity

  Credit use, storage consumption, processing allowances and subscription limits, so planning and administration have something to plan against.

• Automated housekeeping

  Scheduled tasks clear expired sessions and abandoned uploads, refresh operational information, and resume deferred work that has become eligible again.

• Licence management

  Deployment-wide licence refresh and validation keep operation continuous under the configured licence.

Corporate identity, policy-controlled access

Keep people and teams aligned with the directory, then apply the permissions their responsibilities actually call for.

1. 01

   Corporate directory

   People and team membership

2. 02

   Platform accounts

   Synchronised users and groups

3. 03

   Access policies

   Direct, inherited and temporary

4. 04

   Protected operations

   Permissions enforced in the backend

• LDAP and corporate directories

  Verba connects over LDAP to compatible directories, Microsoft Active Directory among them, so people sign in with the corporate credentials they already have. Synchronisation creates and updates accounts and keeps group names and membership aligned.

• Controlled directory coverage

  Configurable locations, filters, group exclusions and field mappings decide which records are included. An LDAP-managed account that leaves the configured scope is removed on the next synchronisation. Connection tests, manual runs and scheduled updates surface results and errors.

Reusable policies, understandable permissions

Company and team scope

Assign reusable permission sets to individuals and to teams, synchronised groups included.

Direct and inherited access

Combine a personal assignment with the permissions that arrive through group membership.

Explicit restrictions

Resolve overlapping allow and deny rules through defined priorities.

Temporary permissions

Start and end dates for access that is only meant to last a while.

Effective access detail

See where a permission came from and whether it is currently active.

APIs and event automation

Supported APIs and event notifications connect an assessment to the applications that manage review, reporting and follow-up.

• Application integration through APIs

  Supported meeting, document, search, configuration and administration operations give an external application a controlled way to ask for information or take an action — so Verba is not an isolated workspace people have to visit.

• Structured results for downstream use

  Named score fields and versioned export definitions are a stable basis for reporting and customer-specific integration. A connected system uses the result rather than parsing numbers out of generated prose.

• Event delivery and recovery

  Supported meeting events, analysis completion among them, notify a connected system and trigger its next action. Delivery attempts and failures are recorded, and eligible notifications are retried on a schedule when an endpoint is unavailable.

• Protected outbound connections

  Company secrets provide reusable integration credentials without putting passwords or tokens inside analysis instructions. API-backed variables use the same mechanism to fetch external context when an assessment is prepared.