Dave Ebbelaar builds a Python support-ticket flow, inspects category probabilities, and combines category, frustration, and refund questions in one call. He also explains why sending client data to a new provider needs a separate privacy decision, even when the API is easy to use.
Original by Dave EbbelaarClassificationIntermediate16 min 50 secPublished Source reviewed
Before you press play
What you’ll find in the video
Define a Choice with instructions and category criteria, then inspect its probabilities and confidence rather than using only the winning label.
Use a Noul proposition to estimate whether a refund is requested and branch on the numeric answer in Python.
Combine Choice, Score, and Noul questions over one ticket state to obtain category, frustration level, and refund intent in one request.
Worth knowing
Auto-generated English captions reviewed with Gemini. The examples are illustrative, not a labelled accuracy study. The author raises client-data and provider-approval concerns without completing a privacy-policy audit.