Introduction

This is where the article content will be displayed. The rich text field from the CMS collection will be bound here to show the full article body with formatted text, images, and other rich content.

Running a test

The Test button is accessible in the top right corner of the interface. Clicking it opens a panel on the right side of the screen.

You can fill in the test feedback data: the conversation content (transcript, email, ticket…), as well as the source, agent, tags, and custom properties. These fields let you simulate realistic conditions to test the logic of your Conditions and filters.

Reading the results

Results appear in the right panel, step by step, following the order of your flow:

  • For each Criterion: the AI's response, the score assigned, and the associated explanation
  • For each Condition: the evaluation result and the decision made (pass or stop)
  • For each Quality Monitoring: the calculated composite score
  • For each Alert: send confirmation and recipient count

This step-by-step reading lets you quickly identify if a prompt is too vague, if a Condition is poorly calibrated, or if the overall logic produces the expected results.

Iterate before activating

It's recommended to test your flow on several examples before activating it — including cases representative of what you want to detect, and cases that should not trigger your logic. A well-tested flow is one that produces reliable results from the start.

Documentation /
Grid Studio
Category

Testing your flow

Before activating a flow, Grid Studio lets you test it on a sample conversation to verify that your logic works as intended.

Book your personalized demo

See how Gravite transforms your quality management in real time.

Request a demo
Live walkthrough of the platform
Tailored to your use cases
No commitment