FOR JIRA SERVICE MANAGEMENT CLOUD

Keep customer
conversations moving.

CustomerChase follows up requests waiting for a customer reply — on your business calendar, with a clear history of every action.

Release preparation · Marketplace availability will be announced after approval.

Your working days

Choose a time zone, weekdays and holidays. Each deadline starts from the follow-up cycle, not the ticket’s last update.

A reply ends the chase

Public replies from the reporter or request participants stop the cycle. Agent controls let you pause, resume, cancel or restart.

Built on Atlassian Forge

Policies, follow-up state and audit history stay in Forge. The app runtime has no third-party data egress.

A FOCUSED WORKFLOW

Waiting → remind → reply or resolve.

Create a project policy, select waiting statuses, add public reminders and optionally finish with an explicitly configured customer transition. CustomerChase uses JSM’s existing customer notifications.

Due actions are checked approximately every five minutes. If Jira’s response is uncertain, the app stops for reconciliation instead of blindly sending another reminder.