Integration
Zendesk support analysis and reviewed macro export
ReplyPilot uses Zendesk ticket changes to discover new comments, then analyzes requester-authored public messages rather than treating every ticket update as new demand. Reviewed content can return to Zendesk as an updated macro or a private internal note.
Updated July 21, 2026 · 6 min read
What is imported
The integration reads incremental ticket changes and then retrieves comment streams. Customer-authored public comments are normalized as support messages. Agent replies and private internal notes are excluded from demand analysis.
- 7, 30, or 90-day initial history
- Optional tag isolation for a pilot
- Stable ticket and comment identifiers
- Recurring cursor-based synchronization
How duplicates are prevented
A ticket may change many times after the original customer message. ReplyPilot deduplicates at comment level, so agent activity, a repeated sync, or ReplyPilot's own private-note write-back does not inflate customer-demand counts.
What can be written back
Approved macro assets can create a Zendesk comment-value macro. Later exports update the same macro through its stored external identifier. Approved green or yellow drafts can be written as private notes for an agent; the integration does not automatically send public replies.
- Create and update content macros
- Private internal-note handoff
- Duplicate write-back protection
- No automatic refunds, status changes, or billing actions
Required configuration
A workspace provides its Zendesk subdomain, account email, and API token. Production credentials should be encrypted at rest and access should remain scoped to the owning workspace.