# Slack integration error with interactive components

**URL:** <https://forum.rasa.com/t/slack-integration-error-with-interactive-components/27047>\
**Category:** Rasa Open Source\
**Created:** [April 5, 2020, 12:38pm UTC](https://forum.rasa.com/t/slack-integration-error-with-interactive-components/27047 "2020-04-05T12:38:37Z")\
**Posts on this page:** 1\
**Showing post:** 46

<div class="post-metadata">

**Author:** ![cck197](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/cck197/32/7901_2.png) [@cck197](https://forum.rasa.com/u/cck197)\
**Post date:** [April 24, 2020, 1:17pm UTC](https://forum.rasa.com/t/slack-integration-error-with-interactive-components/27047/46 "2020-04-24T13:17:32Z")

</div>

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

[http://www.nointerface.com/book/](http://www.nointerface.com/book/)

---

_[View the full topic](https://forum.rasa.com/t/slack-integration-error-with-interactive-components/27047)._
