I used a test environment of an external system for Context Links while learning how they worked. Even deleting the app doesn't remove the links... I'd like to be able to remove all the dev ones.
In certain reports - especially the CSAT report - the "internal" account is counted in the same metrics as customers in the Accounts Table. It would be great to exclude them.
Context Links should contain conversation attributes
Context links are great and we use the time. It would be fantastic if they could be used to transport information from front into the linked system, most critically conversationID or messageID. This could happen via an amended query string or via ...
Export - export table content as displayed on screen
allow to export the data as displayed on the screen
i.e taking into account filters, displayed column and formatting
This avoids doing the work twice one time on the screen then back into the export
Keyboard shortcut: use keyboard arrows to move from P2 to P3 to scroll down P3
Keyboard users scrolling down P2 using the down arrow would like to move to P3 using the right arrow to then use the down arrow to view whole email if too long to fit to view
Customize chatbot flow based on chat visitor geographic location
Ability to customize the chatbot flow and serve a different flow to chat visitors based on their geographic location. For example, many companies only service particular regions or countries. It would be great if the chatbot could determine a user...
Bulk SMS using a template with different recipient names.
We would like to send bulk SMS out using a template that will pull the name in each SMS such as 'Hi Sam' and 'Hi Kate' so the SMS does not copy the name for every recipient.
Now that the core API supports groups, it would be nice to be able to add custom fields to them as well. For my use case, I want to add a boolean value to tell my application if users should be allowed to add themselves to the group via API.