Screens

This section will cover details on the configuration of ClearFeed ticketing screens

When requests are turned into ClearFeed tickets, details are sent back to the requester in a designated ticket message block on the request channel.

  • The screens section lets you customize the ticket message shown to the requester. You can show or hide ticket fields and manage the ticket resolution button.

Enabling ClearFeed Ticketing is mandatory to share the ticket details with the requester. Learn more on how to enable ticketing here.

To configure the ticket message for ClearFeed ticketing, follow the steps given below:

  1. Head over to the Objects section on the ClearFeed web application -> https://web.clearfeed.app/objects

  2. Under the ticketing drop-down, select ClearFeed Ticketing.

  3. Select Screens from the tabs mentioned under ClearFeed Ticketing.

Screen configuration options

The screen configuration options allow users to configure the ticket message block that is displayed to the requesters. The following options are available for configuration:

Fields:

  • Assignee - You can choose to show the name of the Assignee of the ClearFeed ticket on the request channel.

  • Priority - The priority of the ticket can be shown to the requester using this field. The priority of the ticket can be as follows: Urgent, High, Medium, Low.

  • Status - By default, the Status of the ticket is always shown to the requester. This cannot be configured to be hidden. The following statuses are shown to the requester: Open, In Progress, On Hold, Pending, Solved, Closed.

  • Form Name - Name of the Form used to create the ticket.

    • Note: Form name appears only if there is more than one form in the account.

  • Fields populated by Create Form - Only non-empty, non-hidden fields, marked as editable by 'All' in the 'Create Form', will be displayed in the message.

  • Fields populated by Edit Form - Only non-empty, non-hidden fields, marked as editable by 'All' in the 'Edit Form', will be displayed in the message.

Actions:

  1. Mark As Solved button: You can choose to expose the Mark as Solved button which allows responders/requesters to solve a ticket right from the request channel.

    • Check the option to display the Mark as Solved button on the ticket message block.

      • Permissions: All or Responder.

        • All - Allows access to the Mark as Solved button to both the requester and responder

        • Responder - Only agents/responders will be able to use the Mark as Solved action to resolve tickets.

  2. Edit Ticket button: The Edit ticket button will be present on the ticket message by default whenever the Edit action Form is enabled.

    • Disabling a Parent Form (or its underlying Edit action form) will disable the editing feature for existing tickets created using it and the Edit Ticket button will be hidden from all new tickets created using the Form.

Last updated