Desk settings
In Fluo, service desk settings are in the “Edit service desk” window. There you set the name, customer texts, the board connection type, invited people's rights, task type choice and the widget.
To open the window, click the “Desk settings” gear in the header of the desk page. Other ways are listed in “How to create a service desk and connect it to a board”. Changes apply when you click “Save”, and Fluo shows “Desk updated”.
- The “Service desk” column with the name and texts.
- The “Desk connection type” block.
- The “Desk settings” block with toggles.
The “Service desk” column
| Field | What it sets |
|---|---|
| “Title” | The desk name. The team and people invited to the desk see it. The field is required |
| “Internal description” | A note for the project team. Customers don't see it |
| “Instructions for desk users” | Text for customers in the “About the desk” card. The widget shows it too if the “Text above the widget” field is empty |
| “Task description template” | A draft that goes into the description of every new ticket. The customer can add to it or erase it. Pro and Business only |
Desk connection type
| Setting | What it changes |
|---|---|
| “Multiple desk connections with statuses” | You can draw several connections from the desk to different columns. A ticket is sent manually along one of them. Pro and Business only |
| “One desk connection in each route” | The desk has one connection in each route, and you can't draw a second one in the same route |
| “Automatically send task to board upon creation” | Works only with one connection. A new ticket goes straight to the board column, skipping the queue |
Desk connections are drawn on the “Workflow” map, and each task type's route has its own. For more on choosing the connection type and on routes, see “One desk connection or several”.
Desk settings
| Toggle | Default | What it does |
|---|---|---|
| “Chat in ticket” | off | Turns on the conversation with the ticket author. Without the chat, the customer can't write to the team or see its reply |
| “Allow desk participants to mention people with @” | off | Only available with the chat on. Invited people can @mention the project team and other participants of the ticket |
| “Files in ticket” | off | The author can attach files and open attached ones |
| “Checklist in ticket” | off | The author sees the ticket's checklist and can edit it |
| “Show related tasks” | off | Invited people see which tasks the ticket is linked to |
| “Allow desk participants to link tasks and create task chains” | off | Available once “Show related tasks” is on. Invited people link tickets of this desk, including those already moved to a board. With “Everyone sees only their own tickets” on, only their own tickets |
| “Show task blockers” | off | Invited people see what's holding the ticket up. They can't change the blockers |
| “Allow desk requesters to choose the task type” | off | Requesters choose the task type when creating a ticket and change it in their own tickets. The project team always sees the “Task type” field and can set the type. This is the same setting as in the “Task type” field of the desk form. Pro and Business only |
| “Allow returning tickets back to the desk” | on | Invited people can return an accepted ticket to the queue. The team can always do this |
| “Allow deleting tickets from the desk” | on | Invited people can delete tickets. The team can always do this |
| “Everyone sees only their own tickets” | off | Invited people see only the tickets they sent themselves. With the toggle off, every invited person sees the whole queue |
| “Allow desk participants to move tasks to boards themselves” | off | Invited people send tickets to a board themselves, but only along the desk's connections |
| “Allow desk participants to sort tasks” | off | Invited people change the queue order by dragging and with the sorting menu. The order is shared by the whole desk |
| “Show desk metrics to invited users” | off | Invited people see metrics for the tickets open to them |
The same block has the “Set up the desk task form” button. It opens a window where you choose the fields of the ticket form. See “How to set up the ticket form”.
The “Allow desk requesters to choose the task type” toggle is above the “Set up the desk task form” button. Turn it on and save the settings, and the “Task type” field appears in the requesters' form. The place of the field, its width, whether it's required and the list of types for requesters are set in the form window, see “How to set up the ticket form”. The type decides which route's connections take the ticket to a board.
Requesters choose the type on Pro and Business. On Free and Free Team, the toggle has a lock, and clicking it offers an upgrade to a paid plan. You can turn the choice off on any plan. If the paid plan ends, the “Task type” field disappears for requesters, but the setting is kept and comes back once the plan is paid again. The project team sets ticket types on any plan.
Use the desk in other projects of the space
Here you add the desk to the “Workflow” map of other extended projects in this space to connect it to their boards too. Turn on the toggles for the projects. You don't need to save anything. You see the block if the space has other extended projects, but it works only on Business.
On another project's map, the desk has a “Detach the desk from this project” icon instead of the trash icon. While the desk has connections to statuses of that project, the icon won't work, so delete the connections first.
Public ticket intake
Here you turn on the website widget that people without an account use to send tickets. The domains, appearance and embed code are here too. See “How to add the widget to your website”.
Link and activity
- “Public link” is the desk's address in Fluo. The buttons next to it copy the link and open it in a new tab. Only Fluo users can open the link: the team, invited people and, if public intake is on, anyone signed in. An outsider sees only their own tickets in the desk.
- “Active desk”. A turned-off desk disappears for invited people and customers, and the widget shows “Desk unavailable”. The team sees such a desk marked “Inactive”. It doesn't count toward the plan's desk limit.
A spinner or “Failed to load the desk” instead of the form
The window is loading the rest of the desk settings. Wait a couple of seconds. If you see “Failed to load the desk”, click “Retry”. Until the settings load, you can't save the window.
The top of the window says the desk is part of a project template
This is a desk from a template project. It has settings, but no tickets, invitations or widget. They appear in the desk's copy in a project created from this template.
Related articles
On the website: Fluo service desk: client requests straight to the board, site widget