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
    • AI Agents
      • Knowledge Sources
        • Public
        • Private
          • Confluence
          • Zendesk
          • Freshdesk
          • Notion
          • Slack Channels
          • Slack Canvas
          • Coda
          • Intercom
          • Google Drive
          • Other Supported KS
        • Manage
        • Testing
        • FAQs
      • Build AI Agents
      • Use AI Agents
      • Prompt Customization
      • Bot Interactions
    • Natural Language Search
    • ClearBot Assist
  • 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
  • How to Configure Approval Workflows?
  • How the Approval Process Works

Was this helpful?

Edit on GitHub
  1. Helpdesk Features

Approval Workflows

PreviousImporting Insights Data into Google SheetsNextAI Agents

Last updated 23 days ago

Was this helpful?

Approval Workflows help you manage structured decision-making on ticket requests — whether it’s expense sign-offs, IT requests, or compliance approvals.

Approvals is only available on the Internal HelpDesk Product Edition.

How to Configure Approval Workflows?

  1. From the left navigation bar in the WebApp, click More → Approval Workflows.

  2. Click Create Approval Workflow and give your workflow a meaningful name.

  3. Set an Intake Form: The Intake Form defines when the approval process begins.

    • Choose a form used for ticket creation

    • Select Non-Editable fields — these cannot be edited once approval starts.

  4. Define Approval Rules: Approval Rules determine the approval paths for the tickets

    • Add one or more routing rules.

    • For each rule:

      • Set conditions using ticket fields (must match all conditions).

      If no rule matches, the Default Routing is triggered automatically.

How the Approval Process Works

Once your workflow is set up, here’s what happens:

  • When a user raises a ticket using the selected Intake Form, an Approval Request is automatically created and linked to the ticket as a blocker.

Ticket status (e.g., "Closed", "Solved") cannot be changed until the Approval is completed (Approved or Rejected).

  • The system checks all routing rules in order. The first matching rule decides the approval path — i.e., which users need to approve the request.

  • The first Approver is notified via Slack (ClearFeed App). Approvers can view ticket details and approve or reject the request directly in Slack and also add comments while taking the action.

  • If approved, the next approver (if any) is notified.

  • If rejected at any point, the Approval Request is closed as Rejected.

  • If all required approvers approve, the request is marked as Approved.

  • Every action (approval or rejection) is logged as a private comment on the ticket.

    • These appear in the WebApp Ticket Activity, Approval Task view, and the Slack Triage Channel.