Service requests are the way to hand a task over inside UnSpot: order stationery, report faulty equipment, have a meeting room prepared. An administrator configures the services — in which offices they are available and who the assignee is in each office — employees submit requests for them, assignees process those requests. This article is the entry point to the section: it helps you pick the right service type and suggests the order in which to set everything up.
What you need: the Super Administrator or Offices Administrator role to configure things; the “My requests” module enabled (Manage → Company settings → the “Available functionality” block); at least one employee to assign as an assignee — or one assignee per office, if a service will work only in selected offices.
The service type is chosen once, at creation, and never changes afterwards. It decides where the employee submits the request from and what they state in it. This is the main fork of the section — start here.
Service type
When it fits
Limitations
Article
“For employee”
The task is not tied to a place: stationery, access, IT help
No request object and no service mode. The request is submitted from an account only, through the “Create a request” window; the employee states the office in the form
A service for a specific meeting: a coffee break, room preparation, equipment
The “Due date” field is always mandatory: by default it is the meeting date, and the time is the end of the meeting. From the booking card it is ordered by the organiser, their manager or an employee who manages all users, from the “Create a request” window — only by the organiser, for their own meetings
Separately from the type you choose where to process the requests — inside UnSpot or in an external ticket system. That choice is also made once and is available for all three types. The other service settings — availability in offices and assignees, request fields, SLA — can be changed after creation as well.
Processing method
When it fits
Limitations
Article
“Inside UnSpot”
Your own employees handle the requests right in UnSpot
An assignee is required: one for all offices, or a separate one in each selected office. Only here are “Response SLA” and “Completion SLA” available
You already have a service desk and do not want to create accounts in it for your employees
The handover is one-way: the request gets the final status “Sent” straight away, and the answer from the external system does not come back into UnSpot. No SLA
Manage → Company settings → the “Available functionality” block → the “My requests” card
Create and configure services
Manage → Office management → the “Services” tab
Export QR codes
Manage → Office management → the “Resources report” tab
Process requests
The “Requests” section → the “Service requests” tab
Rollout order
Enable the “My requests” module — without it there is no “Services” tab at all.
Decide which tasks you are covering and map them to the service types using the table above.
Decide for each service where the requests will be processed: inside UnSpot or in an external system. This cannot be changed later — only by deleting the service and creating it again.
Decide where the service will be available: “All offices” with one assignee, or “Selected offices only” with a separate assignee in each office. This choice can be changed later.
Assign the assignees. For processing inside UnSpot an assignee is required — the common one or one in each office row — and without it the service does not work.
Decide which fields the request will have: “Due date” and “Files and images”, and whether they are mandatory. Both fields are off for new services — switch on the ones you need; only for “In meeting room” the “Due date” field is always on and mandatory. Optionally set the response and completion SLA.
The service type and the processing method can be changed later
They cannot. In the “Edit service” window both chip groups are read-only. Everything else can be changed: availability in offices and assignees, service details, SLA, request fields, and for the “In the office” type also the service mode
The “Office Services” card is a separate module, and requests will work without “My requests”
They will not. That card has no switch of its own, and the “Services” tab as a whole is gated by the “My requests” module flag: turning it off costs you the setup of all three types at once
The Super Administrator role allows seeing all requests of the company
It does not. The full list is opened not by a role but by a setting in the employee card: the “Subordinates” block, the value “All users”
Employees of every office see the service
It depends on the “Availability” section. An “All offices” service — yes. A “Selected offices only” service is offered only in those offices and offices nested in them one level down, including the public page opened by a QR code — there the list is built for the office of the object
A request always goes to the one assignee of the service
Only for an “All offices” service. For a per-office service the request goes to the assignee of the office stated in the request, and if that office has no row — to the assignee of its parent office
An enabled SLA will highlight overdue requests or send a notification
It will not. SLA times are saved in the service settings, but UnSpot does not track overdue requests and sends no notifications
A request can be brought back from a final status
It cannot. “Completed”, “Cancelled” and “Sent” are not reversible — only a new request
The “Sent” status means the external system has received the request
It means UnSpot has sent the email. UnSpot receives no delivery confirmation
If something does not work
Symptom
Where to look
There is no “Services” tab in office management
The “My requests” module is off
There is no “Create a request” button in the header
There is no working service of the “For employee” or “In the office” type, and the visitor pass module is off. On the “Service requests” page the button is always present
The “Create a request” window does not list the service you need
The service is switched off, has no active assignee, or is set to “Selected offices only” while a different office, or none, is picked in the “Office” field — see “For employee” requests: setup
The status toggle of a service in the table is inactive
No active assignee is left — they were blocked or deleted — or a per-office service has no rows left, for example because all its offices were deleted. See “For employee” requests: setup
A request reached the wrong assignee
For a per-office service the assignee is taken from the office of the request, and if that office has no row — from its parent office. Check the rows in the “Availability” section
An employee cannot attach a file or set a due date
The “Files and images” or “Due date” field is off for the service. For services created before these fields appeared, files are off — switch them on in the “Service request fields” section
The request list is empty although requests were created
The “Creation date” filter in the “Request Filter” window is preset to today — see Processing service requests
The QR export found nothing
No offices are selected: without them the list is empty and unexplained
