# If it arrives by email, it still gets on record.

> Each facility gets its own email address. Anything sent or forwarded there becomes a draft incident. Reports from supervisors, families and vendors then follow the same workflow as every other incident.

Source: https://incidentkit.ai/product/email-to-incident · Updated Oct 5, 2026

**Email-to-incident** (report): Forward a complaint or vendor email and it becomes a draft incident.

## What it does

- **An address per facility** Each site has its own address, tied to that site's routing and roles.
- **Drafts, not lost threads** The email becomes a draft incident, with the message kept as written, ready to complete.
- **Treated as sensitive** Inbound email can hold sensitive information, so it gets the same access controls as any incident.

## How it works

1. **Forward or send** To the facility's address.
2. **Draft created** The message and attachments become a draft incident.
3. **Complete and route** Lauren and a reviewer finish it like any other report.

## Frequently asked questions

### Is email-to-incident safe for patient information?

Not by itself, because email is not a secure channel. On the Regulated plan, we suggest a policy that keeps patient identifiers out of the email body and in the record. Inbound messages are handled as sensitive.

### Can we turn it off?

Yes. Email intake is set per facility.

## Related

- [Incident reporting software: forms, drafts, workflow](https://incidentkit.ai/product/incident-reporting)
- [Lauren: AI incident intake that a person signs](https://incidentkit.ai/product/lauren)
- [Migrate incident data from paper, Excel or legacy software](https://incidentkit.ai/product/import-and-migration)
- [HIPAA and BAA for incident reporting](https://incidentkit.ai/hipaa)
- [F609 reporting alleged violations: 2-hour and 24-hour rules](https://incidentkit.ai/compliance/f-tags/f609)