Home›Agents›Zendesk AI Agents

AgentenCode evidence profileService & sales

✓ Editorially reviewedChecked: September 30, 2026

Agent profile · Service & sales

Zendesk AI Agents

Zendesk AI Agents is classified by AgentenCode as a customer service agents from Zendesk. It belongs to the Customer Service category. This English profile does not maintain a separate factual record: it renders the same underlying evidence, trust and history data as the German profile.

ZendeskService & salesOrganizations

View profile ↓Check sources ↓

Service & saleseditorial classification

Zendeskprovider

14 primary sourcessource status

September 30, 2026last verification

AgentenTrust 2.0 · EU & governance evidence

Trust, privacy and control evidence for Zendesk AI Agents

Direct answer: AgentenCode currently documents 12 of 36 normalized trust controls for this profile. Missing fields remain Unknown and are never automatically interpreted as “no”.

EU AI ActEvidence context only. AgentenCode does not infer legal applicability or compliance from individual product controls.

GDPRPrivacy and security signals are documented field by field. Data residency alone is not a compliance or transfer assessment.

Privacy contextPrivacy & data2 of 8 documentedResidency, training, retention, DPA, subprocessors and processing scope.

Security contextSecurity & access8 of 10 documentedEncryption, SSO, SCIM, RBAC, roles and credential handling.

Human controlHuman control0 of 10 documentedApproval, oversight, permissions and stop or rollback controls.

TraceabilityAudit & traceability2 of 8 documentedAudit logs, APIs, SIEM, observability, tracing and activity history.

Important: these numbers show evidence coverage, not a product rating. 0 of 10 means that no field-level public evidence is stored for those ten controls in the current dataset. It does not mean the product lacks those capabilities.

Field-level evidence

Documented controls and values from primary sources.

Documented yesDocumented valueUnknown remains unknown

High confidence

API · Rest

Yes — documented

Zendesk AI Agents expose documented programmatic API endpoints.

Scope: zendesk_ai_agents_api · verified 2026-10-01 · Primary source ↗

High confidence

API · Webhooks

Yes — documented

Zendesk AI Agents support webhook-based event delivery.

Scope: zendesk_ai_agents_chat_and_ticket_api · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Audit logs · API

Yes — documented

Zendesk exposes audit logs programmatically through documented API endpoints.

Scope: zendesk_enterprise_account · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Audit logs · Available

Yes — documented

Zendesk Enterprise provides audit logs.

Scope: zendesk_enterprise_account · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Custom roles

Yes — documented

Zendesk Enterprise supports custom roles.

Scope: zendesk_enterprise · verified 2026-10-01 · Primary source ↗

High confidence

Governance · RBAC

Yes — documented

Zendesk uses role-based permissions to govern product access.

Scope: zendesk_team_member_access · verified 2026-10-01 · Primary source ↗

High confidence

Governance · SCIM

Yes — documented

Zendesk supports SCIM 2.0 provisioning.

Scope: zendesk_user_provisioning · verified 2026-10-01 · Primary source ↗

High confidence

Governance · SSO · Oidc

Yes — documented

Zendesk supports OIDC SSO.

Scope: zendesk_account_access_for_ai_agents_admins_and_users · verified 2026-10-01 · Primary source ↗

High confidence

Governance · SSO · Saml

Yes — documented

Zendesk supports SAML SSO.

Scope: zendesk_account_access_for_ai_agents_admins_and_users · verified 2026-10-01 · Primary source ↗

High confidence

Privacy · Data residency · Available

Yes — documented

Zendesk offers regional data-hosting options for eligible service data.

Scope: zendesk_service_data_including_ai_agent_account_data · verified 2026-10-01 · Primary source ↗

High confidence

Privacy · Data residency · Customer Region Selectable

Yes — documented

Eligible Zendesk customers can select a supported hosting region for covered service data.

Scope: zendesk_data_center_location_add_on · verified 2026-10-01 · Primary source ↗

High confidence

Security · Encryption · At rest

AES-256

Zendesk documents AES-256 encryption at rest for Service Data.

Scope: zendesk_service_data · verified 2026-10-01 · Primary source ↗

High confidence

Security · Encryption · In transit

TLS 1.2+

Zendesk documents TLS 1.2+ encryption in transit.

Scope: zendesk_ui_and_api_communications · verified 2026-10-01 · Primary source ↗

High confidence

Security · Soc2 Type2

Yes — documented

Zendesk documents SOC 2 Type II compliance.

Scope: zendesk_platform · verified 2026-10-01 · Primary source ↗

Evidence-backed overview

What is Zendesk AI Agents?

Product-specific evidence for Zendesk AI Agents

