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
    • 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
    • Views
    • 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
    • Merging & Split
    • Importing Insights Data into Google Sheets
    • Approval Workflows
  • 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
        • Intercom
        • 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
  • What is a Collection?
  • Types of Collections
  • Collection Settings
  • Accessing Collection Settings
  • Configuration Options
  • Creating a Collection
  • Managing Collections
  • Updating Collection Settings
  • Renaming a Collection
  • Download Collection Data
  • Deleting a Collection

Was this helpful?

Edit on GitHub
  1. ACCOUNT SETUP

Collections

Collections form the core of ClearFeed functionality, acting as way to group channels and apply configurations.

What is a Collection?

A Collection is a group of requests organized by their source—such as Slack Channels, Team Channels, support email addresses, API, Support Portal, Web Chat, or the ClearFeed Slack App.

Each Collection lets you apply common request management and ticketing settings—including workflows, SLAs, assignments, and tagging—across all its sources. This helps streamline operations by managing similar types of requests in a consistent and scalable way.

Types of Collections

ClearFeed supports several types of Collections, each designed to handle requests originating from a specific source or channel. There is a limit on number of collection for a specific type and availability of certain Collection types depend on your ClearFeed Product Edition.

Collection Type
Source
Limit
Product Edition

Standard

Requests from Slack channels.

Multiple per account

All

DM

Tickets from "File Ticket" on the ClearFeed Slack App.

Only one per account

Internal Helpdesk

Email

Requests via your support email address.

Multiple per account

External Helpdesk Internal Helpdesk

Portal

Requests from the ClearFeed Support Portal.

One per account

External Helpdesk

Web Chat

Requests from Web Chat widget.

One per account

External Helpdesk Internal Helpdesk

API

Requests created via API.

One per account

External Helpdesk Internal Helpdesk

MS Teams

Requests from MS Teams channels.

Multiple per account

External Helpdesk

Collection Settings

Collection Settings provide granular control over how requests, tickets, and workflows function within a specific Collection. Accessing and managing these settings allows you to tailor ClearFeed to your team's specific needs and ensure consistent application of rules for the requests grouped within that Collection.

Accessing Collection Settings

You can access Collection Settings via two methods:

  • Navigate to the Inbox in the ClearFeed Web App. Select the Collection you wish to configure from the list. Click on the Collection name, and then click on Settings in the top right corner.

  • Navigate to the Inbox in the ClearFeed Web App. Select the Collection you wish to configure from the list. Click the gear icon beside the Collection name in the list.

Configuration Options

Below is a comprehensive list of all possible settings available within ClearFeed Collections. When creating or updating a specific Collection, only the settings applicable to that Collection type will be available.

  • Responders: Define which users from your organization should be treated as support agents i.e. members capable of responding to requests within this Collection.

  • Email Settings: Configure the Support Email Address from which the emails should be grouped in this collection.

  • Ticket Routing: Configure Request Routing for allowing users to associate requests with any collection within this account when creating requests via ClearFeed App's DM.

  • Additional Collection Settings: Access options to

    • Delete the Collection

    • Download request data for analysis

    • Customize message classification settings (only applicable for the External Helpdesk edition).

Creating a Collection

The process for creating a Collection involves defining specific settings based on the Collection type.

Portal and Web Chat Collections are automatically created when their respective features are enabled.

  • Navigate to Collections from the side navigation bar in the ClearFeed WebApp.

  • Click the Add new Collection button.

  • Based on the type of Collection you are creating, you will be asked to configure the relevant settings. The settings available during creation for each type are:

    • Standard: Responders, Request Channels, Triage Channel, Ticketing, Task Management, Workflows.

    • API: Responders, Triage Channel, Workflows.

    • DM: Triage Channel, Ticket Routing, Workflows.

    • Teams: Responders, Request Channel, Triage Channel, Ticketing.

    • Email: Responders, Triage Channel, Email Settings.

    if any of the option is not shown that means you have already reached the limit of no of collection allowed for that type or the type is not supported for your Product Edition.

Managing Collections

Beyond initial creation and configuration, you can perform several management actions on Collections from the ClearFeed WebApp.

Updating Collection Settings

After a Collection has been created, you can modify its settings. The specific settings that are available for editing depend on the Collection type. Refer to the Overview of Configuration Options section above for a detailed description of each setting.

