I don’t think so buttons will be available for Voice and for sms you can show buttons as menu form just like ordered list.
1 Like
I just got going on Whatsapp via Twilio. The buttons are rendered as a numbered list and as far as I can tell, the only way to respond is to type the payload or something that hits the appropriate intent.
Hey @cck197 if this is something you are stuck at please raise another topic as this topic is related to slack integration 
It might be relevant here if we end up spending a lot of time making it work on Slack when it can’t work elsewhere. Or can it work elsewhere? Is there any evidence of buttons working via SMS or WhatsApp?
@cck197 buttons won’t work with SMS or Whatsapp (though I think Whatsapp are working on developing something along the lines of buttons). On Slack, however, they should work, but I think we’ve discovered a bug with it due to an update of one of the packages we use - @stephens maybe you can chime in here
Thanks for your response! I appreciate it. I think Rasa is an incredible product and I’m excited about what I might be able to build using it. What you just said is exactly the type of thing I’d like to see more of in the docs!
Rather than:
Responses defined in a domain’s yaml file can contain images and buttons as well
Be more opinionated and say something like: “Responses defined in a domain’s yaml file can contain images and buttons as well but understand that in using them, you’re making a design decision. In essence, Rasa is about natural language processing, and UI elements like buttons may not render on all channels, e.g. SMS and voice.”
#noui
I’m looking at a couple of things in the slack connector and will get back regarding the buttons. I also ran into an issue with that.
1 Like
Hi @stephens
Thanks for having a look at the issue.
Did you found something relevant to this problem? we are having the same problem
cheers
No, I’m just back from vacation and don’t have any updates.