This profile links 14 unique primary sources across the product profile, field-level evidence, trust controls and documented relations. The points below describe this product’s stored evidence rather than generic characteristics of Kundenservice.

Data Residency

Yes · Scope: zendesk_service_data_including_ai_agent_account_data · verified 2026-10-01.

Primary source ↗

Region auswählbar

Yes · Scope: zendesk_data_center_location_add_on · verified 2026-10-01.

Primary source ↗

Verschlüsselung at rest

AES-256 · Scope: zendesk_service_data · verified 2026-10-01.

Primary source ↗

Verschlüsselung in transit

TLS 1.2+ · Scope: zendesk_ui_and_api_communications · verified 2026-10-01.

Primary source ↗

SOC 2 Type 2

Yes · Scope: zendesk_platform · verified 2026-10-01.

Primary source ↗

Audit Log API

Yes · Scope: zendesk_enterprise_account · verified 2026-10-01.

Primary source ↗

AgentenCode treats this page as a reference profile rather than a ranking. Product facts are separated from editorial classification, and the profile is tied to a specific verification date. If a capability is not backed by sufficiently precise public evidence, it remains unknown instead of being inferred from marketing language or from similar products.

2primary sources

14field-level evidence claims

12documented trust controls

2history events

How to read the evidence

The field-level evidence layer records a value, a scope, a confidence level, a verification date and one or more primary sources. Scope matters: an enterprise-only security feature must not be generalized to every plan or deployment surface. The same rule applies to hosting, privacy, audit and protocol claims.

AgentenCode also keeps Unknown distinct from false. A missing claim means the public dataset does not currently contain sufficiently precise evidence for that field. A negative value is used only when a reliable primary source explicitly documents a restriction or non-availability.

Decision context

Provider and category

Zendesk AI Agents is documented under Service & sales and is associated with Zendesk. Category labels help navigation but do not replace product-specific evidence.

Verification status

The public profile is marked editorially reviewed and was last checked on September 30, 2026.

Trust coverage

12 of 36 normalized trust controls currently have field-level public evidence. The remaining controls are not treated as negative findings.

Source-first use

For procurement, security or legal decisions, use the linked primary sources and verify the plan, region and configuration that apply to your organization.

Capabilities, strengths and deployment checks for Zendesk AI Agents

Zendesk AI Agents is classified as Customer Service Agents from Zendesk. The profile’s editorial layer is derived from the stored use cases, strengths and checks below; claims about security, privacy or governance remain separate and require field-level evidence.

Ticket-Automation

This use case is part of the stored profile for Zendesk AI Agents. The related strength is “Direkte Zendesk-Integration”. In a production evaluation, the practical boundary to verify is: Wissensbasis und Aktionen testen.

Messaging

This use case is part of the stored profile for Zendesk AI Agents. The related strength is “Mehrere Servicekanäle”. In a production evaluation, the practical boundary to verify is: Kanalabhängige Funktionen prüfen.

E-Mail-Support

This use case is part of the stored profile for Zendesk AI Agents. The related strength is “Generative Flows”. In a production evaluation, the practical boundary to verify is: Automatisierte Antworten regelmäßig qualitativ auditieren.

Serviceaktionen

This use case is part of the stored profile for Zendesk AI Agents. The related strength is “Handover in bestehende Supportprozesse”. In a production evaluation, the practical boundary to verify is: Wissensbasis und Aktionen testen.

What to verify before adoption

Wissensbasis und Aktionen testen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
Kanalabhängige Funktionen prüfen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
Automatisierte Antworten regelmäßig qualitativ auditieren. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.

Editorial boundary: The use-case and strength descriptions are product-specific editorial context based on the stored profile. Trust, privacy and governance statements are only presented as facts when field-level primary-source evidence exists.

Verified history

The public history layer records only confirmed profile changes and verification events. Monitoring signals are not published as product facts until they have been reviewed.

September 30, 2026 · Verification Update
September 28, 2026 · Schema Upgrade

Official sources

This profile links 14 unique primary sources across the product profile, field-level evidence, trust layer and documented relations. Provider documentation remains authoritative when the product changes between verification cycles.

Frequently asked questions

What is Zendesk AI Agents?

Zendesk AI Agents is listed by AgentenCode as a service & sales agent or agentic product from Zendesk.

How much trust evidence is documented for Zendesk AI Agents?

The current trust layer documents 12 of 36 normalized controls. Missing controls remain unknown rather than being treated as false.

When was this profile last checked?

The current profile verification date is September 30, 2026. The linked primary sources remain authoritative if the product changes between checks.

Method note: AgentenCode does not certify GDPR or EU AI Act compliance. It documents evidence that can support a separate legal, security or procurement assessment.