What should we put in Atlas?

Start with documents that decide money and promises: returns and refunds policy, warranty eligibility, shipping SLAs, regional variants, and internal escalation SOPs. If it is written down and used to answer customers, it belongs in Atlas.

How does Atlas connect to Core?

When Core reasons across a request, investigation steps call Atlas for the relevant clause. Atlas returns an answer with citations — document and section — that Composer can attach to the draft. It is a step in the pipeline, not a separate chat window.

Yes. Every Atlas answer traces to a source: document name, section, and match confidence. Your team — and the customer — can see where the policy came from.

Is Atlas secure for sensitive documents?

Yes. Atlas inherits PreSorted enterprise controls: encryption, role-based access, regional residency options, and documents that are never used to train models.

Platform / Core PreSorted Atlas Hub

PreSorted Atlas

Your policies, searchable and citable - wired into every reply.

PreSorted Atlas is the knowledge layer. Returns rules, warranty terms, shipping SLAs, and internal SOPs - grounded in your documents, invoked when Core needs an answer. Not when someone remembers where the PDF lives.

See PreSorted Atlas with Core Book a demo

PreSorted Atlas lookup Warranty eligibility · LaserJet M110

2 sources · cited

1 Query Warranty Policy Coverage Check LaserJet M110

2 Sources

Warranty Terms 2025.pdf §3.2 · Coverage period

"Hardware defects are covered for 24 months from purchase date…"

97 % match

Returns & Claims SOP.docx §1.4 · Required documents

"Claims require proof of purchase (invoice or order confirmation)…"

92 % match

Answer

Covered. 24-month warranty applies. Proof of purchase required.

View Sources Copy Answer Attach to Draft

Why PreSorted Atlas Exists

Models guess. Customers expect you to know.

These questions decide refunds, replacements, and legal exposure - they can't be answered from vibes.

? "Are we still in warranty?"

? "Do you refund shipping on defects?"

? "What's the policy for B2B vs consumer?"

Generic AI Improvises a plausible-sounding answer - and creates a promise you now have to honor.

PreSorted Atlas Retrieves, cites, and constrains - so drafts and actions align with what your company actually published.

How PreSorted Atlas Works

RAG that shows its work.

Four steps from your documents to a cited answer inside the pipeline.

Ingest

Policies, product docs, FAQs, and regional variants go into your org library — versioned and permissioned.

Search & ask

Semantic search plus structured policy queries — policy_type , intent — find the right clause, not just similar words.

Cite

Answers return sources your team — and the customer — can trust. Every claim traces to a document and section.

Invoke in playbooks

Investigation steps call PreSorted Atlas whenever a pattern says "check policy" — automatically, on every matching email.

PreSorted Atlas isn't a separate chat window. It's a step in the pipeline — the Investigator asks PreSorted Atlas; the Composer uses the result in the draft.

PreSorted Atlas + Core

Policy in the middle of the flow, not an afterthought.

The same email, with and without a knowledge layer behind it.

Without PreSorted Atlas

With PreSorted Atlas

✕ Agent paraphrases "standard returns policy"

✓ Agent quotes eligibility with citation

✕ Refund proposed on gut feel

✓ Refund proposed when PreSorted Atlas policy allows

✕ Escalations from wrong promises

✓ Fewer reversals — policy checked before draft

Defined Actions can reference PreSorted Atlas explicitly:


							Issue refund when PreSorted Atlas policy allows.

What to Put in PreSorted Atlas

If it's written down, it should be findable.

Start with the documents that decide money and promises - then expand.

Returns & refunds policy Eligibility windows, condition rules, refund methods

Warranty and product eligibility Coverage periods, exclusions, claim requirements

Shipping, delivery, and lost-parcel rules SLAs, carrier policies, replacement thresholds

Regional / channel variants DTC vs wholesale, per-country consumer law differences

Internal escalation SOPs Shapes draft tone and routing - never customer-facing

RAG Settings

Retrieval is tuned per org - not one-size-fits-all.

Chunk size tuned per doc type

Search depth configurable

Confidence threshold per policy type

Citation format doc + section

Example

"Is my LaserJet still covered?"

One warranty question, answered from your documents - with the paper trail attached.

LaserJet warranty Hi, my LaserJet M110 stopped printing. I bought it last May - is it still under warranty, and what do you need from me?

1 Read Warranty Inquiry LaserJet M110

2 Reason Purchase Context Atlas Policy § 3.2 24-month cover

3 Draft "Hi, your LaserJet M110 is still under the 24-month warranty. Please send proof of purchase and we'll open a claim." Warranty Terms §3.2

4 Propose Update CRM Notes Open Warranty Claim

Approve

Cited from your docs. You make the decision.

Review Trace Edit Draft Approve & Send Escalate

See E-commerce warranty case

FAQ

Atlas questions, answered.

How knowledge, citations, and Core work together.

PreSorted Atlas is the knowledge layer. It turns policies, warranties, SOPs, and product docs into a searchable, citable library that Core queries during Reason — so drafts and actions are grounded in what your company actually published.