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.
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
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.
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.
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.
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.
After clicking "Complete", note down the
access_tokenin the webhook. This value needs to replace theaccessTokenvalue 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:
Replace:
<access_token> with the value you obtained from the DingTalk bot webhook.
<secret> with the signing value you recorded earlier.
Once done, paste the new URL into the DingTalk input field in Ops Deck as shown below:
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.
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.
Last updated