Local / Desktop reference architectureSupport triage and resolution
A Local / Desktop reference architecture for support triage and resolution in SaaS & Tech. Triggered by support ticket created, Padiso orchestrates 3 specialist agents on Claude Code + Ollama, on your machines, reaching helpdesk (zendesk) and your tools through the Model Context Protocol, with budgets, approvals and an audit trail throughout.
Local / DesktopRuntime: Claude Code + Ollama, on your machinesTrigger
Support ticket created
SaaS & Tech
Orchestration
Padiso Orchestrator
goals · tasks · heartbeat
Governance
budgets · approvals · audit
Runtime & agents
Agent runtime
Claude Code + Ollama, on your machines
Onboarding agent
agent
Support agent
agent
Lifecycle agent
agent
Integrations · MCP
MCP gateway
Your systems
Helpdesk (Zendesk)
Product API
Knowledge base
How the data flows
Trigger: Support ticket created
- 1
Triage agent classifies and routes the ticket and pulls account context
- 2
Resolution agent answers tier-1 issues and runs routine actions
- 3
Unresolved tickets escalate with a full context bundle
- 4
Account-changing actions require human approval
Agent team
- Onboarding agent
- Support agent
- Lifecycle agent
Integrations
Reached through the Model Context Protocol, scoped and governed.
Runtime & data
Claude Code + Ollama, on your machines
Helpdesk (Zendesk)
Product API
Knowledge base
Security & operational considerations
- PII redaction in logs
- Approvals on refunds and account changes
- Escalation SLA 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 SaaS & Tech blueprints
Run your business on agents.
Start free, or talk to us about putting an agent workforce to work across your operations.