Use case
Customer support replies that wait for a person
For a small support desk that already lives in Zendesk or Intercom. The crew gathers the ticket. The public reply does not go out until someone approves it.
The problem
The first read of a ticket is often the same: status, requester, and what they already said. The risky part is the reply the customer receives. That should stay behind an approval.
The workflow
On Zendesk, search tickets and read one thread. A model step drafts the reply from that thread and your instructions. The public reply is an external action, so the run waits. An internal note is not the same as that public reply.
Intercom can search conversations, read one, and reply. Closing or assigning a conversation is a separate action. Use the approval step on anything the customer will see.
Limits
These connectors are in the product and were tested with mocked responses. They are not a published live certification against a production Zendesk or Intercom tenant. The crew only sees the help desk the workspace connects.
Questions
Will customers get an email from the draft?
A Zendesk public reply is what the requester receives. That step waits. Reading a ticket does not email them.
Is there a dedicated Zendesk page?
Not as a separate marketing URL. The actions are search, read, public reply, internal note, and update. This use case is the supported workflow. A near-duplicate integration page would not add a different job.