Service Desk Software for Small Teams
Weenvo is service desk software for small teams that want a queue, priorities, time per request and a knowledge base without a separate ticketing tool. Requests come in through a form and are tracked as tasks on a board with the team’s own statuses; time is logged in the task; runbooks sit next to the queue.
Key benefits
A form for every request
A service desk is the single point where a team receives, prioritises and resolves requests from employees or clients. In Weenvo the entry point is a form: the dispatcher creates a task on the board for each submission, with the request type and the requester, and attaches the form with the details.
Your own request types and statuses
A request type is the category of a request, with the fields and the runbook that go with it: access, equipment, bug, question. Types, priorities and statuses are set in the scheme, so the board shows the team’s process, not a vendor’s.
Time per request
The engineer logs the time in the task when closing it. The time report shows where the desk’s hours went by owner and period, and the board filtered by request type shows how many requests of each kind were closed.
Runbooks next to the queue
The how-to for each request type is a documentation page with version history, linked from the task. The procedure that changed in June is still readable in its June version.
A week at an internal help desk, and the same set-up for client support
Internal IT
An IT team of a few people supports a company of a few hundred. Employees request access, equipment and fixes through a form linked from the company portal. The team lead creates a task in the IT workspace for each submission, with its request type and the requester, and attaches the form; the board columns are new, in progress, waiting for requester, done. On Monday morning the team lead sorts the new column by priority and sets owners. A request for a new system access opens the runbook page for that type from the task; the engineer follows it, logs the twenty minutes in the task card and moves it to done. A laptop replacement waits for the requester to pick a date; the task sits in waiting for requester with the deadline on the calendar, and nobody has to remember it. On Friday the lead opens the weekly timesheet in Time tracking and timesheets and the board filtered by request type: access requests were most of the week’s closed tasks, so the next runbook to shorten is that one. Once a quarter a satisfaction survey goes to everyone who submitted a request.
Client support in a service company
A software house or an agency runs the same set-up for its clients. Each client has a workspace with a support form; the client contact submits a request through the form and sees only their own workspace and their own requests on the board. The team creates a task of type support request for each one, with the form attached and a deadline; hours logged on them are reported by client for the month, which is how the account manager watches the retainer. A client’s recurring question gets a how-to page in the client’s documentation, linked from the next request. When a request is closed, the client contact can rate it through a short form.
Both desks run in one Weenvo account: one scheme for internal IT, one for client support, each in its own workspace.
Use cases
Internal IT requests
Access, equipment and fixes through one form, a prioritised board, runbooks per request type, hours per request.
Facilities and office requests
Repairs, bookings and supplies through a form, a board for the office team, deadlines on the calendar.
Client support for a service company
A workspace per client with its own form; the client sees only their requests; hours per client for the retainer. See client projects in Weenvo.
Onboarding requests for HR
A new hire’s accounts, equipment and documents requested through a form and tracked on the same board. See Weenvo for HR teams and company knowledge base.
What this replaces
One form; a task with type and requester created for each submission, the form attached
Instead of: A shared mailbox and a chat channel.
The board, with statuses, owners and deadlines
Instead of: A spreadsheet log of requests.
Requests, time, runbooks and the client workspace in one product
Instead of: A separate ticketing tool for a small team.
Documentation pages linked from the task type, with version history
Instead of: Runbooks in a wiki nobody updates.
Weenvo applications
Forms and surveys
The request form, attached to the task it leads to; a satisfaction survey after closing.
Projects and tasks
The board with the team’s request types, priorities and statuses.
Time tracking and timesheets
Time per request, weekly timesheet, reports by owner and client.
Documentation
Runbooks and how-tos with version history, linked from the task.
Company portal and workspaces
The form on the portal; an IT workspace; a workspace per client for support.
Calendar
Request deadlines next to the team’s other work.
Cost
Free: up to 10 users with every feature, which covers a small help desk. Standard: €10 per user per month, 10 GB of storage, 15% off on annual billing. A support team of 20 users on Standard pays €170 a month on annual billing or €200 billed monthly. Full details on the pricing page. Last checked 2 November 2026.
Free
0 EUR per user per month
- Up to 10 users
- 50 MB storage
- Every feature
- No credit card
Standard
10 EUR per user per month
- 10 GB storage
- Every feature
- 15% off on annual billing
See Weenvo in Action
Want to see how these features work in practice? Explore how Weenvo can help your business.
FAQs
Is Weenvo a ticketing system?
Weenvo runs a request queue: requests arrive through a form and are tracked as tasks, the board carries the team’s statuses and priorities, time is logged per request and the runbook is linked from the task. Deadlines and priorities are set per request and shown on the calendar.
Does a form create a task automatically?
No. A submission stays in the form’s results; the team creates the task on the board and attaches the form to it, so the request details are in the task and in the results overview.
Can requesters submit without a licence?
Yes. A form can be shared by link and answered without a Weenvo account, so a client’s staff or employees without a licence submit requests the same way.
Can we have our own statuses and request types?
Yes. The scheme defines request types, priorities and statuses, and the board shows them as columns. Internal IT and client support can use different schemes.
Can we log time per request?
Yes. Time is logged in the task card and reported by owner, client and period.
Can we keep runbooks with version history?
Yes. Each documentation page keeps every version with author and date, and earlier versions can be opened or restored.
Do you have SLA timers?
Each request has a priority, a deadline and an owner, and the deadline appears on the calendar and in the owner’s task list. Reports show how many requests of each type were closed in the period.
Ask a Question
Specify the details of how you plan to use our solution suite or any individual product. If your organisation has unique processes and requires an Enterprise‑level implementation, you can also submit a request for a customised setup that supports more efficient workflows.
Thank you for contacting us. Our support will answer you as soon as possible!