Use case: service desk
A service desk on one Kanban board.
Requests come in through public forms and email. Your team sorts them with labels, works them through lists, and answers common questions with wiki pages. No ticket system to learn.
- IT and internal support
- Customer service
- Office and facility teams
The problemRequests arrive by chat, phone and five inboxes. Some get lost.
Public forms turn requests into tasks.
Create a form for a board and share its link. Every submission becomes a task in the list you choose.
- The sender confirms with a code sent by email.
- Offer only the labels you allow, such as Bug, Feature request or Question.
- Files and a receipt for the sender are supported.
- New tasks stay unpublished until an editor publishes them.
Free: 25 submissions per month. Team and Enterprise: no limit.
The problemCustomers still write emails. Someone copies them into a tool by hand.
Forward an email, get a task.
An Email Intake gives a board its own address. Every email sent or forwarded to it becomes one task, with its attachments.
- Forward a shared mailbox such as support@, or add the address as Bcc.
- Choose the target list, a default priority and fixed labels.
- Tasks from email are never public.
- Rotate the address at any time.
On every Kanroo Cloud plan. A self-hosted server needs the Enterprise Edition for Email Intakes.
How Email Intakes workThe problem“Any news on my request?” The same question, many times a day.
A public board shows the status.
Publish the board as a read-only page and share the link. Requesters see which list their request is in, and your team writes fewer status emails.
- Any number of public boards on every plan.
- Display names are shown. Email addresses never are.
- Tasks and comments from email never appear. Form requests appear only after an editor publishes them.
- Search engines are told not to index public pages.
The problemHalf of all requests ask the same five questions.
Answer once, in the wiki.
Write the answer as a wiki page and link it from the task. Share pages with customers through read-only links, with a password and an end date if you need them.
- Spaces and nested pages for your knowledge base.
- As many share links per page as you need, for example one per customer.
- Search with ShiftK covers tasks, boards and pages.
Features you will use
Every one of them is on every Kanroo Cloud plan.
Questions and answers
Is Kanroo a full help desk?
No. Kanroo is Kanban with a wiki. It has no SLA timers and no customer portal with sign-in. For a team that wants requests, status and answers in one place, a board is often enough.
Do the people who send requests count as members?
No. They use the public form or write an email. Only the people on your team who work the requests are members of your organization.
Is there a board template for this?
Yes. Kanroo includes a Customer support template. You can also save your own board, with its lists and labels, as a template for your organization.
What about spam?
Form senders confirm with a code sent by email. For Email Intakes, the mail server rejects clear spam. Everything else becomes a task, so forward only a mailbox that exists for requests.
Other use cases
- AgenciesOne board per client project, one wiki space per client, and read-only links that keep each client in the loop.
- Software teamsReleases and bugs on boards, specs in the wiki, and your coding agent connected through MCP. REST API and webhooks for the rest.
- Public sectorWorkspace data in the EU, an open-source core you can self-host, keyboard and screen-reader design, and no built-in AI.
Set it up on your own board.
Every feature is on every Kanroo Cloud plan. Try it alone for free, then invite your team.