The settings that can be edited for each Collection type are:

  • Standard: Responders, Assignment Rules, Request Channels, Welcome Message, Triage Channel, Emoji Rules, Ticketing, Task Management, GPT Powered Answers, Automations, CSAT, Business Schedule and SLA settings, Additional Settings.

  • Web Chat/Portal: Responders, Assignment Rules, Triage Channel, Ticketing, GPT Powered Answers, Automations, Business Schedule and SLA settings, Additional Settings.

  • Email: Responders, Assignment Rules, Email Settings, Triage Channel, Ticketing, GPT Powered Answers, Automations, Business Schedule and SLA settings, Additional Settings.

  • DM: Triage Channel, Ticket Routing, Request Channel, Ticketing, Emoji Rules, GPT Powered Answers, Automations, Business Schedule and SLA settings, Additional Settings.

  • API: Triage Channel, Ticketing, Assignment Rules, GPT Powered Answers, Business Schedule and SLA settings, Automations, Responders, Additional Settings.

  • Teams: Responders, Assignment Rules, Request Channels, Triage Channel, Ticketing, Additional Settings.

Renaming a Collection

You can rename a Collection to better reflect its purpose or the team it serves.

  • Navigate to Collection Settings in the ClearFeed Web App.

  • Click on the Edit icon next to the Collection name.

  • Enter the new name and click Save. The updated name will be reflected across the application (all related settings and dashboards).

Download Collection Data

You can download the request data for a Collection as a CSV file from the Additional Settings section. This data can be used for analysis and reporting.

The downloaded data will primarily include ClearFeed requests (messages identified as customer requests). Messages linked to a ticket will also be included, even if they were initially marked as "Not a Request."

Downloaded Data

The downloaded data will contain the following information:

  • Author

  • Assignee

  • Status

  • Channel Name

  • Last Message Time (in UTC)

  • Request Creation Time (in UTC)

  • Is Linked Ticket Present

  • Linked Ticket Id

  • First Response Time SLA Breach

  • Time to first response (In Min) [Only present if SLA breached]

  • Closure Time SLA Breach

  • Closure Time (In Min) [Only present if SLA breached]

Deleting a Collection

To delete a Collection, it must first be empty of associated incoming request sources. This means:

  • Standard and Teams Collections: Ensure the Collection contains no channels. You must remove them or move them to another Collection first.

  • Email Collections: Remove the Email Address from the Email Settings option.

Once the Collection contains no channels or associated sources, it can be deleted using the Delete Collection button within the Additional Settings section.

Portal, DM, API and Web Chat Collections are not allowed to be deleted.

PreviousSecurityNextManage Request Channels

Last updated 5 days ago

Was this helpful?

: Add or remove Slack/MS Teams channels associated with this Collection. You can also manage the ownership of added channels here.

: Configure a dedicated Slack channel where the support team can work collaboratively on Slack to manage and prioritize incoming requests from this Collection.

: Integrate with Native ClearFeed Ticketing or External ticketing systems (like Jira, Zendesk, etc.) and define the rules for how tickets are automatically created or manually triggered from incoming requests.

: Enable the creation of tasks in integrated project management tools (like ClickUp, GitHub, Asana, Linear, and Jira) directly from a Request Channel thread using a simple emoji reaction.

: Define how requests or tickets are assigned to responders. ClearFeed currently supports assignment via Auto-assignment to first responder or Round-robin.

: Customize an automatic greeting that new users receive when they join a Slack channel monitored by this Collection.

: Enable AI-driven responses for frequently asked questions asked in the monitored channels to provide faster initial support.

: Set up automated workflows based on triggers like request creation, status changes, or specific keywords to streamline repetitive tasks.

: Configure specific actions to be triggered within ClearFeed or integrated tools based on defined emoji reactions applied to request messages in Slack.

: Define your team's working hours and set up Service Level Agreements (SLAs) for initial response and resolution times for requests in this Collection.

: Configure custom workflows applicable to the collection.

: Enable and configure Customer Satisfaction (CSAT) surveys to gather feedback from users after their requests are resolved.

During the creation process, you will be prompted to configure the settings that are applicable to the specific Collection type you are creating. Refer to the section above for a detailed description of each setting.

Request Channels
Triage Channel
Ticketing
Task Management
Assignment Rules
Welcome Message
GPT-Powered Answers
Automations
Emoji Rules
Business Schedules & SLA
Workflows
CSAT Survey
Configuration Options
Accessing Collection Settings - Option 1
Accessing Collection Settings - Option 2