What is Read → Reason → Execute?

Every email moves through the same visible pipeline. Read classifies intent and risk. Reason looks up customers, orders, and policy across connected systems. Execute drafts the reply and proposes actions for human approval — never silent autopilot on high-risk work.

What happens when Core isn't confident?

Every request carries a confidence score. Below your threshold, Core escalates with its investigation attached — it never guesses on refunds, legal language, or high-value customers.

What are Email Patterns and Defined Actions?

Email Patterns are playbooks for known scenarios — returns, warranty, tracking, chargebacks — each with its own lookups and instructions. Defined Actions are the writes to your systems (refunds, tickets, CRM updates) that stay explicit and gated behind approval.

Does Core replace my team?

It replaces the preparation — the 30 minutes of searching before each reply — not the judgment. Your team keeps the decision; Core removes the work before the work.

Platform / Core PreSorted Atlas Hub

PreSorted Core

Every email gets a plan.
You stay in charge .

Core is where inbound mail becomes structured work: pattern match, system lookups, draft reply, and proposed actions - all in a workbench your team actually trusts.

See Core in action Book a demo

You sent me the wrong thing

I ordered one item and received something completely different. I can send a photo. Please fix this — I need the correct product or a return arranged.

Medium Risk

1 Read

Order ORD-91034 Wrong item Photo offered Fulfillment error

2 Reason

SKU mismatch confirmed Second customer identified 3 units available Prepaid return label ready

3 Draft

“Your correct item is in stock and will be dispatched the same day we receive your return scan - or sooner if you'd like us to send it now.”

Option: ship replacement now Option: wait for return scan

4 Propose

Flagged replacement dispatch Zendesk · fulfillment error QA Contact second customer

Approve

Two customers fixed, one warehouse error tracked.

Review Trace Edit Draft Approve & Send Escalate

What's PreSorted Core Is

The operating layer for inbound email.

Core is not another shared inbox with labels. It's an agentic pipeline with rules you define.

Email Patterns

Playbooks for known scenarios — returns, tracking, billing, warranty — each with its own lookups, instructions, and actions.

Global Pattern

When nothing else matches, Global still runs — bounded to your enabled systems. No silent failures.

Defined Actions

Writes to your systems — refunds, tickets, CRM updates — are always explicit, always gated behind approval.

Operating Policy

Ask strategy, refund caps, escalation triggers, and confidence gates — the rules every pattern runs under.

Your team works from one place : the message, the investigation trace, the draft, and the proposed actions - side by side.

How It Works

Five steps. Zero preparation.

Every inbound email moves through the same governed pipeline, from arrival to executed action.

Read

Intent, urgency, and risk on arrival.

Every inbound email is analysed the moment it arrives. Intent, urgency, risk, and business context are identified before anyone opens the thread.

Reason

Gather everything needed to resolve.

The agent gathers CRM records, orders, support history, knowledge articles, policies, and previous conversations. If something is missing, it asks the customer.

Draft

Response and actions, ready to review.

A complete response is prepared, along with the actions required. Create a ticket. Process a refund. Update the CRM. Everything is ready for review, not executed automatically.

Approve

You keep the decision.

Your team reviews the reasoning, evidence, and proposed actions. Edit if needed. Approve with confidence. Nothing happens outside your governance.

Act

Execute across your systems.

Once approved, PreSorted executes the actions across your business systems with full policy enforcement, auditability, and complete traceability.

Read → Reason → Execute

Three modes. One transparent flow.

Every email moves through the same visible pipeline - you can inspect any step at any time.

Stage 1

Read

Understand the email: sender, subject, intent, sentiment, and risk. Match it to the right pattern — or fall back to Global.

Reader · READ

Classified as return request

94% confidence

Stage 2

Reason

Run your playbook: look up the customer, pull orders, and check policy. Gather missing data before you draft — not after.

Salesforce Contact

Shopify Orders

Atlas warranty policy

Stage 3

Execute

Compose a draft reply and propose Defined Actions for approval. High-risk or low-confidence cases escalate — never autopilot.

Propose Shopify refund

Propose Zendesk ticket

Act on Email

Draft Mode

We propose. You approve.

Core defaults to draft. Auto-send exists only where you explicitly allow it - with confidence thresholds and approval gates you configure.

Edit the reply before it goes out

See which systems were queried and what came back

Approve, reject, or modify each proposed action

Escalation triggers for legal, fraud, or angry high-value customers

“

The AI did the legwork . My team made the call .

The Core operating principle

Patterns That Scale

Teach the system once. Handle the next hundred the same way.

Two kinds of patterns cover everything that lands in your inbox - the known and the unknown.

Email Patterns

Named playbooks for recurring mail. Each pattern carries its own lookup steps, narrative instructions, and defined actions.

“Where Is My Order?” “Wrong Item Received” “Invoice Mismatch” “Warranty Claim”

Global Pattern

The safety net. When no pattern matches, Global still runs a bounded investigation and lands on the workbench.

Never silent failure - every email surfaces with a trace

Never uncontrolled automation - bounded to your enabled systems

Always reviewable - unmatched mail becomes tomorrow's new pattern

Example Walkthrough

One email. Full trace. One approval.

Here's exactly what Core does with a real request - and where you come in.

Return request

I know it's past 30 days, but the zip broke after one use. This feels like a manufacturing defect — can I still return or exchange it?

Medium Risk

1 Read

Order ORD-85521 6 weeks old Zip broke after one use ACL trigger

2 Reason

Outside 30-day window Atlas: ACL override Defect covered by law No supervisor escalation

3 Draft

“Under Australian Consumer Law, you are entitled to a remedy regardless of our standard 30-day return window.”

Option: replacement Option: refund

4 Propose

Prepaid return label attached Replacement or refund · choice logged

Approve

A 2-hour supervisor escalation becomes 30 seconds, legally correct.

Review Trace Edit Draft Approve & Send Escalate

FAQ

Core questions, answered.

How draft mode, patterns, and approval work in practice.

No by default. Core runs in draft mode: it prepares the reply and Defined Actions, then waits for your team. Auto-send only happens for patterns you explicitly allow, with confidence thresholds and approval gates you configure.

PreSorted Core

Core is where email stops being guesswork .

Give every inbound message a plan, a trace, and an approval gate - starting this week.

Talk to sales Explore Platform

Enterprise ready · SOC 2 · 50+ connectors

Every email gets a plan. You stay in charge .

The operating layer for inbound email.

Email Patterns

Global Pattern

Defined Actions

Operating Policy

Five steps. Zero preparation.

Read

Reason

Draft

Approve

Act

Three modes. One transparent flow.

Read

Reason

Execute

We propose. You approve.

Teach the system once. Handle the next hundred the same way.

Email Patterns

Global Pattern

One email. Full trace. One approval.

Core questions, answered.

Can Core send emails without approval?

What is Read → Reason → Execute?

What happens when Core isn't confident?

What are Email Patterns and Defined Actions?

Does Core replace my team?

Core is where email stops being guesswork .

Every email gets a plan.
You stay in charge .