> For the complete documentation index, see [llms.txt](https://docs.pharos.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pharos.ai/configuration-guide/error-tracking/email-to-case-error-tracking.md).

# Email-to-Case Error Tracking

How Pharos captures Email-to-Case failures depending on Support Settings and Case User configuration.

Email-to-Case is a critical entry point for customer data. When emails fail to create or update cases—due to parsing errors, validation rule failures, required field violations, or assignment rule issues—those failures can mean lost opportunities and invisible support requests. Pharos captures these errors using the same email-based approach as Apex exceptions—an email service receives the notifications and creates log records. The configuration path depends on your org's **Support Settings** (Setup → Support Settings).

***

## Two Configuration Paths

Depending on your org's Support Settings, Pharos uses one of two approaches to route Email-to-Case errors to its email service. Pharos detects which configuration applies and makes the appropriate update. Use the information tooltip (ⓘ) on the Error Tracking screen for the specific address Pharos uses in your org.

### Path 1: Email for Automated Case User Notifications

When your Support Settings include **Email for Automated Case User Notifications**, Pharos updates this field to the Pharos email service address. Error notifications are then sent to that address and captured by Pharos. This is the preferred path—it uses a dedicated notification field and does not modify any user record.

![Support Settings — Email for Automated Case User Notifications](https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-9c2672802b21697c234fe0839edbefc20811aa9e%2Fsupport-settings-email-notifications.png?alt=media)

### Path 2: Automated Case User's Email

When your org uses an **Automated Case User** (a user record that owns cases created from email and appears in Case History for automated case changes), Pharos updates that user's **Email** field to the Pharos email service address. This ensures error notifications sent to the case owner are captured by Pharos.

![Support Settings — Automated Case User](https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-9e5971e2856842722a96eff90df7074b0a8130d6%2Fsupport-settings-automated-case-user.png?alt=media)

**Important:** This must be carefully considered if the Automated Case User is an actual end user. Updating their email address affects their ability to receive other correspondence at that address. If you do not wish to change the user's email, use the workaround below.

{% hint style="warning" %}
**Automated Case User is a real person?** Pharos will update their Email field to the Pharos email service address. If you prefer not to change the user's email, have the user set up an email forwarding rule instead: forward emails containing "email to case error" (or similar) to the Pharos email service address. Pharos can still capture those forwarded messages.
{% endhint %}

***

## What Gets Captured

Once configured, Pharos captures a range of Email-to-Case failures. The table below summarizes what is detected and the impact of each failure type.

| Failure Type                  | Impact              | Pharos Detection             |
| ----------------------------- | ------------------- | ---------------------------- |
| **Email parsing errors**      | Cases not created   | Captured with details        |
| **Validation rule failures**  | Leads/cases dropped | Captured with context        |
| **Required field violations** | Silent failures     | Full context provided        |
| **Assignment rule issues**    | No owner assigned   | Configuration fix identified |

{% hint style="info" %}
**Related:** [Automated Error Tracking — Email2Case and Web2Lead](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/log-ingestion-methods/automated-error-tracking.md)
{% endhint %}
