How to configure a bot for attendant transfer Help Center February 24, 2023 19:56 Updated Transferring the tickets in your Human Service - Desk is essential to guarantee a good service for your customers, that's why we created a possibility for you to activate this solution directly. Another feature that will help after setting up the transfer by attendant is: How ticket distribution works. Make the following settings to enable it in your human service chatbot: To enable the functionality, the following walkthrough will change internal distribution settings. In the bot portal, click on the settings gear as shown below: On the settings screen, access advanced settings: “Click here to access advanced settings”. An alert modal will appear asking if you want to continue, click on “Confirm” to proceed. In the advanced settings, a list will appear with the columns: Domain, Key and Value. Look for the domain setting “firstname.lastname@example.org” and key “DistributionType”. This setting accepts SQL or Redis values. Click the pencil next to this setting to edit its value: Replace the current value with “Redis” and click on the confirmation icon on the side, as shown below: Ready! Now your bot uses the Redis distribution on the Desk. If your bot does not have this configuration available, it means that it uses the standard SQL distribution. In that case, follow these steps: Click “Add”: Fill in the fields as follows and click the confirm button on the side: Domain:email@example.com Key: DistributionType Value: Redis Ready! The new configuration has been added and your bot uses the Redis distribution on the Desk. For more information, visit the discussion on the subject in our community or the videos on our channel. 😃 Related articles Setting up Desk Human Service in Builder How to configure an active message response redirecting for an attendant in Blip Desk Sending WhatsApp Active Messages on Blip Desk Defining service Rules with one or multiple conditionals What Is the Dashboard?