What is a service desk?
A service desk in Fluo collects tickets from customers, contractors and colleagues from other departments. Each ticket becomes a project task and goes to the team's board.
How a ticket moves
A service desk lives in an extended project next to its boards. On the “Workflow” map, you draw connections from the desk to board columns. Tickets go to work along these connections.
- Someone sends a ticket. People without an account do it through the widget on your website. People with a Fluo account create a ticket on the desk page if they were invited to the desk or given its public link.
- The ticket joins the desk queue. It's a regular project task, only without a board and column yet. Such a ticket is called not accepted.
- The team works through the queue. A ticket is sent along a connection to a board column, and that's how it's accepted. Tickets you don't need are closed right in the queue.
- On the board, the ticket is handled like a regular task. It gets an assignee and moves across the columns. Its card shows a headset icon with the desk name.
- All this time, the author sees their ticket and talks to the team in its chat. They don't see the team's internal discussion.
If the desk has only one connection, it can send new tickets to the board by itself, skipping the queue. If the project has task types, each type has its own route with its own desk connections: a ticket without a type follows the “No type” route, and a ticket with a type follows its type's route. See “One desk connection or several”.
The desk page
Desks you take part in are collected in the sidebar, in the “Service desks” block. The block appears once you have at least one desk. Click a desk to open its page.
- The “About the desk” card: the name and the instructions for customers.
- The ticket queue. The buttons in the header switch between open and closed tickets and show only not accepted or only accepted ones.
- “Desk metrics”: how many tickets are waiting and how quickly they're picked up and resolved. See “Desk metrics”.
Who takes part in a desk
| Who | What they see |
|---|---|
| The team: space members and people invited to the project | The whole queue, both chat channels, the desk metrics and settings |
| People invited to the desk | Only the desk: the queue or their own tickets, the “About the desk” card and the conversation with the team. They don't see the project and boards |
| Ticket authors from the widget | Their own tickets and replies, once they sign in to Fluo with the “Track progress” link |
| Fluo users with the public link | Their own tickets in this desk |
People invited to the desk and ticket authors don't take up seats in the subscription. See “Who sees what in a desk and how to invite a customer”.
Service desk and plans
| Feature | Free | Pro | Free Team | Business |
|---|---|---|---|---|
| Active desks per space | 1 | 5 | 1 | unlimited |
| Desk connections to boards on the “Workflow” map | no | yes | no | yes |
| Several connections for one desk | no | yes | no | yes |
| Website widget and tickets without authorization | no | yes | no | yes |
| Custom ticket form and description template | no | yes | no | yes |
| Requesters choose the task type | no | yes | no | yes |
| One desk in several projects of a space | no | no | no | yes |
On Free and Free Team, the “Workflow” map is view-only, so you can't create a new desk there or connect one to a board. If a desk was created during a Pro trial, it stays after the trial, but the widget and the other paid features turn off. All plans are compared in “Fluo plans and feature comparison”.
Example
The Aurora team has released a habit tracker. The app's website has the widget of the “User support” desk. A user writes that reminders don't arrive. The ticket joins the queue, and Vera sends it to the “Backlog” column on the “Bugs” board. Timur fixes the bug and closes the task, and Vera replies to the user in the external channel of the chat.
Related articles
On the website: Fluo service desk: client requests straight to the board, site widget