Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Customer Chatbot #157

Merged
merged 10 commits into from
Mar 23, 2024
Merged

Customer Chatbot #157

merged 10 commits into from
Mar 23, 2024

Conversation

neelasha23
Copy link
Contributor

@neelasha23 neelasha23 commented Mar 15, 2024

Closes #139


📚 Documentation preview 📚: https://ploomber-doc--157.org.readthedocs.build/en/157/

@neelasha23 neelasha23 marked this pull request as ready for review March 18, 2024 11:15
@neelasha23
Copy link
Contributor Author

App deployed here: https://proud-leaf-7750.ploomberapp.io/app
@edublancas

@edublancas
Copy link
Contributor

some feedback: I broke it but I'm unsure why

image

second attempt:

image

image

third time:

image

image


please verify the overall logic. I'm guessing the customer ID and order ID are validated? but if so, it should print a message saying they're invalid

If I need to put a specific customerID /orderID let me know

@neelasha23
Copy link
Contributor Author

I'm not able to reproduce this error.

Screenshot 2024-03-21 at 6 50 29 PM Screenshot 2024-03-21 at 6 57 29 PM

I can't understand what I'm missing. Do you have the orders.csv file downloaded? Have mentioned in the README

@edublancas

@edublancas
Copy link
Contributor

I used the app that you deployed to test, but it's gone (I guess it was deleted because you uploaded to your account)

use the pro account we're sharing so the apps are not deleted

@neelasha23
Copy link
Contributor Author

neelasha23 commented Mar 21, 2024

Have fixed the bug. It was coming up because OpenAI was responding with a different JSON format after multiple invalid requests.

Screenshot 2024-03-21 at 10 29 42 PM

Latest app deployed here: https://throbbing-pond-7869.ploomberapp.io/app

You can find the valid OrderIDs and customeIDs here: https://archive.ics.uci.edu/dataset/352/online+retail

@edublancas

@edublancas
Copy link
Contributor

looks good, just two things to simplify the experience:

  1. set a default customer ID so users don't have to put it
  2. explain why you have a today's date field
  3. add some explanation of the overall functionality in the left bar: use the default customer ID and "today's date" as a an example to explain what to expect. e.g. "customer with ID {X} has orders {Y}, {Z}, with the default today's date {XYZ}, you can cancel {Y} but not {Z} because Z is >14 days old. Try modifying the date to {ABC} so you can see that you can now cancel {Z}

@neelasha23
Copy link
Contributor Author

@edublancas
Copy link
Contributor

edublancas commented Mar 22, 2024

there's a lot of unnecessary details in the text please trim it. some observations

  • don't put the full URL, you can add the link on top of some text: like this
  • shorten sentences: "Input a valid CustomerID. An user is only allowed to cancel their own orders. Default CustomerID is 15574." can just be "Input CustomerID, default provided"

this text is hard to read:

Let's see an example: Customer ID 15574 has placed orders 556878 (15.6.2011), 539215 (16.12.2010) and 536796 (2.12.2010).
Since the default today's is 20.6.2011 it is possible to cancel order 556878, but not the rest of the orders since they are more than 14 days old.
In order to cancel order 539215 change today's date to some relevant date that is not more than 14 days from 16.12.2010 like 18.12.2010. Similarly for order ID 536796.
  • the date format doesn't match the date field
  • you need to do a lot of re-reading to understand what works and what doesn't. a simple format can be

Only orders in the past 14 days can be canceled. CustomerID 15574 has the following (using 2011-06-20 as today's date):

  1. 556878 (X days old, you can cancel this one)
  2. 539215 (Y days old, you cannot cancel)
  3. 536796 (Z days old, you cannot cancel)

To cancel 2), set X as the date. To cancel 3) try setting Y as the date


please be more careful of these details, when users open an example, they won't spend much time on it if they don't understand it. we have to ensure to communicate a clear message as fast as we can

@neelasha23
Copy link
Contributor Author

Updated description
New app deployed: https://black-poetry-5215.ploomberapp.io/app
@edublancas

@edublancas edublancas merged commit 125a8f7 into main Mar 23, 2024
1 check passed
@edublancas edublancas deleted the customer_chat branch March 23, 2024 17:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

customer chatbot v2
2 participants