Buttons for automating primary dialogs
Content
- follow the link;
- consistently select the topics of his message — for this, the button must activate the trigger that will send the next pool of buttons. Depending on the selected buttons, you can, for example, configure the assignment of a ticket to a specific agent or group;
- get the necessary information — for this, the button must activate a trigger that will send the specified text;
- get a form to fill in the data — to do this, the text of the button must activate the trigger that will send a message with the form.
Buttons creation
To create a button, use this constructor:
text {{button:button name;link;link type;visibility}}
- text — any text that will be displayed before the button;
- button name — the only required parameter — the text that will be displayed on the button;
- link — a link that will open when you click on the button (if necessary);
- link type — specify blank to open the link in a new tab or self (used by default) to open the link in the same tab;
- visibility — specify noshow so that the text of the button name is cut from the block of text before the button, or specify show (used by default) so that nothing changes.
This is how the buttons will look, for example, in a widget:
And this is how these buttons look in text form:
Important! When creating a button, you can not use optional parameters, and then semicolons between them are also not needed. But if you want to pass the last parameter «visibility» without using the parameters «link» and «link type», you will need to put all the dots with commas — like this:
text {{button:button name;;;visibility}}
Imagine a row of windows in a house. There may or may not be a person in each window, but the window frames remain unchanged. That is, we kind of «cut out» the parameters we don't need, and left semicolons between them.
Nuances
- Regular text buttons without links of the form {{button:button name}} work in all listed channels;
- Buttons with links work only in a widget, Telegram and VKontakte;
- The «link type» parameter works only in a widget. In Telegram and VKontakte, links can only be opened in the same tab. But if the parameter is specified, it will not break the operation of the button;
- The «visibility» parameter works only in a widget. But if the parameter is specified, it will not break the operation of the button.
Examples of buttons
All these button options will work correctly:
Text {{button:button name;https://usedesk.com;blank;show}} Text {{button:button name;https://usedesk.com;blank}} Text {{button:button name;https://usedesk.com}} Text {{button:button name}} {{button:button name}} {{button:button name;;;noshow}}
Buttons in Telegram
Sending buttons is available only if you integrate Telegram with Usedesk via a bot. It is not possible to send buttons via a personal telegram account. The maximum number of characters in the button text is 34.
This is how the sent buttons look in the Usedesk:
Buttons in Instagram
Buttons aren't displayed in Instagram web version — only in the app. The maximum number of characters in the button text is 20.
This is how the sent buttons look in the Usedesk:
Buttons in a widget chat
Buttons in VKontakte
- messages can be sent to to your VKontakte community:
- bot capabilities should be enabled in the community.
When setting up integration with VKontakte via Botmother (via chats), the buttons will not work, because Botmother does not perceive them.
Buttons in Facebook
The maximum number of characters in the button text is 20. If the text does not fit into the button, it will go under the ellipsis.
This is how the sent buttons look in the Usedesk:
And so — in the Facebook interface: