Send selected inventory update requests with a clear description of the problem so support can investigate the affected property, channel and dates.

## Before you start

- Select the affected property. This guide starts at **Updates → Status**, not the organization-wide Updates screen.
- You need access to the property and at least one existing update request to include. Sending a support request does not require permission to change rates, availability or restrictions.
- This workflow concerns outbound inventory updates, not reservation delivery.
- The public demonstration login can search and view request details, but cannot use **Go** to open this workflow or submit a support message.

**Sending to support is not a retry.** It does not resend inventory, change the selected requests' processing status, archive them, or correct the channel's rates and availability. Do not select **Retry** instead when your intention is to ask for help.

## Select the requests

1. Select the affected property in the property selector.
2. Open **Updates → Status**.
3. Choose the relevant **Status**, **Channel**, **Room Type** or **Rate Plan** filters. Leave **Status** at **All** if you are unsure of the current result.
4. Click **Search**.
5. Review the requests' channel, product, affected dates, values and status message.
6. Tick the checkbox beside each request you want support to investigate.
7. Choose **Send To Support** in the action dropdown.
8. Click **Go**.

**Search** loads results; **Go** runs the selected action. Check the action dropdown before clicking Go. The checkbox in the table heading selects requests on the current page, not every matching request on other pages. Select related requests for the same issue rather than sending an unrelated batch.

Opening **Send To Support** does not send the email. It shows **Subject**, **Message**, **Send**, **Cancel**, and an **Update Requests** section containing your selection.

## Review the selection and describe the problem

1. Check the property, channel, product and dates in **Update Requests**. If the selection is wrong or empty, use **Cancel** and select the correct requests again.
2. Enter a short **Subject** that identifies the issue, such as “Availability differs for the weekend.”
3. In **Message**, describe what you expected and what you observed.
4. Include the affected stay dates, room type/rate plan, the time you made the change and its time zone, and any relevant error text.
5. Mention any troubleshooting or retry you have already performed.
6. Click **Send** once when you intend to submit the message to support.

