IPL FAQ chatbot made using AWS Lex.
A bot that generates a response based on multiple previous utterances as well as user’s queries to respond in a relevant and sensible manner. The bot also performs a long form of FAQ for various queries which we curated using the given dataset.
We built an extractive chatbot which is powered by a BERT question answering modelling running in the backend. Our model is in onnx format which allows it to run very efficiently on CPU. (Inference time 252 ms). We build context for the tabular data using natural language processing, this context allows us to have multi-turn dialogues without having to use some complex dialog management system
The whole backend is deployed on FastAPI which gives performance at par with Golang.
- Text to Speech Announcement
- Answers or Followup in Text Format
- Instant replies
- Conversational flow of dialog
- Verified and correct answers
- IPL betting games.
- Fantasy IPL where you can choose a team or player based on the best proven statistical fact based on previous data.
- General FAQ.
- Prove your friends wrong about a fact only you remember, within seconds.
- Video Demo [The bot itself won't work due to mixed content error by ngrok so please run it locally for now].
- Deployed Link.
$ git clone https://github.com/ramaneswaran/lexbot
$ cd lexbot
$ pip3 install -r requirements.txt
$ aws configureAdd your AWS Access Key, Secret Key and set the region to us-east-1. Leave the next field blank.
$ python3 bot.py$ git clone https://github.com/ramaneswaran/lexbot
$ cd lexbot
$ live-serverInstall the chrome extension for CORS Changing here and enable it.
- Open the site locally as mentioned above or visit this link.
- Start asking your queries by just typing and clicking on enter or submit on your device.
- Wait for less than a second to receive a followup to your query or the answer itself (in both voice and text formats).
- We intend to make this chatbot available on Twitch and other supported vendors soon while also adding more complex queries with an even faster response.
- We need to deploy the backend on a SSL verified domain as ngrok gives a mixed content error because it serves on http.