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
  • Auto-assign to First Responder
  • Auto-assign to First Responder for ClearFeed Requests and External Tickets
  • Round Robin Assignment
  • Availability of Users
  • FAQs

Was this helpful?

Edit on GitHub
  1. Helpdesk Features

Assignment Rules

PreviousBusiness Schedule & SLANextTeam Assignment

Last updated 3 days ago

Was this helpful?

Assignment Rules allow you to automatically assign incoming requests based on your support setup and team structure. This automation helps streamline your workflow and ensures requests are directed to the right people quickly. You can configure assignments to:

  • Automatically assign requests to the first team member who responds.

  • Distribute requests among members of a Slack group using a round-robin method.

  • For integrations with external ticketing systems like Zendesk or HubSpot, assign both the ClearFeed request and the linked external ticket simultaneously to the first team member who responds.

Auto-assign to First Responder

This rule automatically assigns the ClearFeed request to the first team member who takes an action on the request within Slack, such as replying to the initial message or reacting to it. Follow the steps to enable:

  • Navigate to the Collection where you want to enable or modify assignment rules.

  • Open Settings for that Collection.

  • Select Assignment Rules.

  • Select the assignment rule: Auto-assign to the first responder.

  • Click Save.

Auto-assign to First Responder for ClearFeed Requests and External Tickets

Note:

  • This rule is only applicable and visible if Ticketing for the Collection has been set to Zendesk or HubSpot in the Collection settings.

  • If the ticket is already assigned to some agent on Zendesk/HubSpot, this will not work.

When this rule is enabled, the first team member who interacts with the request in Slack will be automatically assigned both the ClearFeed request and the linked Zendesk or HubSpot ticket. Follow the below steps to enable:

  • Navigate to the Collection where you want to enable or modify assignment rules.

  • Open Settings for that Collection.

  • Select Assignment Rules.

  • Select the assignment rule: Auto-assign to the first responder for ClearFeed requests and external tickets.

  • Click Save.

Round Robin Assignment

The Round Robin assignment rule distributes incoming requests evenly among members of a designated Slack group. ClearFeed cycles through the members of the group, assigning each new request to the next available person in the sequence. Follow the below steps to enable:

  • Navigate to the Collection where you want to enable or modify assignment rules.

  • Open Settings for that Collection.

  • Select Assignment Rules.

  • Select the assignment rule: Round Robin Assignment.

  • Select the desired Slack Group from the dropdown menu.

  • Click Save.

Important Notes for Round Robin:

  • Group Membership: Only members of the selected Slack group will be considered for automatic assignment.

  • Internal Helpdesk: In the case of an Internal Helpdesk Collection, only users designated as agents within ClearFeed will be assigned tickets via Round Robin, even if the Slack group contains non-agents.

  • Self-Assignment Skip: When an agent creates a request and is scheduled to be the next assignee according to the round robin sequence, they will be automatically skipped. The system will instead assign the request to the next eligible agent in the rotation to prevent self-assignment by the requestor.

Availability of Users

ClearFeed checks user availability through their Slack status when using Round Robin assignment. Users will be skipped in the assignment sequence if their Slack status is set to one of the following exact strings (case-insensitive):

  • Out of Office

  • Off Sick

  • On Holiday

  • DND

  • OOO

If a user is marked as unavailable, the request is assigned to the next available responder who is part of the configured Slack Group.

FAQs

  1. If users are marked as unavailable on Slack, how are requests assigned on Round Robin Assignment? Answer: If a user is marked as unavailable based on their Slack status (as listed above), the request is automatically assigned to the next available eligible responder in the Slack Group rotation.

  2. What happens if a Slack Group and its members change? Answer: If a Slack Group is renamed or if its members are modified, we honor the new group members.

Prerequisite: Before setting up a Round Robin assignment, configure your Slack workspace with the necessary Slack groups. to learn how to create Slack Groups.

Can we automatically add/remove users from Slack groups based on their shifts? Answer: While ClearFeed doesn't directly manage users within a Slack Group, you can use third-party apps like the for scheduled user management in Slack. ClearFeed will always use the latest set of users present in the Slack Group at the time of assignment.

Follow this guide
Rotation App
Setting up auto assignment to first responder
Setting up assignment to First responder for CR Requests & Zendesk/HubSpot Tickets
Setting up Round Robin Assignment