Scan-specific knowledge

​

The pattern

1. Link shared knowledge to the chatbot — breakfast hours, wifi, checkout, house rules.
2. Link item-specific knowledge to what gets scanned — each room’s TV manual on that room’s QR code. If many rooms share a TV model, put the rooms in a QR group and link the manual to the group once.
3. Keep item-specific articles off the chatbot. If every manual is also linked to the chatbot, every guest can reach every manual and the ambiguity comes back.

​

Example

# Shared knowledge on the chatbot
curl -X PATCH https://api.awardee.com/v1/chatbots/8f3a9d2e-1b4c-4f5d-9e8a-7c3b2a1d0f9e \
  -H "Authorization: Bearer aw_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "category_ids": ["c3d4e5f6-a7b8-4c9d-0e1f-2a3b4c5d6e7f"] }'

# Room 12's TV manual on room 12's QR code
curl -X PATCH https://api.awardee.com/v1/qr-codes/room-12 \
  -H "Authorization: Bearer aw_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "article_ids": ["5e6f7a8b-9c0d-4e1f-a2b3-c4d5e6f7a8b9"] }'

​

Rules

• It only applies to chatbot destinations. Linked knowledge is used when the scanned item sends visitors to a chatbot — for a QR code in a group, whichever destination wins (the group’s, if set). A QR code pointing at a page or URL keeps its links, but they have no effect until it points at a chatbot.
• Live items only. Inactive QR codes, products and objects contribute nothing.
• Same rules as chatbot knowledge. Only published articles are used, internal articles are never used, and every linked id must belong to your organization (422 unprocessable otherwise).
• Replace-only writes. Send the full desired article_ids / category_ids set; omit a field to leave it untouched; [] detaches everything.
• Webhooks. qr_code.updated, qr_group.updated, product.updated and object.updated payloads include both arrays, and fire even when a PATCH only changes them.