ClearFeed Help Center
ChangelogSign Up
  • Getting Started
    • Integrate Slack
    • For Customer Support
      • ClearFeed Helpdesk
      • Slack <> Ticketing Integration
    • For Internal Support
      • ClearFeed Helpdesk
      • Slack <> Ticketing Integration
    • GPT-Powered Answers
    • Security
  • ACCOUNT SETUP
    • Collections
      • For External Helpdesk
      • For Internal Helpdesk
      • For Integrations
    • Manage Request Channels
    • Setup Triage Channel
    • Teams Setup
    • Email Setup
    • Customer Portal
    • Web Chat
    • Child Accounts
    • Manage Users
    • Login Methods
    • Personal Preferences
  • Create Requests
    • Slack Channels
    • Private Tickets
    • DMs on Slack
    • Email
    • Web Chat
    • From Triage Channel
    • Web Dashboard
    • API
  • Manage Requests
    • Triage Channels
      • For External Helpdesk
      • For Internal Helpdesk
      • For Integrations
    • Web Dashboard
    • ClearFeed Slack App
    • Request Fields
  • Helpdesk Features
    • Tickets
    • Tasks
    • Custom Fields
    • Forms
    • Emoji Rules
    • Insights
    • Quick Replies
    • Customers
    • Automations
    • Workflows
    • Business Schedule & SLA
    • Assignment Rules
    • Team Assignment
    • CSAT Survey
    • Announcements
    • Welcome Messages
    • AI Fields
    • Digests
    • Notifications
  • ClearFeed AI
    • GPT-Powered Answers
      • Virtual Agent & Agent Assistant
      • Testing GPT-Powered Answers
      • Personalize GPT-Powered Answers Name & Logo
    • Knowledge Sources
      • Private Knowledge Sources
        • Confluence
        • Zendesk
        • Freshdesk
        • Notion
        • Slack Channels
        • Slack Canvas
        • Coda
        • Google Drive
        • Other Supported KS
      • Public Knowledge Sources
      • Managing Knowledge Sources
      • FAQs
    • Prompt Customization
    • Search Using Natural Language
    • Bot Interactions
    • ClearBot Assist
    • AI Agents
  • Integrations
    • Task & Ticketing Systems
    • Zendesk
      • Forms
    • Freshdesk
      • Forms
    • Intercom
      • Forms
    • ClickUp
      • Lists
    • HubSpot
      • Forms
    • Salesforce Service Cloud
    • Jira Service Management
    • Jira
    • Linear
    • Asana
    • GitHub
    • FAQs
  • Account Settings
    • Whitelabel ClearFeed
    • Additional Settings
      • Bot Whitelisting
      • Notification Settings
      • Data Retention
      • Pausing Resolution Time
      • Account Management
    • Plans & Billing
    • Developer Settings
  • Pricing and Billing
    • Pricing
    • Billing
      • External Helpdesk
      • Internal Helpdesk
      • Integrations
  • Changelog
    • ClearFeed Release Changelog
Powered by GitBook
On this page
  • Triage channel
  • Triage Properties
  • Not a Request
  • Internal Comments
  • Triage More Actions
  • How are consecutive messages treated?

Was this helpful?

Edit on GitHub
  1. Manage Requests
  2. Triage Channels

For External Helpdesk

Learn how to effectively utilize the triage channel to support customers on Slack.

PreviousTriage ChannelsNextFor Internal Helpdesk

Last updated 5 months ago

Was this helpful?

Key functionalities of the triage channel for External Helpdesk
  • Serves as a single source of truth for consolidating requests from all customer channels.

  • Allows responders to respond to customer queries and edit request properties.

  • Facilitates internal communication between responders and allows sharing the request to an engineering integration such as Jira, GitHub, Linear, etc...

Note: All responses to the request thread on the Triage will be propagated and posted on the same thread in the request channel.

  • All requests from request channels in a Collection will be propagated to their corresponding Triage.

  • If you are working predominantly from triage channels, we suggest you (and preferably leave those channels)

Triage channel

Whenever a customer starts a new conversation in a customer channel, it will be synced into the triage channel as shown below:

  • You can reply in the triage channel thread, and the responses will be synced to the customer channel.

  • Edit button allows you to manage the request's Assignee, Status, Priority, and custom fields (if any).

  • Clicking on view in #channel takes you to the customer channel where the request was started.

  • Mark as Solved allows you to resolve the request.

    • Mark as Closed allows you to permanently close the request.

Triage Properties

Not a Request

Marking a request as Not a request

ClearFeed allows marking conversations as "Not a Request" to exclude them from reports and SLAs.

  • This can be done for Open/Pending requests with a dedicated button or via "More Actions" for In-progress/On-hold ones.

  • Clicking "Not a Request" offers two options:

    • Remove: Deletes the conversation entirely.

    • Archive: Hides the conversation but reopens on further messages.

Note: When responder messages exist in the triage channel, using Remove marks the message as "Not a Request" instead of deleting it. Follow-up messages from the requester will not reopen the request.

Internal Comments

Using Internal Comments on the triage channel

Triage More Actions

Enable responders on the triage channel to convert requests to tickets or link tasks in downstream task management systems with More actions.

Clicking More Actions shows the customer's email and the ClearFeed Collection to which the channel belongs at the bottom.

File a ticket and establish a two-way sync
  • If you use Freshdesk, Salesforce, Zendesk, Hubspot, or JSM for ticketing, convert Slack requests to tickets with the "File a ticket" option in "More Actions."

  • All responses and attachments flow smoothly between Slack and your ticketing system.

  • Agent responses from the triage channel are visible in both the request channel and the external ticketing system.

  • Your team can continue working on requests in the triage channel even after converting them to tickets.

File tasks or link existing tasks from engineering integrations
  • Use ClearFeed to create tasks in engineering systems (like Jira, GitHub, and Linear) and link them to requests for better tracking.

  • Comments from the triage channel thread are synced into the linked task for better visibility.

  • ClearFeed can automatically update the triage channel thread when the linked tasks are completed in the engineering system.

Using Internal Comments on the triage channel

How are consecutive messages treated?

ClearFeed merges consecutive direct messages by the same author on a channel if these messages are made within 5 minutes.

This is done to ensure unthreaded replies are also captured in the request. When this is done, you will see the following message in the triage channel:

If the customer has talked about 2 different issues and 2 different requests should be created for it, follow the below steps:

  • Click on "Split" button

  • A pop-up would show all the messages from the subsequent threads

  • Click on "Confirm"

This would create a new request in the Triage Channel and you can reply to it as you would to any new request.

If you need to create multiple requests, you can follow these steps repeatedly.

  • To adjust the interval, go to Advanced Collection Settings.

  • Modify the CONSECUTIVE_MESSAGES_BY_SAME_AUTHOR_INTERVAL setting (default: 5 minutes).

  • Set to 0 to disable the interval.

Use to mark the conversation as not a request and optionally, remove it from the triage channel.

Use (prefix messages with emoji) to collaborate internally.

Use for filing a task to an external tool like Jira, GitHub, Linear, etc...

ClearFeed allows private conversations with your team members on requests using the emoji.

Messages (and any attachments) with the stay hidden from the customer.

ClearFeed allows private conversations with your team members on requests using the emoji.

Messages (and any attachments) with the stay hidden from the customer.

Learn more about the same .

🔒
🔒
🔒
🔒
Not a request
🔒
internal comments
More Actions
mute all request channels
here
New request from customer channel syncs into triage
Lifecycle of a request from the triage channel
Not a Request action on the triage channel
Using internal comments on the triage channel
Message in a new thread added to the same request