> ## Documentation Index
> Fetch the complete documentation index at: https://kero.chat/help/llms.txt
> Use this file to discover all available pages before exploring further.

# Add an RCS test device

> Add a test device to your RCS Agent and experience your messaging as a customer before launch.

Before your RCS Agent is launched, you can add an RCS-enabled mobile device to test how your Agent and messages appear to customers.

Testing helps you check your Agent's branding, message content and interactive features before external verification and launch.

> [!NOTE]
>
> Your RCS Agent must have been created and be available for testing before a test device can be activated.
>
> This normally takes place when your Agent reaches **Ready for Verification**.

## 1. Open your test devices

Open the RCS Agent you want to test and go to **Test devices**.

You'll see the mobile numbers that have already been added to the Agent and their current status.

## 2. Create a test device

Select **+ Create Test Device**.

Enter the following information:

**Mobile Number**

Enter the mobile number of the device you want to use for testing, including the country code.

For example: `+27780004444`

**Note**

Add an optional description to help you identify the device.

For example: `Marketing Team Test Phone`

Select **Create**.

> [!NOTE]
>
> The mobile number should belong to an RCS-enabled device that you can access during testing.

## 3. Accept the tester invitation

After you create the test device, an invitation is sent to the mobile number.

Open the invitation in **Google Messages** and select **Make me a tester**.

You'll receive confirmation that the device has been added as a tester for your RCS Agent.

> [!WARNING]
>
> Adding the mobile number in Kero does not activate the test device. The tester invitation must be accepted on the phone before the device can be used for testing.

## 4. Check the device status

Return to **Test devices** in Kero.

Once the tester invitation has been accepted, the device status changes to **Active**.

Your device is now ready to receive test messages from the Agent.

## 5. Test your RCS Agent

Once your device is active, use it to experience your RCS messaging as a customer would.

Check:

* **Agent identity:** Your Agent name, logo and branding are correct.
* **Message content:** Text, images and other rich media display as expected.
* **Interactive features:** Suggested replies, actions and links work correctly.
* **Customer experience:** The message is clear, recognisable and easy to interact with.

Testing gives you an opportunity to identify any changes you want to make before your Agent proceeds to external verification and launch.

> [!TIP]
>
> Test your Agent from the recipient's perspective. Check that customers can recognise your business, understand the message and complete the intended action.

## Manage a test device

Select an existing test device to view or update it.

You can:

* Update the **Note**
* Save your changes
* Delete the test device if it is no longer required

> [!WARNING]
>
> Deleting a test device removes it from the Agent's tester list.

## What happens after testing?

Once your testing is complete and your Agent is ready for external verification, a Kero Customer Success Specialist coordinates its submission through the relevant RCS provider.

Your Agent progresses from **Ready for Verification** to **Verifying** when external verification begins.

During verification, Google Support and the relevant mobile network operators may email your business contact to confirm that your business authorised Kero to create the RCS Agent.

**Your responsibility:** Respond promptly to these verification emails. Delays in responding may delay your Agent's approval and launch.

For more information about the approval process, see [RCS Agent verification and launch](https://kero.chat/help/rcs-agent-verification-and-launch).

> [!NOTE]
>
> Testing your Agent does not mean it has been approved for live customer messaging. Your Agent must reach **Launched** before you can send live RCS messages.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.