ReplyTurn
Who should reply next in JSM without changing the workflow status?
A request can be in progress while the next public response is still due from your team. It can also remain assigned to an agent while the customer is being asked for more information.
That is why a work status and a reply state should not be assumed to mean the same thing.
Jira already offers ways to use workflow statuses and automation to track a conversation. If those rules reliably provide the signal your team needs, keep using them. Another app should have a clear reason to exist in your process.
ReplyTurn is intended for teams that want a shared reply-state signal alongside their workflow. It derives that signal from public conversations in supported Jira Service Management and Customer Service Management spaces. Internal notes are excluded; reading a request is not treated as answering it.
For a practical evaluation, choose an active service space and follow the setup guide. Compare the displayed state with the public conversation. Check that an internal note is not mistaken for a customer-facing reply and that the information helps your team decide what to do next.
Initialization and event processing are not a promise of instant completion for every site. Judge the app on your actual supported workflow, not on a claim that it fixes all routing, roles, automation or SLA problems.
ReplyTurn runs on Atlassian Forge and stores derived reply state, not comment bodies. Its privacy and support pages describe the relevant scope.
Who replied last when a request is still escalated?
A customer can reply while a request remains in an Escalated or In Progress workflow status. The team may need that work status to stay unchanged while making the next public reply visible.
Jira Automation can update reply-related workflow statuses or maintain a custom field for your own process. If that gives your team the signal it needs, keep it. Atlassian documents comment-driven status automation and its visibility and role conditions; check those conditions when configuring your rule.
ReplyTurn is an alternative when you want a separate, shared conversation-derived signal. Keep your workflow status and consult ReplyTurn Reply State, Waiting Since, Last Customer Reply and Last Agent Reply in a queue, or open Needs Reply Now for active requests awaiting an agent. This does not replace your escalation process or guarantee a resolution time.
To evaluate the distinction, choose a demo request, compare the public conversation with the reply state, add an internal note, then send a public agent reply. Allow asynchronous processing and refresh. The note should not change reply ownership; the public reply should move ReplyTurn to Waiting Customer. See the real demo views and follow the setup guide below.