Custom Labels for Service Request Statuses
Every team has its own vocabulary. What Juniper calls a request that has just come in, your team might call new, logged, or intake. Custom status labels let you set that wording yourself, so the Service Requests dashboard reads the way your team already talks.
Once set, the label appears everywhere that status is shown: the web dashboard, mobile app, status overview, filters, individual requests, exports, and stats or reporting views.
Getting Started
- Who can do this: Property developers and customer admins.
- Before you start: Labels are account-wide. They can't be set per property or project, so a relabel affects every request in the account, not just the ones you're currently viewing.
Setting a Custom Label
From the Service Requests dashboard, click the pencil icon beside the Service Requests heading at the top of the page to open the status panel.
Every status is listed. Click one to expand it, choose Custom label, type your wording, and click SET. Suggested labels reflecting common industry wording are also offered — for Assigned, for example, you'll see options like Allocated, Dispatched, and Assigned to trade.
Relabel as many statuses as you need, then click DONE. Changes take effect immediately.
To change a label later, expand the status and click REPLACE. To go back to Juniper's original wording, select Default instead.
Do Custom Labels Change How a Status Behaves?
No. Custom labels are display-only. Renaming a status changes what your team reads on screen and nothing else: a status that opens the assign dialog still opens it after relabelling, dashboard filters and status counts keep working, notifications keep firing on the same triggers, and reporting stays intact. Juniper tracks the underlying status separately from the label you choose to display, which also means relabelling is completely reversible, with no effect on requests sitting in that status.
Where Custom Labels Show Up
Custom labels appear consistently across the Service Requests dashboard, status overview, and filters; individual request views; CSV and PDF exports; stats and reporting views; the Juniper mobile app; and the weekly service-provider status reminder email.
Which Statuses Can Be Relabelled?
All 13 service request statuses accept a custom label. This is a fixed set: you can rename any of these statuses, but you can't add a new one, remove one, or change the order they appear in.
|
Status |
What it does |
|---|---|
|
Submitted |
Logged and awaiting triage |
|
Under Review |
Awaiting internal review |
|
Approved |
Approved to proceed |
|
Assigned |
Opens assign dialog |
|
Scheduled |
Opens scheduling dialog |
|
En Route |
Trade is on the way |
|
In Progress |
Work underway |
|
On Hold |
Paused, no action for now |
|
One Year Warranty |
Covered by the 1-year warranty |
|
Resolved |
Work complete, awaiting close |
|
Closed |
Request closed |
|
Declined |
Opens decline dialog |
|
Archived |
Archives the request |
A Practical Example
Say your team refers to incoming requests as "new" rather than "submitted." Relabel the Submitted status as New, and your Status Overview shows a New count in place of Submitted, covering exactly the same requests, with every filter, notification, and report working as before.
Quick Reference
|
Detail |
Info |
|---|---|
|
Who can edit labels |
Property developers and customer admins |
|
Where to find it |
Service Requests dashboard → pencil icon beside the page heading |
|
Character limit |
40 characters per label |
|
Scope |
Account-wide — labels can't be set per property or project |
|
Applies to existing requests |
Yes, immediately, with no change to the requests themselves |
|
Appears in exports, stats, reports |
Yes |
|
Appears on mobile |
Yes |
|
Reversible |
Yes, at any time |
|
Affects status behaviour |
No |
Questions? Contact the Juniper support team at juniper-support@spark.re.