> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm-1/arm-features/environment-provisioning/unsupported-metadata-templates/email-to-case-settings/email-to-case.md).

# Email to Case

The **EmailToCase** template allows users to configure either On-Demand Email-to-Case or standard Email-to-Case settings within Salesforce via AutoRABIT.

## Steps to Create the EmailToCase Template

1. Log in to your AutoRABIT account.
2. Navigate to the **Env. Pro.** module.
3. Click **Create New Template**.
4. Select the **Create Unsupported Metadata Template** tab.
5. Enter a **template name** and a **short description**.
6. Check the **EmailToCase** box under the **Email to Case Setting** section.
7. Click **Add**.
8. On the next screen, a **Test Case Name** is automatically generated. Click **Add** to provide custom test data. Fill in the necessary details, then click **Save**.

   ![EmailToCase Test Case Screen](/files/n7czgnYLgKIfhKuttRj6)
9. Click **Save** again to finalize and save the template.
10. After creation, you will be redirected to the **Environment Provisioning History** screen.
11. Click **Run** to execute the template in your destination org.
12. Choose the **destination org** from the dropdown and provide **email address(es)** to receive notification emails.
13. Under **Post Deployment Steps**, select the recently created test cases.
14. Visit the **View History** page for a comprehensive summary of the executed operations.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledgebase.autorabit.com/product-guides/arm-1/arm-features/environment-provisioning/unsupported-metadata-templates/email-to-case-settings/email-to-case.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.