​Buttons for automating primary dialogs

Buttons for Telegram

You can show the client a button in Telegram by clicking on which something will happen. It is enough to send the client the construction {{button: Button text; link; blank}}, which will turn into a button, and the client can use it:


  • Button text – the name of the button. As an example, there might be a call to action. Specify the minimum possible limit of 32 characters;
  • Link – the link to which the button will lead. The link could be:
    • a link to an external resource that will open in a browser;
    • a link to the Telegram channel, which the client will go to immediately when he clicks on the button;
    • emptiness. If you do not specify anything, then the client will be able to click on the button, and the name of the button will be sent to you in Usedesk. You can customize any trigger for the name and continue the conversation with the client. An example with a rule is specified because the client will not receive any informational message when he clicks on the button.

You can write any text in front of the button, and the text will always be above the button. If there is no text, then an underscore will be sent because Telegram cannot send buttons with an empty message.

You can set a menu of buttons that your customers will navigate before starting a dialogue with the operator. An example of how buttons look in Usedesk and Telegram:

in Usedesk

in Telegram


Buttons for Instagram

Important!
Buttons don’t showing on Instagram web version. This feature is only available via mobile app.

You can show the client a button on Instagram that will trigger something. It is enough to send the client the construction {{button: Button text ;;; show}}, which will turn into a button and the client can use it:

Button text - the name of the button. As an example, there might be a call to action. Limited to 20 characters.


Unfortunately, Instagram itself does not support buttons with links, so sending only buttons with text remains possible.

You can form a menu of buttons that your clients will navigate before starting a dialogue with an operator. When the client clicks on the button, the selected option will be displayed, and the buttons will disappear. An example of how buttons look in Usedesk and Instagram:

in Usedesk


on Instagram


Buttons for a chat widget


You can read about the buttons in the chat of the widget in detail in our article.


Buttons for Facebook


You can show the client a button on Facebook that will trigger something. It is enough to send the client the construction {{button: Button text ;;; show}}, which will turn into a button, and the client can use it:

Button text – the name of the button. As an example, there might be a call to action. It is limited to 20 characters. If the text does not fit into the button, it will go under the ellipsis.
Unfortunately, Facebook does not support buttons with links, so it remains possible to send only buttons with text.

You can form a menu of buttons that your clients will navigate before starting a dialogue with an operator. The buttons are available in the Facebook channel with or without chat binding.

When the client clicks on the button, the selected option will be displayed, and the buttons will disappear. An example of how buttons look in Usedesk and Facebook:

in Usedesk


on Facebook

Was the article helpful?

Yes No