How Zild Works
Zild turns an incoming event into a governed operational decision: respond, use a tool, create work, or hand off to a person.
Zild turns an incoming event into a governed operational decision: respond, use a tool, create work, or hand off to a person.
Execution flow
- A channel receives a message, call, file, or system event.
- Zild identifies the tenant, app, agent, user, and available context.
- The agent applies instructions, knowledge, permissions, and guardrails.
- The platform decides whether to answer, call a tool, create a task, or escalate.
- The result is recorded for monitoring, quality review, and improvement.
Platform layers
| Layer | Purpose |
|---|---|
| Context | Conversation history, CRM data, documents, transcripts, and approved knowledge. |
| Decision | Agent reasoning limited by instructions, confidence, policy, and permissions. |
| Action | Messages, tool calls, tasks, transfers, CRM updates, or workflow triggers. |
| Evidence | Conversation records, transcripts, evaluations, metrics, and audit history. |
Operational control
The important rule is simple: the AI should act only when it has enough context, evidence, permission, and instruction. Otherwise it should ask for more information, limit the answer, or transfer to a human.