---
title: "Test your AI Employee with ChatGPT or a connected AI assistant"
description: "Let a connected AI assistant build scenarios, role-play customers, and review actual Mr. AI Testing replies instead of running every test manually."
language: en
canonical: https://mrailabs.com/docs/en/settings-and-usage/test-ai-employee-with-connected-assistant/
published: 2026-09-29T19:19:10.681386
last_verified: 2026-09-29T19:19:10.681386
audience: "For account admins"
---

# Test your AI Employee with ChatGPT or a connected AI assistant
## Can ChatGPT test my Mr. AI Employee for me?

Yes, when the Mr. AI account is connected to an assistant that supports the Testing tools. The assistant can build scenarios, start a Test Session, act as a customer, send messages into Mr. AI Testing, continue the conversation, then review the returned replies and summarize problems. The reply being evaluated must come from Mr. AI Testing itself, not from ChatGPT writing an answer on its own.

- The connected assistant organizes the test; Mr. AI Testing generates the reply under test.
- Use a separate Scenario for each important journey.
- Start a fresh Scenario after an important change.

## A practical request

> **Ready-to-use prompt**
> Test my AI Employee for pricing, product discovery, objection handling, and asking for a human agent. Use Mr. AI Testing on every turn, then summarize the problems you find.

## What can the connected assistant do?

- Build scenarios around the change you made.
- Start an isolated Test Session.
- Act as a customer and send real test messages into Mr. AI Testing.
- Continue multi-turn testing inside the same Session.
- Review AI Employee replies returned by Testing Chat.
- Try multiple Scenarios and summarize recurring gaps.
- Test supported Proposed Configuration before publishing it.

> **The most important rule**
> If ChatGPT writes an answer itself without running Mr. AI Testing, that is not a test of your AI Employee. Ask it to use Testing and evaluate the reply returned by Mr. AI.

## Current AI Testing service limits

- Current limit: 15 successful Testing messages per Session.
- Current limit: 6 new Testing Sessions per Workspace per day.
- Current limit: 90 Testing Messages per Workspace per day.
- Current Session lifetime: 4 hours.
- The daily boundary uses Africa/Cairo.
- MCP Testing messages do not deduct Customer Points.
- MCP Testing V1 accepts Text only; Image and Audio are available in Dashboard Testing.

> **Limits can change**
> These are current service limits and can change through server configuration. Treat them as current limits, not a permanent plan promise.

## After an important change

Start a fresh Scenario even if an older one is still active. This keeps the new replies from being blurred by conversation context created before the change. For supported proposals, you can also test the proposed configuration before Publish.

> **Test before Publish**
> Testing before publishing is the recommended quality workflow, but it is not a mandatory Publish Gate today.

## What remains inside Testing?

- No Customer Points are deducted for Testing messages.
- No delivery to a real customer channel.
- No real Business Action writes.
- No Follow-up scheduling and no real Stage Follow-up Task execution.

[Open Build & Manage with AI](/client/manage-with-ai)

[Read the Testing Playbook](/docs/en/learn/test-ai-employee-before-real-customers/)

[Test manually with Test Assistant](/docs/en/getting-started/test-assistant-before-live/)

[Review Build & Manage with AI](/docs/en/settings-and-usage/build-and-manage-with-ai/)

[Understand the AI Employee quality loop](/docs/en/knowledge-and-behavior/continuous-ai-employee-quality-loop/)