How to make a chatbot answer from your own content
Use your own practice account and test data. Record an observation for each completion claim. You can print this worksheet or keep your answers in your own notes; this page does not submit them.
1. Build a chatbot that knows the café’s information
Open the local practice and try the opening-hours and phone-number questions. For each, report whether a note was found and what the page showed. This is a scripted exercise; do not report it as a live AI test.
Open the ready practice link below; no download or API key is needed.
Use both prepared questions and compare Selected evidence with Scripted response.
Review your work
Distinguishes a matching hours note from an absent phone fact.
Reports the local scripted result without claiming an AI request.
2. Start the supplied project with your coding assistant
Run the supplied project and try the opening-hours question. Report the local URL, whether a real reply arrived and which source opened. If you cannot run it yet, name the exact missing prerequisite or error.
Download the complete workshop, not a single source file.
Use the setup request above and the private environment names from the supplied file.
Open the actual local application and follow the reply’s source link.
Review your work
Distinguishes the application URL and a real reply from a file preview.
Records the source or an honest blocked/not-run result without exposing secrets.
3. Test the answer by opening its source
The answer says “Open every Sunday until 17:00” and links to a note saying Sunday is closed. Is that reply acceptable? Name the mismatch and the check you would ask your coding assistant to make.
Compare the exact claim with the opened source.
Describe the correction you need; you do not have to write the server code.
Review your work
Rejects the Sunday-opening claim despite its real source link.
Asks for a check that the answer follows the selected source, not a cosmetic change.
4. Add one café rule and test the change
Add the terrace-only dog rule with your coding assistant. Synchronize and test the changed project. Submit the new note and a short expected/observed record, clearly naming local scripted practice, live AI or not run.
Change records.json; let the helper update the generated copies.
Restart and reload, then test a supported dog question and a question that the notes cannot answer.
Check that the reply never broadens terrace-only into permission indoors.
Review your work
Keeps the dog policy precise and provides a source that actually contains it.
Separates observed results from predictions, missing matches and service failures.