Testzilla Console (Tessie)

Tessie is the AI assistant built into Testzilla, and the Console is its full-screen home in the app. Instead of clicking through forms, you describe what you want in plain language and Tessie does the work for you — across the whole platform and across the systems you have connected through Integrations.

Think of the Console as the no-code power surface: everything the API and MCP server can do, driven by conversation, scoped to your account.

Just want a first result?

The fastest path is to ask Tessie. From the Dashboard or Projects page, click Set up with Tessie / Ask Tessie and describe what you want to test. See the Quickstart for the no-code walkthrough.

What Tessie can do

Build your test setup from a sentence

Describe the agent you want to test and Tessie assembles the whole hierarchy for you — no forms:

• Creates a Project to group everything.
• Adds the right Channel for your agent and picks the connection type (phone, LLM Chat, Web Chat, or Web Voice).
• Writes the Tests — scenarios and pass/fail criteria — from your description.
• Runs them, and reports back the results.

“Test my Retell support line on +1 555 0100. Make sure it can book an appointment and never gives medical advice.”

From that one sentence Tessie creates the project, the phone channel, the booking and safety tests, and starts the runs.

If the channel has an Agent System Prompt — the system prompt of the agent under test — Tessie reads it as context when generating the suite, so the tests cover what the agent actually claims to do. The prompt is your IP: it is read-only context for Tessie and is never edited.

Use your connected systems through Integrations

When you connect a system under Integrations (Retell, Vapi, ElevenLabs, and others), Tessie can read from it directly — so you do not have to look up IDs and copy them in by hand. It can list the agents in your connected account, pull the agent and phone-number details a channel needs, and wire them onto the channel for you.

Manage schedules

Ask Tessie to schedule runs instead of triggering them by hand — for example, run a regression suite nightly, or before each release. It sets up the scheduled runs and you track them on the Queue and Dashboard.

Improve your prompts from real results

This is where the Console earns its keep. Tessie reads your actual test results — the transcripts, failures, and analyses — and proposes concrete improvements:

• Sharpen Testzilla’s own prompts — tighten a test’s scenario or pass/fail criteria, or the shared project and channel prompts that tests inherit.
• Fix the agent under test — when results reveal a weakness, Tessie can suggest edits to the prompt of the connected agent itself, and (for systems connected through Integrations) help apply those changes back to the source agent.

The loop is: run tests -> read results -> improve prompts -> re-run. Tessie drives all of it from chat.

Move and port agents between systems

Because Tessie can read connected systems through Integrations, it can help move or port an agent’s configuration between Integration accounts or systems — for example, lifting an agent’s setup from one connected account to another, so you can stand up the same agent in a new environment and test it there.

Caution

Tessie acts on your behalf and can create, change, and run things that cost credits, as well as propose edits to connected agents. Review what it suggests before applying changes to a production agent.

Where to find it

The Console / Tessie lives in the left nav of the web app. A compact Ask Tessie entry point also appears on the Dashboard and Projects pages for quick, in-context requests; the full-screen Console is for longer, multi-step work.

Console vs API vs MCP

All three drive the same Testzilla backend, scoped to your account — pick the surface that fits how you work:

Console (Tessie)

No code. Describe what you want in plain language inside the app. Best for setup, exploration, and improving prompts from results.

MCP

Drive Testzilla from your own AI agent (Claude Code, Cursor, and others) over the Model Context Protocol. See Integrate via MCP.

API

Automate from your own code and CI over REST. See Integrate via API.