> For the complete documentation index, see [llms.txt](https://resources.atriptech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.atriptech.com/popular-topics/notification/ticketing-delay-notification.md). # Ticketing Delay Notification Due to various reasons, there can be a rare delay in ticket issuance. In such scenarios, the order is automatically routed to the Exception Queue. You can choose to receive ticket delay notifications through one or more of the following methods: **Email:** You can configure your email address in ATRIP. **DingTalk:** Atlas will set up a bot in your DingTalk group to send notifications. **Slack:** Atlas will set up a bot in your Slack group to send notifications. 1. **Email Notification Configuration** You can self-configure the email addresses you would like to set to receive these notifications. **Configuration Path**: ATRIP → Profile → My Profile → Notification → Email Notification ![](/files/BzkRvGEHFdGgN9OcLK8D) Once configured, the added email addresses will receive notifications explaining the reason for the delay. If you need to contact the Operations team about the affected order, you can respond via a service request stating the order number. regards to that order number. **Possible reasons for ticketing delay:** * System Issue * Sold Out * Awaiting Airline Confirmation * Awaiting Customer Confirmation * Airline System Issue * Payment Issue **Where can I see the ticketing delay notification in ATRIP?** You can view the **Ticketing Delay Notification** on the **Booking Details** screen. Hover your mouse over the booking status to see the reason for the delay. Refer to the below screenshot as a reference. ![](/files/PgYGGogWwrG4J5e9z3u9) **When is a Service Request created?** A **Service Request** is automatically created only when the delay reason is **“Awaiting Customer Confirmation”**. In this case, you’ll need to reply with the required information before the ticket can be issued. 2. **DingTalk Group Message Configuration** If you opt for notifications to be sent via DIngTalk, Atlas will assist in configuring this feature for you. **How to configure?** **Step 1: Add the robot in the DingTalk group and obtain key parameters in the URL** Path: **DingTalk → Group Settings → Bot → Add Robot → Customize.** ![](/files/LWqjyN9lGHWCZIexRLTh) * Add a bot to the DingTalk group and obtain the key parameter in the URL. * Check the "Add Signature" option in the security settings and write down the signature value. This value will be the value corresponding to the \`secret\` value in the URL later. * In the security settings, check the box for signing and note down the signing value, which will correspond to the \`secret\` value in the URL later. ![](/files/EC7YE3ZN1fVJN78lPDMd) * After clicking "Complete", note down the `access_token` in the webhook. This value needs to replace the `accessToken` value in the subsequent URL. **Step 2: Configure in Ops Deck** Path: **Client Library → Details → Operational Configuration → Notification Configuration → DingTalk.** * Enter the URL in this format: {% embed url="" %} * Replace: \ with the value you obtained from the DingTalk bot webhook. \ with the signing value you recorded earlier. * Once done, paste the new URL into the DingTalk input field in **Ops Deck** as shown below: ![](/files/ijcgxk2CzwDL5CGEP8Nw) 3. **Slack Group Message Configuration** If you opt for notifications to be sent via Slack, Atlas will assist in configuring this feature for you. **How to configure?** **Step 1: Configure a Slack channel app and obtain the webhook URL.** * Open your preferred Slack channel. * Right-click and select **View channel details.** * Go to **Integrations → Apps → Add an App.** * Follow the setup prompts. * Copy the **Webhook URL** displayed on the final page. > Please ensure you have the necessary permissions to add apps and integrations to the Slack channel. Once you have the Webhook URL, you can use it to send notifications or messages to the Slack channel as part of your operational configurations. ![](/files/lQkRJx1x6xKkhIPxMci0) ![](/files/c3tcRN9eptjakH7hPSGg) ![](/files/OcaiyIC3uPVC8aM5iknF) ![](/files/LGdSABT4zaGYg81f8a0V) **Step 2: Configure in Ops Deck** Path: **Client Library → Details → Operational Configuration → Notification Configuration → Slack** In the Slack section, enter the Webhook URL you obtained. This enables ticketing delay notifications to be sent directly to your Slack channel. ![](/files/JSXKfwKmRpnSOmFNG87V) --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://resources.atriptech.com/popular-topics/notification/ticketing-delay-notification.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.