Skip to content
Module
Module 2 of 6Lesson 1 of 3~10 min

Identify a use case worth an assistant

Many AI assistants disappoint because they tackle a problem that a good FAQ or a guided flow would have solved better. This lesson helps you spot the user problems where an assistant brings real value, and justify that choice to your team before committing to any development.

Lesson objective

By the end of this lesson, you will be able to identify, among several user problems, the ones an AI assistant solves better than an FAQ, a search box or a guided flow, and to justify that choice.

Topics covered

  • AI use case
  • AI assistant
  • product value
  • chatbot vs FAQ
  • AI prioritization

Where it fits

Frame the assistant

Does my product need an assistant, and to do what exactly?

Lessons in this module

  1. Identify a use case worth an assistant (this lesson)
  2. Write the framing brief
  3. Understand the anatomy of an LLM assistant

What you will learn in the course

This lesson is part of the course Build an AI assistant for your product

  • Identify a use case that justifies an AI assistant and write its framing brief (problem, users, allowed actions, out of scope, success criteria).
  • Design the conversational experience: entry point, tone, handling uncertainty, handoff to a human and response format.
  • Choose and justify a knowledge strategy (instructions, injected context, RAG, fine-tuning) and a conversation memory strategy.
  • Specify the assistant's tools and actions (data read, actions written, confirmation, permissions) and choose how to build it.
  • Identify the risks (injection, leaks, excessive actions, costs) and design layered guardrails that go beyond the prompt.
  • Design an evaluation plan with a reference dataset, criteria, grading methods, release thresholds and a regression rule.
  • Define production metrics (product, quality, cost, latency), alert thresholds and the loop from user feedback to the evaluation set.