**Source URL:** https://quality.veevavault.help/en/lr/28400/index.md

# Using Complaint Intake & Promote to Complaint (QMS)

The _Complaint Intake_ object allows organizations to intake and triage potential product quality complaints for specific products and their respective batches before an associated _Complaint_ record is created automatically. QMS users can continue to create _Complaint_ records directly, but this feature helps streamline the process of receiving, triaging, and creating complaints.

This feature includes the _Promote to Complaint_ action for the _Complaint Intake_ object, which allows Vault to create one (1) or more _Complaints_ related to the source _Complaint Intake_ record. When this action executes, Vault copies active custom and standard fields from the _Complaint Intake_ to the resulting _Complaint_ records created from this action, including product information and attachments on the _Complaint Intake_ record. The _Promote to Complaint_ action can only be run once per _Complaint Intake_ record; attempting to execute the action multiple times will result in a system error.

To support the _Promote to Complaint_ automation, the objects and object types below are included in the standard QMS data model. These objects support the creation of related standalone _Complaint_ or _Quality Event Complaint_ records.

* **Complaint Intake**: Represents a potential complaint to be triaged. If necessary, one (1) or more _Complaint_ records can be created and related to the source _Complaint Intake_ record. The number of _Complaint_ records created depends on how an Admin configures the _Promote to Complaint_ action.
  *  **Complaint Intake**: Represents a potential pharma complaint. You can also use this object type to intake complaints of any custom object types on the _Complaint_ object.
  * **MedTech Complaint Intake**: Represents a potential medtech complaint.
* **Reported Product**: Represents the product associated with a _Complaint Intake_ record. Each _Complaint Intake_ record can have one (1) or more _Reported Product_ records.
* **Reported Product Batch**: Represents the product batch associated with a _Reported Product_ record. Each _Reported Product_ record can have one (1) or more _Reported Product Batch_ records.

Your Vault may process complaints using either a standalone _Complaint_ object or a _Quality Event_ of a _Complaint_ object type. In this article, these are collectively referred to as _Complaints_.

## Creating Complaint Records With Complaint Intake

Vault can create a _Complaint Intake_ record via an integrated third-party system, such as a manufacturer's website, or via complaint emails received in a configured [_Complaint Email Inbox_](/en/lr/61887102/). Vault users also can create a _Complaint Intake_ record manually. Once a _Complaint Intake_ record is initiated, users can complete a configurable _Complaint Intake Assessment_ process to determine if Vault should automatically generate one (1) or more _Complaint_ records.

The number of _Complaint_ records Vault creates from a _Complaint Intake_ depends on the number of _Reported Products_ and _Reported Product Batches_ and whether an Admin configures the _Promote to Complaint_ action to split by batch.

All required fields on the _Complaint_ record must be populated on the corresponding _Complaint Intake_ and _Reported Product_ records prior to executing the _Promote to Complaint_ action.

As outlined in the examples below, if Vault receives a _Complaint Intake_ record that includes one (1) _Reported Product_ and no _Reported Product Batches,_ the _Promote to Complaint_ action creates one (1) _Complaint_ record with the appropriate _Product_ listed. If Vault receives a _Complaint Intake_ record that includes two (2) _Reported Products_ and no _Reported Product Batches_, the _Promote to Complaint_ action results in the creation of two (2) _Complaint_ records with the appropriate _Products_ listed:

| Complaint Intake Record Received | Complaint Records Created |
| ----| ---- |
| CI-00001 <br/>**Reported Product:** Amoxicillin Tablet 100mg | COMPLAINT-00001 <br/>**Product:** Amoxicillin Tablet <br/>**Product Variant:** Amoxicillin Tablet 100mg |
| CI-00002 <br/>**Reported Product:** Amoxicillin Tablet 100mg  <br/><br/><br/> **Reported Product:** Amoxicillin Tablet 200mg | COMPLAINT-000002 <br/>**Product:** Amoxicillin Tablet <br/>**Product Variant:** Amoxicillin Tablet 100mg <br/><br/>COMPLAINT-000003 <br/>**Product:** Amoxicillin Tablet <br/>**Product Variant:** Amoxicillin Tablet 200mg |

If Vault receives a _Complaint Intake_ record with one (1) _Reported Product_ and two (2) _Reported Product Batches_ and an Admin has configured the action to split by batch, Vault creates two (2) _Complaint_ records, each with the associated _Product_ and _Batch_ records, for example:

| Complaint Intake Record Received | Complaint Records Created |
| ---- | ---- |
| CI-00003 <br/>**Reported Product:** Amoxicillin Tablet 250mg <br/>**Reported Product Batch:** Amox 250mg Tab Batch 001 <br/>**Reported Product Batch:** Amox 250mg Tab Batch 002 | COMPLAINT-000004 <br/>**Product:** Amoxicillin Tablet <br/>**Product Variant:** Amoxicillin Tablet 250mg <br/>**Batch:** Amox 250mg Tab Batch 001 <br/><br/>COMPLAINT-000005 <br/>**Product:** Amoxicillin Tablet <br/>**Product Variant:** Amoxicillin Tablet 250mg <br/>**Batch:** Amox 250mg Tab Batch 002 |

