Skip to main content
Submitting Maintenance Requests Using Limble

How to Submit a Maintenance Ticket with Limble's Work Request Portal

Rachel Link avatar
Written by Rachel Link
Updated over 2 months ago

Overview

If you're reading this article, your company wants you to learn how to submit maintenance requests using Limble's work request system!

Depending on how your company has set up your unique work request system, some of these features may not apply.

If you have any questions, reach out to the person who shared this article with you.

Table of Contents

Accessing the Work Request Form

To submit a ticket you'll need to access the work request form, also known as the work request portal. You can do this via QR code, URL/Link, or email.

  1. QR code: If your company uses a QR code, scan it using your phone’s camera.

  2. URL/Link: If your company provides a URL or link, you can click on it from your desktop or phone.

  3. Email: If your company uses the email method, they’ll provide an email address -- always ending in "@task.limblecmms.com" -- where you can send a message to the maintenance team.


    If this is the case, you will not be using the work request portal. Talk to your administrator about what details to include in your request.

To find out where your company keeps this information, such as on a break room bulletin board or company intranet, talk to your administrator.

Filling Out the Work Request Form

Once you've accessed the form, it's time to build your request. The form will look something like this:

The form contains the following sections:

Required fields are always indicated with "*" (asterisk). Optional fields don't need to be filled out, but more information will help the team identify and solve the issue quickly.

Depending on how your company has set up your unique work request form, some of these fields may not apply to you.

Title, Description, and Contact Information

Give your request a title. This helps the team understand what the request is about.

Give your request a description. Include pertinent details, such as the time and date of the incident, to help the maintenance team understand and address your request quickly. This field is limited to 1000 characters.

Include your contact information, including your name and email address. If you don’t include an email in your request, you will not be able to view or receive status updates about your ticket through Limble.

If you want to include more than one email, add a semicolon and space between each email. For example: bryan@limble.com; jeff@limble.com; rick@limble.com

You may also be asked to include a phone number as another form of contact.

Locating the Request

Helping your team locate and identify the issue will ensure your request is resolved in a timely manner.

“Where or what is having a problem” allows you to identify what is having the issue. Click on the textbox.

In the new window, select the correct item. You can use the search bar to quickly find what you need.

If you are required to provide an answer but don’t know what to choose, click on “I’m Not Sure.”

Once you've made your desired selection, confirm by clicking "Select."

Depending on your company's settings, you may also be asked to include a map location. To do this, click on the field under "Set map location."

In the new window, find and click on the location. Then, exit the window.

Adding a Picture or Document

You know what they say: a picture's worth a thousand words! Adding a photo can help the maintenance team evaluate the issue.

Click “Add Picture/Document.” From the dropdown, you can choose to take or upload a photo, or upload a file.

Once your file has been uploaded, you can crop or mark up the photo to highlight the issue. After you've made your desired edits, click the yellow checkmark to confirm your upload.

Text and Dropdown Fields

You may be asked to include other information in a text or dropdown field. Some of these responses can do things on the backend to ensure the correct team member is assigned to the issue and it’s prioritized appropriately.

In a dropdown field, click on the field and select your desired response.

In a text field, enter your response in the text box.

Once you've filled out the form, click “Submit” to send it to the team.

You’ll see a confirmation message that your ticket has been created.

Staying Updated on Your Ticket

Once you’ve submitted your request, there are a few ways to stay updated on the progress of your ticket:

Email Notifications

Notifications will be sent to the email address(es) you included with your request.

Make sure to check your spam folder for emails from Limble and move them to your inbox to receive future messages.

Depending on your system’s settings, you may receive an email when your request has been submitted.

You may also receive other updates from the team through comments, which will be sent via email. You can reply to these comments by responding directly to the email.

Viewing the Ticket

You can check the status of your request by viewing the ticket itself.

To access the ticket, click the link to the work request in your email.

You can also click the button at the bottom of the work request portal that says “Check Work Requests.”

On the new page, enter the email address you used for the request. Then, click “Submit.”

You'll receive another email. Click "Check Work Requests."

You’ll be directed to a page with your in-progress and completed tickets. Depending on settings, you may see tickets from other requesters.

Click on any request name.

The new window includes the work request name, details, and any comments made on the ticket.

You can communicate with the maintenance team from here by clicking “Add Comment” and submitting your message in the new window.

You will always receive an email when your request has been resolved.

Your maintenance team may include a survey link to get feedback about their work. If it’s there, make sure to fill it out and give them kudos!

Watch the Video Tutorial

Still have questions? Reach out to the person who sent you this article!

Did this answer your question?