Skip to main content
This playbook is for systems that keep source content in a CMS, help center, product catalog, or internal knowledge tool and need to publish approved content into Uppzy. Use this for content that is safe to answer from:
  • Public help center articles
  • Approved policy pages
  • Support macros
  • FAQ entries
  • Product care or setup guides
Do not sync secrets, private credentials, raw payment data, or private customer records.

Flow

  1. Select approved source records
  2. Normalize each record into a document payload
  3. Send text or Q&A documents to Uppzy
  4. Store source IDs and returned document IDs in your own sync log
  5. Run a smoke chat after each content batch
  6. Review statistics and feedback after rollout

Choose the document type

Use text documents when the source is article-like content.
Use Q&A documents when the source is a direct question and answer.

CMS sync example

This example maps CMS records to text documents. It assumes your CMS client returns only approved records.

FAQ sync example

Use Q&A documents for short direct answers.

Batch safety

Keep content sync predictable:
  • Sync a small first batch before a full import
  • Keep a source-to-document mapping in your own database
  • Avoid syncing draft, archived, or unapproved records
  • Normalize HTML into readable text before sending it
  • Remove tracking snippets, raw IDs, hidden content, and unrelated markup
  • Run smoke questions after each batch

Smoke test after sync

Run a known question after a content sync and check whether the answer uses the expected content.

Rollout checklist

  • Sync only approved customer-facing content
  • Start with text and Q&A documents before large file batches
  • Keep source IDs in your own sync log
  • Run a smoke chat after each batch
  • Review low-confidence answers and update the source content first