Local / Desktop reference architectureTicket triage and routing
A Local / Desktop reference architecture for ticket triage and routing in Customer Support. Triggered by inbound ticket created, Padiso orchestrates 3 specialist agents on Claude Code + Ollama, on your machines, reaching helpdesk (zendesk / intercom) and your tools through the Model Context Protocol, with budgets, approvals and an audit trail throughout.
Local / DesktopRuntime: Claude Code + Ollama, on your machinesTrigger
Inbound ticket created
Customer Support
Orchestration
Padiso Orchestrator
goals · tasks · heartbeat
Governance
budgets · approvals · audit
Runtime & agents
Agent runtime
Claude Code + Ollama, on your machines
Triage agent
agent
Resolution agent
agent
Escalation agent
agent
Integrations · MCP
MCP gateway
Your systems
Helpdesk (Zendesk / Intercom)
CRM
Knowledge base
How the data flows
Trigger: Inbound ticket created
- 1
Triage agent classifies, prioritizes and routes the ticket with account context
- 2
Resolution agent answers common issues and runs routine actions
- 3
Hard cases escalate with a full context bundle and suggested next steps
- 4
Sensitive actions (refunds, account changes) require approval
Agent team
- Triage agent
- Resolution agent
- Escalation agent
Integrations
Reached through the Model Context Protocol, scoped and governed.
Runtime & data
Claude Code + Ollama, on your machines
Helpdesk (Zendesk / Intercom)
CRM
Knowledge base
Security & operational considerations
- PII redaction in transcripts and logs
- Approvals on refunds and account changes
- Escalation SLAs enforced
Local / Desktop deployment
Self-hosted: agents and models run on your machines, so regulated data and credentials never leave your network. Best when data residency is non-negotiable.
Run this blueprint anywhere
More Customer Support blueprints
Run your business on agents.
Start free, or talk to us about putting an agent workforce to work across your operations.