Welcome to RASA Connector...!
Choose an option
* Help Center https://gethelp.tiledesk.com/
* I want an agent
It will render as a couple of messages, an image ad a couple of buttons (the first is a link-button, the second a Quick reply button)
To add an image use the tdImage syntax, as in the following example
Multiline syntax (tdImage example):
Welcome to RASA Connector...!
Choose an option
tdImage:https://i.imgur.com/nGF1K8f.jpg
* Help Center https://gethelp.tiledesk.com/
* I want an agent
RASA single line syntax:
- text: "Welcome to RASA Connector...!\n\nChoose an option\ntdImage:https://i.imgur.com/nGF1K8f.jpg\n* Help Center https://gethelp.tiledesk.com/\n* I want an agent"
We’ll send a newsletter when the RASA protocol will be fully supported.
According to my tests the example of markdown with buttons is not working, I was able to display map, video and image but in isolation. I’ll wait for improvements in the Rasa module. Thanks!
We released a new version of the Rasa chatbot with support for native RASA buttons and images (also based on your feedback in this thread, telling us that markbot was not working).
So we disabled markbot in this new release, considering rasa native support is better.
But we are open for discussion. Do you think Markbot is still useful?
What might be useful for next time is to leave the Markbot on for a few more releases so people have a chance to convert it. Now I find out about it by accident and have to spend today to convert everything.
Because you told us that markbot was not working (and because we still do not have many feedback on this RASA integration) we concluded (probably mistakenly) that native RASA support was better than markbot (that probably it’s diffuclt to understand).
We are trying to enable both (markbot and rasa native) in the next release with the option to disable Markbot is it creates problems for a particular project.
You are right, I was totally confused Thanks to be comprensive!
We are struggling to understand how to have a good “compatibility policy” between Tiledesk’s Markbot and RASA native format to support both simultaneously. I’m sorry for you guys that are rebuilding everything again and again becasue of our own issues. Just a little patience.
Anyway, just to be transparent, we think that only using “native RASA” you can’t address:
tdFrame (that will go completily missing in the integration)
Link Buttons (very useful in some cases) that we do not see RASA supports
So we think that markbot is necessary if you want full integration.
The idea is to “merge” buttons, the ones coming from RASA with those coming from markbot.
And support all the other things like tdFrame.
While there is some other problem with native RASA images, where we see RASA sending images always as separate messages, while Tiledesk is able to send the image with his description text as a single message.
Any opinion is useful.
And please consider this module as a “Beta”, we just have to evidence it in the Console in the next release
So the full rasa integration, because that’s easy for people who are familiar with Rasa. And the Markbot language, because that gives you full flexibility to develop custom replies.
Personally I would focus on Markbot, because of the flexibility to develop your own things. Take for example the facebook messenger. Facebook messenger has the “carousel” which is not something that rasa offers by default, but is possible by sending a response in json format.
By doing both you can have the best of both worlds.
I would have a use for that.
And what you point out. I am already using the tdFrame and especially the Link Buttons. I don’t want to miss those now
By the way is there any chance that Markbot will turn on again for the Rasa connector?
We updated Tiledesk Cloud with a new RASA connector release.
Now the RASA connector supports both Native RASA buttons+Images+splittedMessages and Markbot (adding support for Tiledesk URL-Buttons, tdFrame, tdImage etc.). Bug fixing too.
Just connect your RASA server and let me know if it works as expected.