Bot to read QRs and return a coupon
Budget: $250 – $750 USD
Hello, I need a chatbot (that will be be added on a webchat, whatsapp, messenger or telegram) that will use the phone camera through the chat app to read a QR and return a coupon.
The functionality will be something like this:
1) Open your chat app
2) Open camera and take picture of QR code
3) Bot will do 2 things: (1) register in the database (create a log line) recording that the user "xxx" (phone number or id from social network) required "this coupon" on "this date" and (2) will return the image of the coupon, the QR image of the coupon and the coupon description after matching the QR content on the coupon DB
Initially this should work in a web chat funcionality (when the user should identify itself first) but a bonus would be having the option on WhatsApp (using twilio or 360dialog for the administration of WhatsApp having the user sending a whatsapp message first or opening the whatsapp app directly from the QR code, open to suggestions) or Facebook Messenger.
If possible, Dialogflow would be preferred because this is the first part of a complete solution, but I am open to alternatives (maybe something like that is not needed for now).
The functionality will be something like this:
1) Open your chat app
2) Open camera and take picture of QR code
3) Bot will do 2 things: (1) register in the database (create a log line) recording that the user "xxx" (phone number or id from social network) required "this coupon" on "this date" and (2) will return the image of the coupon, the QR image of the coupon and the coupon description after matching the QR content on the coupon DB
Initially this should work in a web chat funcionality (when the user should identify itself first) but a bonus would be having the option on WhatsApp (using twilio or 360dialog for the administration of WhatsApp having the user sending a whatsapp message first or opening the whatsapp app directly from the QR code, open to suggestions) or Facebook Messenger.
If possible, Dialogflow would be preferred because this is the first part of a complete solution, but I am open to alternatives (maybe something like that is not needed for now).