> For the complete documentation index, see [llms.txt](https://help.gleantap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.gleantap.com/campaigns/sending-a-test.md).
# Sending a Test
There are multiple ways to send test Email and SMS Campaigns. Follow the steps below to send yours.
## Test Email Campaign
### From the 'Content' Stage
**Step 1**: Make any necessary adjustments to your template, then click 'Save.'
**Step 2**: Type in the email address of the test recipient, then click 'Send Test.'
### From the 'Review & Send' Stage
**Step 1**: Find the 'Send Test Email To' box at the bottom right.
**Step 2**: Type in the email address of test recipient, then click 'Send Test.'
### From the 'Configure' Menu
**Step 1**: Click 'Configure' on the top right, then 'Test Message' from the dropdown menu.
**Step 2**: Select 'Email' from the 'Type' menu, enter the 'To' and 'From' email addresses, the subject line, and select the template, then click 'Send.'
## Test SMS Campaign
### From the 'Configure' Menu
**Step 1**: Click 'Configure' on the top right, then 'Test Message' from the dropdown menu.
**Step 2**: Select 'SMS / Text Message' from the 'Type' menu, enter the recipient's phone number, the message, and any files you'd like to include (maximum file size is 5MB), then click 'Send.'
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.gleantap.com/campaigns/sending-a-test.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
