What's the context library?

The context library is a per-page knowledge base for the facts your replies must never get wrong — hours, shipping thresholds, return windows, pricing, product specifics. Reply200 reads it before answering, so it states what's true instead of guessing.

What goes in it

Short, factual statements — one per entry (up to 500 characters each). Think of what a new support hire would need on day one:

• "Free shipping on orders over $75; 2pm EST cutoff for same-day handoff."
• "Returns: 30 days from delivery, original packaging, refunds in 5–7 days."
• "We don't price-match competitors; the loyalty discount kicks in at the 5th purchase."

Each entry shows a status — Ready once it's live, Processing while we index it, or Failed if it needs a fix — plus when it was last edited. Change or remove any entry anytime. A single page holds up to 120,000 characters total, so there's room for a real knowledge base.

Context vs. CTAs

Two different jobs, two different places:

• Context — facts the reply should know (this library)
• CTAs — actions the reply should take (route to your site, suggest a follow…)

"Free shipping over $75" is context. "Send pricing questions to the pricing page" is a CTA.

Share across pages

Build it once for a page, or share one library across every page in the same Business Manager — so sister pages answer policy questions identically without re-entering anything.

How it's used

When we write a reply, your context entries are part of what we pull from — alongside the post itself and your page's voice. If a comment touches something in your library, the answer reflects it. If nothing applies, we fall back to the post and skip rather than guess.