SHYENA
AI Evaluation for Cognigy Conversational Agents

Automated AI Evaluation. Trusted Every Time.

Shyena is built to evaluate any AI system before it ships — live today for conversational and voice AI. It runs real, agent-driven conversations against your live bot, judges the quality of every turn with LLM-based evaluation and deterministic checks, and makes it structurally impossible for a broken conversation to report a green pass.

Built for Cognigy customers

Already running Cognigy? This is the evaluation layer built for you.

Shyena isn't a generic testing tool with a Cognigy integration bolted on — Cognigy is our live, flagship platform. Agentic personas, real conversation execution over the same channel your customers use, and the execution-integrity gate all run against your actual Cognigy agent today.

Cognigylive platform, today31 / 117metrics, default / full

Automated

End-to-end automated AI evaluation at scale.

Accurate

Precise, consistent and unbiased results.

Trusted

Reliable insights. Confident decisions.

The platform

Three engines. One release gate.

Evaluation — live today

Shyena tests and evaluates Cognigy-built conversational and voice AI agents — driving real chat and voice sessions against your live Cognigy bot and judging every turn.

CognigyMore platforms next

Security — live today, via Ziran

LangChainCrewAIBedrockMCPBrowser & HTTPS agents

Intelligence — CIS

CIS is Shyena's proprietary conversation intelligence system — it understands your agent's business rules and logic on its own and generates thousands of test conversations from that understanding, so coverage grows with your agent instead of your team's authoring time.

Proprietary

The problem

Conversational agents don't fail like normal software.

01

Non-determinism breaks your test signal

LLM-driven agents answer differently every run. The same scenario passes on Tuesday and fails on Wednesday, so teams stop trusting the suite and start ignoring red builds.

02

Manual QA can't cover open-ended dialogue

A realistic agent has thousands of viable conversation paths. Reviewing transcripts by hand covers a handful per release, and the ones you skip are the ones that reach customers.

03

Test tools assume scripted click-paths

Traditional automation asserts that a selector exists. It cannot judge whether the agent handled an angry renewal request correctly, stayed in policy, or actually resolved the issue.

31

metrics evaluated on every case, by default

117

metrics in the full catalog, including custom ones you define

0

false green passes — the gate structurally prevents it

Default depth for a standard case; accessibility-gated runs evaluate more.

Where Shyena fits

Not a prompt tester. Not an observability tool.

Tools like Promptfoo and DeepEval test prompts and outputs against datasets you define. Arize Phoenix observes traces after the fact. Ragas scores whatever dataset you hand it. None of them drives a live conversation through your actual customer-facing channel. Shyena is the only one that executes a full live conversation, judges it on semantics and orchestration as well as wording, and refuses to let a broken run report a pass.

 PromptfooArize PhoenixDeepEvalRagasShyena
What it testsPrompts, models and RAG pipelines via direct API calls; a separate module red-teams for jailbreaksTraces already captured from an instrumented appSingle-turn outputs, multi-turn conversations, and agent tracesRAG, workflow and agent outputs you provide as a datasetA full live conversation, turn by turn
Execution surfaceDirect API/HTTP calls — not your live customer-facing channelDataset replay or post-hoc production traces — not your live customer-facing channelA callback to your app's code, or post-hoc traces — not your live customer-facing channelNone — scores the dataset you give itReal browser or voice session — the same surface your customers use
Test authoringDeclarative config test cases with assertions; red-team prompts are generated, not authoredGroup captured traces into datasets, rerun through app versionsFixed input/output datasets, or a goal + persona + expected-outcome golden the simulator role-plays fromQuestion / context / answer / ground-truth dataset rowsGoal + persona + playbook — the agent improvises like a real customer
Handles conversation non-determinismRed-team strategies adapt and backtrack to find a jailbreak — not general goal completionFixed dataset inputs per run, or observes production after the factIts conversation simulator adapts toward a stated goal — but via a callback, not your live channelN/A — scores conversations that already happenedBuilt around it — the same goal reaches the outcome via a different valid path every run
LLM-judged + deterministic scoring, combinedBoth exist as assertion types, evaluated per-assertion — not fused into one gated verdictBoth exist as evaluator types, but as separate experiments — not fused into one gated verdictBoth exist as metric types — G-Eval plus deterministic scorers like tool correctness — not fused into one gated verdictBoth exist as metric types, computed independently per rowBoth, natively combined in one verdict
Execution-integrity gatingNo concept of thisNo concept of thisNo concept of thisNo concept of thisYes — a broken or incomplete run is capped at FAIL before quality is even scored
Semantic / state-transition validity modelNoNoNo named equivalentNoYes — six-construct verdict validates state transitions, not just wording
Orchestrator-level decision & dispatch analysisNoPartial — manual trace inspectionPartial — tool-correctness and agent-trajectory metrics, not a weighted per-turn modelNoYes — per-turn analysis of whether the agent dispatched correctly, not just replied well
Accessibility scanningNoNoNoNoYes — gated a11y scans on smoke and pre-production runs
Voice + chat channel coverageText/API onlyDepends on instrumentationText/API onlyN/A — not a channel-execution toolBoth — the same execution engine drives voice and chat
Full audit trail for compliance reviewEval run logs and CI historyYes — that's its core purposeTest run reports; deeper history via its hosted platform integrationWhatever you log around the scoring run yourselfYes — every prompt, judge call, assertion and retry recorded and exportable
Scale architecture (retry, backpressure, DLQ)Caching and concurrency controls; CI-orientedN/A — ingests traces, doesn't execute runsPytest-native parallelization; CI-orientedN/A — a single scoring pass over your datasetBuilt in, tuned to not overwhelm the agent under test

