AWS reference architectureException resolution
A AWS reference architecture for exception resolution in Logistics. Triggered by customer or partner requests status, Padiso orchestrates 3 specialist agents on Amazon Bedrock AgentCore, reaching transportation management system (tms) and your tools through the Model Context Protocol, with budgets, approvals and an audit trail throughout.
AWSRuntime: Amazon Bedrock AgentCoreTrigger
Customer or partner requests status
Logistics
Orchestration
Padiso Orchestrator
goals · tasks · heartbeat
Governance
budgets · approvals · audit
Runtime & agents
Agent runtime
Amazon Bedrock AgentCore
Tracking agent
agent
Exception agent
agent
Comms agent
agent
Integrations · MCP
MCP gateway
Your systems
Transportation Management System (TMS)
Customer CRM
Carrier feeds
How the data flows
Trigger: Customer or partner requests status
- 1
Comms agent assembles the latest status from the TMS and carrier feeds
- 2
It sends a proactive update across the right channel
- 3
Logs the interaction against the shipment
- 4
Disputes or claims are routed to a human
Agent team
- Tracking agent
- Exception agent
- Comms agent
Integrations
Reached through the Model Context Protocol, scoped and governed.
Runtime & data
Amazon Bedrock AgentCore
Transportation Management System (TMS)
Customer CRM
Carrier feeds
Security & operational considerations
- Single source of truth from the TMS
- Rate-limited outbound comms
- Escalation on disputes
AWS deployment
Deployed in your AWS account on Bedrock AgentCore, with IAM scoping, PrivateLink to your VPC, and CloudTrail/CloudWatch for audit and observability.
Run this blueprint anywhere
More Logistics blueprints
Run your business on agents.
Start free, or talk to us about putting an agent workforce to work across your operations.