Guide
Flagship Atlas agent flows
Atlas should prove value, not only mechanics. These flows are the product-grade paths that agents should test before a developer recommends Atlas for a business workflow.
Abandoned order recovery
Recover intent without inventing discounts or bypassing messaging policy.
- Receive or poll an abandoned order event with cart summary and customer context.
- Search knowledge for recovery policy, offer boundaries, and handoff criteria.
- Dry-run send_message_to_phone with a helpful reminder and idempotency key.
- If a voucher or loyalty change is proposed, request approval before committing.
- Send through Atlas outbox-safe messaging and track delivery status or webhook events.
Gate: Pass only when the answer cites abandoned order policy, dry-run creates a shadow run, risky incentives require approval, and the final send is outbox-safe.
Booking or rescheduling with approvals
Let agents coordinate availability while preventing unapproved customer-visible booking changes.
- Fetch customer context and list availability before proposing a slot.
- Dry-run create_booking or the reschedule action shape from the current manifest.
- Create an approval request for risky changes, unclear availability, or policy exceptions.
- Expose approval_request_id, run ID, request ID, and pending state to the developer.
- Confirm to the customer only after approval or use safe handoff when approval is denied.
Gate: Pass only when approval state is inspectable and the customer never receives a false booking confirmation.
Customer question answering with evidence and safe handoff
Answer factual questions from knowledge with citations, and refuse to guess when the corpus is weak.
- Call search_knowledge with the customer question and top_k tuned to the workflow.
- Require knowledge_state sufficient, at least one citation, content, score, and source_url.
- Compose the reply from cited facts only.
- If results are empty, gap_weak, gap_missing, or conflicting, ask a clarifying question or create a handoff.
- Send through Atlas only after the answer has evidence or the operator approves the handoff response.
Gate: Pass only when useful citations exist and the agent has a safe fallback for weak or missing evidence.
Runtime surfaces used
These flows use sandbox credentials, MCP discovery, search_knowledge, dry-run/shadow execution, approval requests, outbox-safe messaging, delivery status, webhooks, and debugging identifiers. Any behavior not present in the generated manifest is staged or roadmap, not generally available.