> 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.md).

# Email to Case Settings

Configure your **Email-to-Case settings** on this page. Each routing address is an email address that the customers can use to submit cases to your support team. Emails are automatically converted to cases based on the settings specified for each routing address.

After you configure your Email-to-Case settings, choose whether to set up On-Demand Email-to-Case or Email-to-Case. On-Demand Email-to-Case enables you to solely use Force.com to convert email to cases, whereas Email-to-Case enables you to use salesforce.com and your email system to convert email to cases.

#### **For On-Demand Email-to-Case:**

1. Define email addresses on your email system for case submissions.
2. Create email routing addresses that include the addresses defined for cases.
3. Configure your email system to forward case submissions to the Email Services Address provided to you by Salesforce.
4. Enable On-Demand Email-to-Case.

#### **For Email-to-Case:**

1. Download the Email-to-Case agent from the Apex Developer Network.
2. Install the agent behind your network firewall.
3. Configure email routing addresses.
4. Enable Email-to-Case.


---

# 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://knowledgebase.autorabit.com/product-guides/arm-1/arm-features/environment-provisioning/unsupported-metadata-templates/email-to-case-settings.md?ask=<question>&goal=<user_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.