Suptask
Suptask Web AppSignup for FREE
  • Welcome
  • Getting Started
    • Install Suptask
      • Slack permission scopes
      • Invite the Suptask App
    • Your first Inbox & Form
    • Ticket submission
    • Manage and Reply on tickets
    • Key concepts
    • User Guides
      • Ticketing as an Agent
      • Ticketing as a User
      • Rollout and Onboarding guide
    • FAQ & Troubleshooting
    • Contact Support
    • Videos
  • Setup & Configure
    • Inboxes
      • Inboxes
      • Users and Agents in the same channel
      • Service Level Agreements (SLA)
      • Agent Work Hours
      • Automatically create tickets from new messages
      • Migrate to the new generation
    • Forms & Fields
      • Forms
      • Custom Fields
      • Default Fields
      • Custom Statuses
      • Tags
      • Using the Organization field
    • Users & Permissions
    • Slack External Connections
    • Multiple Slack Workspaces
      • Multiple Workspaces & Slack Community
      • Enterprise Grid
    • Branding & White-labeling
    • Language & Translations
  • Working with tickets
    • For Agents: who respond and manage tickets
      • Overview and manage tickets as an Agent
      • Responding to tickets
      • Move or Escalate to another Inbox
      • Submit tickets on behalf of a user
      • Request and manage Approvals
      • Customer Satisfaction Score (CSAT)
      • Templated answers with Canned Replies
      • AI Assistant
      • Followers
      • Delete tickets
    • For Users: who submit tickets
      • How to submit a ticket
      • Overview your tickets as a user
    • Overview & Analytics
      • Overview and track tickets
      • Dashboard
      • Reports
    • Essentials for Your daily work
      • Tickets Summary Notifications
      • Setup one-click emoji reactions
      • How to search for tickets
      • Display Suptask in Slack
  • Integrations, Automations & Workflows
    • Introduction to Integrations
    • List of integrations
    • Integration guides
      • Slack Workflows
      • WhatsApp
      • JIRA Software
      • Zendesk
      • ClickUp
      • Notion
      • Google Sheets
      • Suptask API
      • WebHooks
      • Export API
      • Integrate with other Slack Apps
      • External issue & ticketing systems
        • Create tickets from Suptask to GitLab
        • Create tickets from Suptask to GitHub
        • Create tickets from Suptask to JIRA
    • Email-to-Slack Ticketing
      • Email-to-Slack Ticketing
      • Gmail & Google Workspaces
      • Microsoft Outlook
      • AI Email routing
    • On-call rotation
    • Automations in Suptask
  • Account Management
    • Account Settings
    • Subscription & Billing
      • Subscription & Billing
      • Integrations billing
      • Limitations in the Free plan
Powered by GitBook
On this page
  • How to reply on a ticket as an Agent
  • Public replies vs Internal comments
  • Agent replies: Public (default)
  • Agent replies: Internal comments
  • Replies with Approvers and Followers
  • Withdraw a Public reply
  • Add additional users to a ticket

Was this helpful?

Export as PDF
  1. Working with tickets
  2. For Agents: who respond and manage tickets

Responding to tickets

Learn how Agents respond and manage tickets

PreviousOverview and manage tickets as an AgentNextMove or Escalate to another Inbox

Last updated 1 month ago

Was this helpful?

Submitted tickets are directed via the Form to the Responder channel of the Inbox.

Agents gets access to submitted tickets by being a member of the Responder channel in Slack. They can work privately as a team to resolve tickets together, leaving both Private and Public replies on tickets.

How to reply on a ticket as an Agent


Public replies vs Internal comments

Replies on tickets from Agents can either be:

  • Public reply The reply posted and visible for the Requester who submitted the ticket.

  • Internal comment The reply is internal and only visible to the team of Agents in the Inbox.

This allow your team of Agents to cooperate on tickets without having to leave Slack. It is as easy as sending messages to each other in a message thread.

This cooperation is empowered by the Responder channel that is connected to your Inbox, where Agents can send replies on the tickets directly in Slack.


Agent replies: Public (default)

This option is enabled by default, the replies on tickets in the Responder channel are by default Public and will be visible to the Requester.

How to send a Private reply:

  1. Open the ticket in the Responder channel.

  2. When writing your message, make sure to add the 🔒 (:lock:) emoji at the beginning of the message.

    • This will mark the reply as being Private.

  3. Send the message which will make it a Private reply on the ticket, only visible to the team of Agents in the Inbox.

How to send a Public reply:

  1. Open the ticket in the Responder channel

  2. Send your reply in the ticket message thread.

  3. This reply will be Public by default and visible to other Agents in the same Inbox & Responder channel.


Agent replies: Internal comments

With this option selected, the default replies on tickets from Agents in the Responder channel are by default Internal comments, and not visible to the Requester.

How to send a Private reply:

Any message sent on a ticket with this option enabled will be Private by default.

  1. Open the ticket in the Responder channel

  2. Send your reply in the ticket message thread.

  3. This reply will be Private by default and only visible to other Agents in the same Inbox & Responder channel.

How to send a Public reply:

  1. Open the ticket in the Responder channel

  2. Send your reply in the ticket message thread, this reply will be Private until you make it Public.

  3. Add the 🎺 (:trumpet:) reaction emoji on the message. See below on how to add the reaction emoji.

  4. This will push the message as a Public reply back to the requester(s). The message will look like this when it has been pushed as a Public reply:

How to find the 🎺 (:trumpet:) reaction emoji

You can find the reaction emoji by hovering the mousepointer over the message you want to make Public.

From here you can search to find the emoji

Learn how to configure one-click emojis


Replies with Approvers and Followers

The replies for approvers and followers will always be Private by default, and not visible to the Requester of the ticket.


Withdraw a Public reply

Accidentally sent a Public reply? You can withdraw a Public reply, making sure it is no longer visible to the Requester.

How to withdraw a Public reply:

  1. Open the ticket in the Responder channel.

  2. Identify the Public reply message you want to withdraw, to make it Private and not visible to the Requester.

  3. Edit the message

    1. If your replies are Public by default: add the 🔒 (:lock:) emoji in the beginning of the message.

  4. This will change the message from Public to Private, where the Requester will no longer see it on the ticket.


Add additional users to a ticket

You can easily add additional users to a ticket in order for them to receive notifications from the ticket. This can be done by simply tagging the user in the ticket message thread, which will make Slack send notifications about updates to this user as well.

By default, all replies from Agents are Public. You can change the default behavior of Agent replies in the using the Default Agent replies visibility option.

Get quick access to the trumpet and ticket reaction emoji in your Slack client, by adjusting your preferences.

They always need to need push their reply explicitly to become Public by following the

If your replies are Private by default: add the 🎺 (:trumpet:) .

You can also make use of the feature if the users you want to add are not Agents.

🎺
🎫
Account settings
Setup one-click emoji reactions
Followers
instructions for replies with Private visibility.
reaction emoji on the message
Learn more on how the Inbox & Responder channel works.
Configure your