Ticketing Delay Notification
Last updated
Was this helpful?
Help Center
Last updated
Was this helpful?
Due to various reasons, there can be a rare delay in ticket issuance. In such scenarios, the order would be sent to the exception queue. The customers have the option of getting notified about the delay by any one or multiple methods as explained below:
Email: The customer configures the email id in ATRIP.
DingTalk: Atlas configures a bot in the customer DingTalk group and the notification will be sent to that group.
Slack: Atlas configures a bot in the customer Slack group and the notification will be sent to that group.
Email Notification Configuration
Who will do the configuration?
Customer needs to add the email ids who need to receive these notifications.
Where can be configuration be done?
Atrip -> Profile -> My Profile -> Notification -> Email Notification
The email id which has been added will receive an email stating the reason for the delay. The customer can respond via a service request if they need to contact the operations team with regards to that order number.
What are the different reasons for the delay in ticket issuance?
The reasons for delay in ticket issuance can be any one of the following:
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?
The "Ticketing Delay Notification" will be displayed in the "Booking Details" screen when you hover the mouse over the booking status as shown in the below screenshot:
Why is a Service Request created for the ticketing delay notification?
A Service Request is only created when the reason for the delay is "Awaiting Customer Confirmation". The customer needs to respond back with the response when the customer is ready with the required information.
DingTalk Group Message Configuration
Who will do the configuration?
Atlas will do the configuration in the DingTalk group chat.
How can the configuration be done?
Step 1: Add the robot in the DingTalk group and obtain key parameters in the URL
Location: 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 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_token` in the webhook. This value needs to replace the `accessToken` value in the subsequent URL.
Step 2: Configure the client in the ops deck
Location: Client Library -> Details -> Operational Configuration -> Notification Configuration -> DingTalk.
Enter the URL.
URL example:
We need to replace the value corresponding to the value of access token and secret in the above sample in
The accessToken field value corresponding to the value of access_token in the webhook obtained by configuring the robot before.
The value of the secret field is the signed value configured in the robot before.
Specifically:
The value of the accessToken field should be replaced with the access_token value obtained from the DingTalk bot webhook.
The value of the secret field should be replaced with the signing value (secret) noted during the bot setup.
Once these values are inserted into the URL, the new URL should be configured in the DingTalk input field as shown below:
Slack Group Message Configuration
Who will do the configuration?
Atlas will do the configuration in the Slack group chat.
How can the configuration be done?
Step 1: Configure a Slack channel app and obtain the webhook URL.
Select the channel.
Right click on "view channel details".
Navigate to Integrations → Apps → Add an App.
Follow the page prompts to complete the setup.
After the final page, the Webhook URL displayed is the one you need.
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 for the Client in Ops Deck
Location: Client Library -> Details -> Operational Configuration -> Notification Configuration -> Slack
In the Slack section, enter the Webhook URL you obtained. This will allow notifications to be sent to the specified Slack channel according to your operational configurations.