If Vault receives a _Complaint Intake_ record with one (1) _Reported Product_ and two (2) _Reported Product Batches_ and an Admin has not configured the action to split by batch, Vault creates one (1) _Complaint_ record with the associated _Product_ and _Batch_ records, for example:

| Complaint Intake Record Received | Complaint Records Created |
| ---- | ---- |
| CI-00004 <br/>**Reported Product:** Amoxicillin Tablet 300mg <br/>**Reported Product Batch:** Amox 300mg Tab Batch 111 <br/>**Reported Product Batch:** Amox 300mg Tab Batch 222 | COMPLAINT-000006 <br/>**Product:** Amoxicillin Tablet <br/>**Product Variant:** Amoxicillin Tablet 300mg <br/>**Batch:** Amox 300mg Tab Batch 111 <br/>**Batch:** Amox 300mg Tab Batch 222 |

### Creating Complaint Contacts {#complaint-contacts}

When creating _Complaint Intake_ records, you can create related _Complaint Contacts_ to manage information about reporters and complainants. This is required if your process involves sending [external notifications](/en/lr/77669/#complaint-contacts) from a _Complaint Intake_. Notifications sent from _Complaints_ may also require creating _Complaint Contact_ records related to a _Complaint Intake_.

_Complaint Contact_ records are specific to a _Complaint Intake_ record. If configured in your Vault, you may be able to select a _Master Complaint Contact_ record when creating a new contact to populate details about the contact.

The _Promote to Complaint_ action does not copy related _Complaint Contact_ records, but you can view and manage the _Complaint Contacts_ related to a source _Complaint Intake_ from the _Complaint Contacts_ section on the created _Complaint_ records. For _Complaints_ to display _Complaint Contacts_, they must have the _Complaint Intake_ reference field populated.

### Managing Complaint Intake Follow-Ups {#follow-ups}

If configured by your Admin, you can create and manage follow-ups for _Complaint Intakes_ from the _Complaint Intake Follow-Up_ section on a _Complaint Intake_ record, and on any _Complaints_ created from the intake. If you add attachments to the _Attachments_ section of a _Complaint Intake Follow-Up_ record, Vault displays these attachments in a _Complaint Intake Follow-Up Attachments_ section on the related _Complaint Intake_ record, and on any _Complaints_ created from the intake. For _Complaints_ to display follow-ups and follow-up attachments, they must have the _Complaint Intake_ reference field populated.

The _Promote to Complaint_ action does not copy _Complaint Intake Follow-Up_ records or their attachments, but follow-ups and attachments related to a source _Complaint Intake_ display on the _Complaints_ created from the intake.

## Supported Attachment File Formats {#supported-formats}

When the _Promote to Complaint_ action runs, Vault copies attachments in the following file formats from the _Complaint Intake_ record to the created _Complaint_ records: CSV, DOC, DOCM, DOCX, EML, HTML, JPEG, JSON, LOG, MP4, MSG, PDF, PNG, PPTX, RTF, TXT, XLS, XLSM, XLSX, and ZIP. Attachments in these formats are also available as viewable renditions on _Complaint_ records. Vault may copy attachments in other file formats, but they must be downloaded to be viewed.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: The <em>Promote to Complaint</em> action does not copy attachments related to <em>Complaint Intake Follow-Up</em> records. You can view these attachments in the <em>Follow-Up Attachments</em> section on <em>Complaint Intake</em> records and related <em>Complaint</em> records created from the intake.</p>
    </div>
  </div>
</div>



## Translating Complaint Intake & Complaint Records

Depending on your Vault's configuration and your organization's complaint intake process, you may need to change the state of _Complaint Intake_ or _Complaint_ records or run a user action to translate key fields on these records. See [Working with Quality Automated Language Translations](/en/lr/981285/) for more details.

## Related Permissions

To create and manage _Complaint Intake_ records, users require _Read_, _Create_, and _Edit_ permissions for the _Complaint Intake_ or _Quality Event Complaint Intake_, _Reported Product_, and _Reported Product Batch_ objects.

To create and manage _Complaint Contacts_, users require _Read_, _Create_, and _Edit_ permissions for the _Complaint Contact_ object, and _View_ permission for the _Complaint Contacts_ object control on the applicable object (_Complaint_ or _Quality Event_).

To create and manage _Complaint Intake Follow-Ups_, users require _Read_, _Create_, and _Edit_ permissions for the _Complaint Intake Follow-Up_ object, and _View_ permission for the _Complaint Intake Follow-Up_ and _Follow-Up Attachments_ object controls on the _Complaint Intake_ and _Complaint_ or _Quality Event_ objects.