Meridian Voice
Voice and virtual agent
Capture against versioned scripts, review transcripts and prepare a human handover.
Reimea Meridian
Give every request a clearer next step.
Connect voice capture, service operations and source-backed suggestions. Let people inspect the draft and decide what happens next.
The complete Meridian range
Seven Meridian product areas.
Distinct jobs. A shared design.
Voice, Service Desk, Knowledge, Intelligence, Guardian and Wellness are shown individually below. Reimea Exchange is the eighth member of the wider Reimea family and remains a separate product.
Meridian Listen
Understanding human conversations
Follow conversations between people, surface expressed concerns and questions, and show the words behind each signal for human review.
Meridian Service Desk
Requests, assignment and inventory
Manage requests, service targets and inventory, with AI suggestions reviewed before use.
Meridian Knowledge
Governed sources and retrieval
Manage source ownership, review and publication in Knowledge Studio. Helpdesk articles follow a separate workflow.
Meridian Intelligence
Reporting and operational insight
Explore operational data, quality checks, aggregates, forecasts and monitors, with assumptions visible.
Meridian Guardian
Supervision and quality review
Explore service oversight and human review. Demonstrator risk signals do not establish validated autonomous clinical decisions.
Meridian Wellness
Clinical demonstrator
Explore bounded wellbeing and patient-facing concepts using synthetic data. This is not a validated diagnostic or treatment service.
And Reimea Exchange
The eighth Reimea product: a separate source-attributed care-record design, currently a synthetic demonstrator.
Explore Reimea ExchangeA service request, from first words to reviewed handover.
Start with a narrow business-support workflow: an IT issue reported by phone. Review the capture, inspect the suggested source, confirm the owner and record the human decision.
The first pilot should measure what changes: handling time, completeness, correction rate and the work reviewers must do.
Read the illustrated workflow exampleChoose the scope before the edition.
| Edition | Focus |
|---|---|
| Voice | Voice, governance, reporting and monitoring |
| Service Desk | Helpdesk, knowledge and reports |
| Intelligence | Informatics, knowledge, reporting and planning |
| Clinical | Voice capabilities plus clinical demonstrators |
| Enterprise | Defined modules, configured to the agreed scope |
An edition name is not clinical approval. Clinical and patient-facing modules remain demonstrators.
What deployment needs.
A customer-specific environment
The design supports a separate Azure deployment per customer and environment, with Entra identity configuration and customer-owned operational responsibilities.
Agree data flows, model-task scope, keys, monitoring, retention and recovery before use. Validate role and route coverage in the deployed environment.
A shared release decision
The supplied review is based on source and documentation. It does not establish a completed Azure deployment, an independent security assessment or a production service level.
Read the dated evidence summaryKnowledge Control has its own place.
See how the source lifecycle works: ownership, staging, approval, deprecation, versions, dates and module-scoped retrieval. This is the shared management capability around knowledge, listed separately from the retrieval product.