Extend conversation translation to API/webhook reply channels

Please give a quick overview of your product feature request or feedback and note who in your organization is affected by this issue (2-3 sentences)

We're requesting that conversation translation be extended to support API/webhook-driven reply channels, along with a send-time visibility flag for agents when a reply bypasses translation. This affects our support agents directly, and indirectly our customers, who may receive replies in the wrong language without the agent realizing it.

What problem do you see this solving? (1-2 sentences)

It would ensure clients receive translated replies regardless of the channel used to send them, with a visible fallback signal for agents in cases where translation still can't be applied.

When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business? (3-4 sentences)

Replies sent through our MS Teams integration via API have repeatedly reached clients untranslated, in English, despite being logged internally as translated. This has recurred across multiple tickets in different languages over the past month. It causes client confusion, repeated back-and-forth asking for their language, and delays in resolving time-sensitive cases (e.g. fund transfers, account verification).

Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)

Yes, agents now manually translate replies before sending, since our brand/group works exclusively via API and can't use the standard Agent Workspace compose flow where translation applies.

What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)

Ideally, conversation translation would apply automatically to replies sent via API/webhook channels just as it does in Agent Workspace; as a fallback, a visible flag at send time when translation can't apply, so agents can catch and correct it manually.

Related ticket: https://support.zendesk.com/hc/en-us/requests/15023891