help — cat readme.md

How to use Paco's insurance chatbot

This is an internal learning tool for coworkers and people with little or no insurance background — developers, architects, testers, project managers, anyone who keeps running into unfamiliar insurance terms. Ask about an insurance term or concept the way you would ask me, and it will explain it, give you an example, and can even quiz you on what you have learned.

DISCLAIMER: It's not a customer-facing or policyholder-facing bot. It has no account access, no claims lookup, no policy data — it only talks about the glossary behind it. Please don't paste real customer or policy information into it while testing.

Start chatting →
help — ls commands/

💬 What you can ask

  • List all terms in a category good place to start Not sure what to ask yet? Browse everything in one line of business at once, then ask about whatever catches your eye.
    show me all Auto insurance terms list terms under Life
  • Ask for a definition The core feature — ask what a term means, in plain conversational phrasing.
    what's a deductible? explain reinsurance what does ACV mean?
  • Ask for an example Works as a follow-up too — you don't need to repeat the term name, it remembers what you were just talking about.
    give me an example use it in a sentence
  • Compare two terms Also works as a follow-up, comparing against whatever you last discussed.
    what's the difference between ACV and replacement cost? how's that different from replacement cost?
  • Browse categories See the lines of business and topics the glossary is organized into.
    what categories are there? what topics exist?
  • List the risks a line of business covers
    what risks does auto insurance cover? common risks under Property
  • Quiz mode Get quizzed on terms, optionally scoped to one category, with a running score.
    quiz me test me on Auto terms
  • The conversational basics
    hi help bye
help — tips.txt

💡 Tips for getting good answers

  • Phrase things as a question or request — a bare term with nothing around it (just typing "ACV") won't be recognized on its own.
  • If the bot isn't sure which term you mean, it'll ask "did you mean X or Y?" — just reply with the term name.
  • Follow-ups don't need the term repeated — "give me an example" or "how's that different from Y" both refer back to whatever you last asked about.
  • Say you're new to insurance at the start of the session, and category/risk browsing will show you Basic terms before Technical ones.
  • Typos are tolerated for single-term lookups (fuzzy matching kicks in), but are less reliable when comparing two terms at once — see limitations below.
help — cat limitations.txt

⚠️ Limitations — please read before testing

This is an basic, early, limited test build. Running into these limitations isn't a sign something is broken — it's exactly the kind of thing worth flagging back.

  • It matches phrasing, it doesn't truly understand language. Recognition is rule-based (pattern matching + a glossary lookup), not an LLM — it only recognizes phrasing it's been explicitly taught. Genuinely novel wording may get a "not sure what you mean" reply even if a human would understand it fine. That's useful feedback — note down what you typed.
  • The glossary itself is hand-compiled, not an official or verified source. I started the glossary of termsfrom public web content and has been reshaped and expanded by hand. It can contain factual errors or awkward phrasing — treat answers as a starting point for learning vocabulary, not as authoritative.
  • Comparing two terms is weaker when one of them is misspelled. "compare ACV and workres comp" may only pick up the correctly-spelled term. Comparing correctly-spelled terms, or comparing against the term you were just discussing, both work reliably.
  • Categories and difficulty ratings are rough automatic guesses Not reviewed by an insurance expert, only me with my insurance knowledge — good enough to browse by, not authoritative.
  • The first message after a period of inactivity can be slow. The backend runs on a free-tier server that spins down when idle and takes a few seconds to wake back up.

Testing this? Anything that gets a wrong or confusing answer — or a message you'd have expected it to understand — please report back to me. That is the purpose...