Fast Start
What you will have in minutes
A locally running, ECZ-ID-backed agent scaffold with resolver-verifiable identity hooks, a credential manifest, and Resolver verification ready to run.
What you do first — in order
What comes back from TrustOps
- Agent ECZ-ID(s)
- Credential manifest (JSON, discovery only)
- API keys issued in TrustOps
Success looks like
Resolver returns a resolver-verifiable state for your Agent ECZ-ID. You can share it with any party without an account.
1What This Kit Builds
An identity-aware support intake agent that handles inbound requests, triages tickets, routes to resolution paths, and tracks SLAs. Every interaction is resolver-verifiable, making support operations commercially legible and auditable.
2Who It Is For
Customer success teams, support engineers, and developers building automated support workflows. Ideal for organisations where support interactions must be identity-verified for compliance, quality assurance, or enterprise requirements.
3Why ECZ-ID Matters Here
Support interactions often involve sensitive data and critical decisions. ECZ-ID ensures every support action carries resolver-verifiable identity, enabling customers to verify they are interacting with legitimate support agents and enabling organisations to maintain auditable records.
4Architecture
Intake Classifier
Classifies inbound requests by type, urgency, and routing requirements with identity context.
Identity-Aware Router
Routes requests to appropriate resolution paths based on resolver-verifiable identity and permissions.
SLA Tracker
Monitors service-level agreements with identity-anchored timestamps and status updates.
Escalation Manager
Manages escalation workflows with resolver-verifiable identity at every handoff point.
Satisfaction Engine
Measures and tracks customer satisfaction with identity-linked interaction records.
Trust Context Logger
Logs every support interaction with resolver-verifiable identity metadata for audit readiness.
5Build Steps Overview
Trust Map
Required Passports
Recommended Passports
Relevant Packages
What Each Enables
6TrustOps Credentialing Checkpoint
TrustOps Credentialing Checkpoint
Pause here to acquire your required ECZ-ID trust objects
This is a designed pause point in your build process. Before continuing, you need to acquire the required ECZ-ID passports and credentials from TrustOps. This midpoint credentialing approach ensures your agent is built with resolver-verifiable identity from the start—not bolted on after the fact.
Required Passports
- ECZ-ID Business Passport
- Agent Credential
Recommended Passports
- API Passport
Relevant Packages
What You Must Acquire in TrustOps
What You Bring Back from TrustOps
9Return and Complete Integration
With your TrustOps credentials in hand, return here to complete the final build steps.
10Verify Through Resolver
Verify agent identity
Query the support agent’s ECZ-ID through Resolver.
Verify interaction records
Trace any support interaction back to resolver-verifiable identity through Resolver.
Check SLA attestations
Verify SLA compliance records through Resolver.
Audit routing decisions
Verify that routing decisions carried correct identity context.
11Deploy Into Your Environment
ECZ-ID-backed agents are portable. Your resolver-verifiable identity travels with your agent regardless of deployment target after TrustOps and Resolver checks. No vendor lock-in.
12Limits & Non-Claims
- This kit does not provision credentials. All credentialing happens through TrustOps.
- This kit does not replace your support platform. It integrates with existing systems.
- SLA enforcement depends on correct configuration of tracking parameters.
- Customer identity verification is separate from agent identity verification.
- Satisfaction metrics are tracked but not automatically acted upon.
Ready to Build This Agent?
Start with the build steps above, credential through TrustOps, and deploy your resolver-verifiable agent anywhere.