![Blank Send To Support form with Subject, Message, Send and Cancel controls](https://support.channelrush.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBcWNCIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--b67a5751e7942bed3223de651aec3e3635b666e8/updates-send-to-support-form.png)

*The fields start blank. The selected requests appear in a separate section below the form.*

Both text fields are optional in the form, but a useful subject and explanation help support understand the issue. At least one selected request belonging to the current property is needed to send.

Do not include passwords, API keys, payment details or unnecessary guest information. If you need to retain your unsent explanation while changing the selection, copy it before leaving the form; there is no Save Draft control.

### What is included automatically?

The message includes generated summaries of the selected requests, with identifying information such as request ID, channel, organization/property, products, affected dates and selected weekdays. It also includes supported summary values, any recorded status message, and request timestamps. Your signed-in name, email address and property are included so support can identify the sender.

**The request list is not an exact preview of the outgoing email.** The summary does not attach every attempt log or include every field shown on screen. Describe consequential values in your message, especially additional channel parameters or through-stay restrictions. There is no attachment uploader or recipient selector on this form; the support destination is determined by your organization's support arrangement.

The requests are read again when you click **Send**. If processing continues while the form is open, the details sent can reflect a later state than the one you first viewed.

## Check the result

After a normal submission, the application returns to **Update Status** and displays:

> The selected update requests have been sent to support along with your message.

This is the application's send confirmation, **not a delivery receipt or acknowledgement from a support agent**. It does not confirm that the inventory problem is resolved or that a channel accepted an update. No ticket number or guaranteed response time is provided by this form.

Check the selected property and search filters after returning. Not every filter is preserved through the support workflow. Set the scope you want and click **Search** again before interpreting the results or taking another action.

If the page errors, the confirmation is unclear, or you need receipt confirmed, contact support through your usual support channel with the property, request IDs, subject and approximate send time. **Do not repeatedly click Send or resubmit merely to obtain a clearer result:** another submission can create another email.

## Read the selected-request reference

The **Update Requests** section is read-only. It lets you verify that you are escalating the intended requests; it is not an inventory editor or a live comparison with the channel.

![Selected demo inventory request showing its channel, room, allocation, processing status and timestamps](https://support.channelrush.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBcWdCIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--19fc4bab43172cdb91657b1ddb66f298cae19023/updates-send-to-support-request.png)

*This demo request records a successful allocation update. Its status is the inventory request's processing result, not the result of sending a support email.*

| Item | What to check |
|---|---|
| **Channel / Room Type / Rate Plan** | The property and destination products affected by the request. A rate plan appears when applicable. **VRT** identifies a virtual room type. |
| **Updates** | The inventory dates, selected weekdays when shown, and values carried by the request. These are not the dates the support message was sent. |
| **Sell Rate / Net Rate** | Requested amounts and currency when present. An asterisk identifies the selected rate type. |
| **Allocation / Stop Sell** | The room quantity and sales-open/closed value carried by the request. |
| **CTA / CTD** | Closed to arrival / closed to departure values when present. |
| **Min Nights / Max Nights** | Minimum/maximum stay values when present. |
| **Min Nights Through / Max Nights Through** | Through-stay restriction values when present. Include them in Message if they are central to the issue. |
| **Cut Off Days** | The advance-booking cutoff value when present. |
| **Additional parameters** | Channel-specific rate or other values, when applicable. Explain the relevant parameter in your message rather than assuming it is included in the email summary. |
| **Status and message** | The stored inventory-processing result and any explanation. Read the message as well as the colored indicator. Successful is not a fresh check of the channel's current inventory. |
| **Attempts** | The processing-attempt count, not a count of confirmed successful deliveries. |
| **Source / user** | Where the update originated, such as **UI - Quick**, and user information when available. |
| **Archived** | When shown, the request has an archive flag. This is separate from processing status and does not mean the issue was resolved. |
| **ID** | The inventory request identifier to quote to support. It is not a reservation number. |
| **Created / Last Run** | Recorded creation and processing/edit times, displayed in your user time zone. Last Run alone does not establish a successful delivery. Include the zone when describing events. |
| **Logs** | Opens available attempt-log details in a new tab. Opening it does not resend inventory, and the log is not automatically attached to this support email. |

A missing value is not automatically zero, No, or an instruction to clear a restriction. **[BLANK / NOT SET]** indicates missing product-name information; explain it to support if it affects the investigation.

## Cancel without sending

Click **Cancel** to leave the form without sending its message. If a discard warning appears after you have typed text, keep the form open if you still need that text, or confirm leaving when you intend to discard it.

After returning, verify the property selector and filters before searching again. If they are not the intended scope, reselect the property, open **Updates → Status**, set the filters and click **Search**. Do not rely on the **Status Updates** breadcrumb to preserve the originating scope.

## Common problems

- **No requests selected.** The selection is empty or no longer contains a request available for the current property. Return to **Updates → Status**, check the property, click **Search**, and select the intended requests again. If a known ID remains unavailable, give it to support rather than resending inventory to generate a new request.
- **A request you expected is missing.** Check the property, status, product and date filters on Update Status. Broaden the relevant search and click **Search**. An empty result does not prove that an update was never saved or sent.
- **Go does not open the support form.** Check that **Send To Support** is selected and at least one row is checked. If the page says **Actions do not match**, make the top and bottom action dropdowns agree. A demonstration-account warning means this action is unavailable for that login; do not attempt to work around the restriction.
- **The wrong property or filters appear on return.** Reselect the property and rebuild the search before continuing. If the navigation problem persists, report the originating page and expected property to support.
- **Send reports an error or no clear result.** Keep the request IDs, subject and send time. Check with support before submitting again because the email may already have been attempted.
- **The confirmation appears but the inventory issue remains.** The form requests investigation; it does not repair inventory. Follow up with the original request IDs and current observations. Do not retry or archive requests as a substitute for confirming the correct recovery action.

## Related

- [Investigate inventory update requests across properties](https://help.channelrush.com/hc/channelrush/articles/status-updates) — the separate organization-wide workflow, for users with the relevant access.
- [Investigate stored inventory differences](https://help.channelrush.com/hc/channelrush/articles/inventory-consistency)
