Auto-file a JSM ticket

This feature enables all requests created by end-users in a request channel to automatically file a ticket in the ticketing system that is integrated with the collection to which the request channel belongs.

This feature is generally used when you want your support agents to continue working an existing ticketing system and don't want any new team members to monitor the slack channels.

Using this feature, along with the bi-directional sync functionality post responses from agents in the ticketing system back on the same Slack thread and let users continue the support chat from the Slack channel.

How it Works?

Let us go through the flow of creating a JSM Ticket from Slack using automatic ticket creation with ClearFeed.

  1. A customer conversation is created: When you get a message from a requester on a request channel about a new query, a request is created on ClearFeed.

  2. Auto-Creation of a Ticket: Each request is auto-converted to a ticket.

  3. The Slack message is synced to the ticketing platform ticket: The new request messages is sent over the ticketing platform.

  4. Ticket confirmation message: ClearFeed will post a reply on the corresponding thread once a ticket is created.

  5. Comments from JSM ticket get posted on Slack: Any public comment and attachments sent from JSM on the ticket get posted on the Slack thread. ClearFeed will post public comments from JSM agents as a bot. This bot will display the agent's name and profile picture.

  6. Messages from Slack get posted on the JSM ticket: Messages posted on the Slack thread will get posted on the Ticketing Platform.

  7. Sync with Triage Channel: All messages on the ticket and the request channel are also synced to the slack thread on the triage channel. A part of the team can continue to work from the triage channel as well. All responses from the triage channel will be posted on the request channel and get synced to the ticketing platform as well.

  8. Ticket solve and other state changes: When the ticket status changes state on the Ticketing Platform, ClearFeed sync the status of the ticket on the thread.

  9. Automated State Transition: Ticket Status is updated when a non-responder posts a message in the thread. If the ticket is in pending/on-hold/solved status and if a customer replies to the ticket then the ticket status changes to open.

  10. Reopen / Solve Tickets from Slack: You can reopen the ticket from slack if you find the issue is persisting.

Last updated