Let’s just say, we have a kind of article subscription app, and we got dozens of feedback everyday.
Supposed we have several type of account:
- Free
- Buy article coins, and using these coins to read some articles
- Subscription users
Some of the feedback would look like:
- Why I can’t read article even I’m a subscription user?
- I can not by coins
- The article couldn’t be load
- Why all my 100 coins lost?
- My app crash.
- I have waited for 2 days for reply. Are you kidding me? I could read the article a month ago, and you just copy-and-pasted to reply me? DO YOU TAKE ME FOR SERIOUS??!! …
The traditional seq2seq chatbot seems not applying to my specific case, what I wanna to is:
- Know what the user want, like “Why I can’t read article even I’m a subscription user?”, we would like to ask the user send us the article ID or url, and check the user’s status from internal backend services.
- Classify the feedback type, like “My app crash.”, then upload the crash log from app and kick off a Jira ticket.
- Summarization, like " I have waited for 2 days for reply. Are you kidding me?.."
What’s more, we are not an English app, so we might need to train our model with our language.
I was wondering if maybe RASA is the right tool in this case?