Conversation Insights for an enterprise organisation.

Vectorfy built a system that helps staff review calls for quality, compliance and customer safety. It had to work with the organisation's existing cloud provider and customer management system.

Engineering case study · Client and provider confidential

What the system enables

Read a call summary, see who said what, and check the transcript behind each finding. Reviewers can assess service quality and investigate privacy or safety concerns.

  1. Turn recordings into transcripts

    Detect speech and identify who spoke

  2. Find what needs attention

    Summaries, quality checks and possible compliance issues

  3. Review in the existing CRM

    Call insights beside the customer record

  4. Keep the service running

    Managed releases, monitoring and GPU scheduling

Illustrated product view. System view: call recordings pass through an audio pipeline and a fine-tuned transcription model, insights are prepared for review inside Dynamics 365, with GPU scheduling on Kubernetes and GitOps releases underneath. Example data.

A simplified view of the system. Illustrative diagram.

What made the project difficult

The cloud provider could not change

The challenge

The required provider was slow at running the AI model. Moving to another provider was not an option.

What we did

We changed the AI framework, model, prompts and tests to meet the business needs, then deployed within the approved cloud environment.

The provider later fixed a bug that made the model run faster. Our work was adapting and delivering the system within that environment.

Transcription needed a custom approach

The challenge

A leading speech model did not meet the requirements for these calls.

What we did

We fine-tuned a transcription model and built a custom audio pipeline. It detects speech, splits recordings into manageable sections and identifies who spoke when.

Identifying speakers is called diarization. It helps reviewers connect a statement or assessment to the right person.

The system had to fit the existing CRM

The challenge

The customer management system could not be replaced, and the integration lacked the documentation we needed.

What we did

We built the review interface inside the CRM and connected it to the call-processing services.

Staff could review transcripts and insights alongside the records they already worked with.

GPU processing costs needed control

The challenge

The custom speech models needed GPU computing, which could become expensive to run.

What we did

We used Kubernetes, the platform that runs and scales containerised services, to schedule GPU work and reduce processing costs. A separate GitOps setup, where deployment is driven from version-controlled configuration, manages releases.

The project included the application, speech processing and the infrastructure needed to run them.

What we delivered

A working call intelligence system in the approved cloud environment, integrated with the existing CRM. The delivery included custom speech processing and GPU scheduling to reduce running costs.

Client name and proprietary methods withheld.