They're not mutually exclusive — teams often unit-test prompts with tools like these before Shyena runs the full conversation as the release gate none of them cover.

How it works

One run. 31 metrics. A verdict you can defend.

Every regression run follows the same four stages, and each stage produces evidence the next one is allowed to trust — from a single persona definition to a case scored against 31 metrics by default, spanning LLM-judged quality, deterministic assertions, semantic state-transition validity, and orchestrator-level decision analysis.

01

Define agentic test personas

Describe a goal, a persona and a playbook — not brittle scripted steps. Shyena improvises like a real customer would.

02

Execute real conversations

A real browser or API session drives your live agent end to end, across chat and voice, with retries and backpressure built in.

03

Evaluate against 31 metrics

LLM-as-judge scoring, deterministic assertions, six-construct semantic assurance, and orchestrator-level decision analysis — 31 metrics evaluated by default, from your quality pillars down to whether the agent dispatched the right tool call.

04

Gated, trustworthy verdicts

If the execution didn't complete, the verdict is capped at FAIL regardless of score. No false green passes, ever.

Platform

Everything a release gate for conversational AI needs.

Built first for conversational and voice AI. RAG evaluation is next — the judge model already includes five RAG-specific quality dimensions.

Agentic Test Personas

Model the customers who actually call you: confused, impatient, multilingual, off-script. Each persona pursues a goal instead of replaying a transcript.

Real Conversation Execution

Runs against your live conversational AI platform through the same surface your customers use — no mocks, no simulated backends.

LLM-as-Judge Metrics

Turn-level scoring for grounding, resolution, tone, policy adherence and escalation quality, with the reasoning stored alongside each score.

Deterministic Assertions

Hard checks for the things that must never be fuzzy: refund amounts, disclosure text, redaction, handoff targets and latency budgets.

Semantic Assurance

Six-construct state-transition validity model — intent integrity, context memory, dialogue state correctness, business compliance, tool decisions, and recovery — with a causal root-cause taxonomy behind every violation.

Orchestrator Quality

Scores the agent's internal decisions, not just its replies: correct tool/route dispatch, missed invocations, and decision oscillation across a conversation — weighted and traceable to the exact turn.

Execution-Integrity Gate

Incomplete, timed-out or errored runs can never be scored into a pass. Integrity is evaluated before quality, not after.

Automated Bug Report Generation

Every FAIL gets an LLM-generated root-cause report — a 5-Whys chain, severity, and duplicate detection — rendered as Jira-ready markdown, automatically, no manual write-up required.

Custom Metrics

Extend the 31-metric default catalog with your own — subclass a documented SDK, register it, and it runs alongside the built-ins with the same exception isolation and latency tracking.

Full Audit Trail

Every prompt, judge call, assertion and retry is recorded and replayable, so a verdict can be defended in a release review or an audit.

A broken conversation should never look like a passing one.

Most tools score whatever transcript they collected. If the agent stalled at turn 17, they grade the first sixteen turns and call it green. Shyena evaluates execution integrity first.

Shyena FAIL

turn 17 · session terminated before goal resolution
quality score 0.81 · integrity check FAILED
verdict capped → FAIL (execution incomplete)

Scored honestly and capped. The team sees exactly which turn broke, with the full judge reasoning attached.

A lesser tool PASS

16 turns collected · no assertion errors raised
average score 0.81 → threshold 0.75
verdict → PASS

A false green: nothing crashed loudly, so the run reports healthy — and the regression reaches production.

Automated

No manual effort, continuous evaluation.

Measurable

Quantitative metrics that matter.

Reliable

Consistent, repeatable and unbiased.

Explainable

Transparent results with clear evidence.

Actionable

Insights that drive real improvement.

Continuous

Always learning, always improving.

Trust

Nothing here asks you to take our word for it.

We're early — no wall of customer logos, no analyst quadrant, on purpose: we'd rather get the evaluation model right first. Here's what you can actually check yourself today, not what we claim.

  • We use an independent, open-source red-teaming engine

    Our red-teaming service runs on Ziran — an independent open-source project we have no role in developing. Read the actual detection logic on GitHub, not a description of it. github.com/taoq-ai/ziran

  • The metric catalog is documented, not just claimed

    31 metrics run by default, 117 in the full catalog — see exactly what each one scores in the docs.

  • The gate is checkable on your very first run

    Bring one real scenario to a free pilot. If a run breaks mid-conversation, watch it get capped at FAIL yourself — nothing to take on faith.

A team collaborating around a laptopColleagues talking in an office hallwayTwo colleagues in a professional setting

Resources

Field notes on testing conversational AI

See it evaluate your own agent

Bring one real scenario. We'll run it against your live conversational AI agent and walk through every judged turn with you.