Notifications not received by user
Landport automatically sends notifications to an user based on actions taken by other users and events that transpire on the user's requests. There can be several reasons why a notification is not received:
- Landport did not send a notification - Certain events do not, by design, trigger notifications, but if it seems Landport incorrectly missed sending a notification, here's how to investigate:
- Either log in to the account of the Manager responsible for the request or tap All Requests on your own account to activate "Manager Account Sharing" (assumes it's been defined to see the pertinent Manager).
- Tap the request number. If needed, tap here to view the "Search for a Request" article.
- Below the history log, tap My messages regarding this Request (Incident, Work Order, etc.). You'll see a table showing a record of the notifications initiated and/or received by the user for the last month only (older records roll off the system):
- Look for the notification that should have been received. If it's there, meaning that Landport sent it, then please review the below additional possibilities. If it's not there, and it should have occurred in the last month, then please see item #3, below, and then if still needed, submit a Support ticket with all the details (request number, particular notification not received).
- The Manager declared the request done on behalf of the Servicer - In this instance, a notification is not automatically sent to the original Requestor, giving the Manager the flexibility to decide if and when a notification should be sent. As a side note, an easy way to communicate to the requestor that the job is done is:
- Tap the request number.
- Submit a comment with any closing details, which will be sent to the Requestor and to the Servicer (unless you as the Manager serviced the request...then the notification is redundant).
- On the next page, tap Approve & Close.
- The intended recipient's email/text address is missing or incorrect - If you find this to be the case, you'll want to correct it. Tap the link below to view the appropriate article on editing an user (includes or references how to look them up):
- The intended recipient's notification settings need to be adjusted - Managers, Servicers, and Requestors in "standard mode" (tap here for definition) can access their profile to adjust notification settings and may have inadvertently turned one off. If needed, tap here for guidance on how to adjust "Notification Preferences".
- The
recipient organization's system might be treating the notifications as spam
and placing them in the
recipient's spam folder, or blocking them completely, so they
don't even arrive to the
recipient - The recipient will want to check with the area that administrates their organization's communication system to make sure that messages from the
following address: auto_resp_r@landport.net, are allowed (or "white
listed").
Related Articles
Notification Preferences (Select Which Messages to Receive)
To control when (e.g. new request reported, job completed) and how (e.g. email, MMS text) you are notified when certain request-based events occur: From the Dashboard, tap Your Profile. Tap Select which messages to receive. Select your preferences ...
Getting Added As An Observer (In Order to Receive Notifications)
If you are not the Manager/Requestor/Servicer for a particular request, but want to receive notifications when comments are posted, you may become an "observer" as follows: 1. From the Dashboard, tap All Requests (see Tip). 2. Tap the request ...
Replying To Landport Notifications
The Landport system is designed to be a forum for information exchange between all parties associated with a particular request. To add a comment to a request (e.g. in reply to a Landport notification), you may either: Tap the link in the body of the ...
FAQ: May I put another person's email address into my profile, in addition to my own?
Yes, you may add one additional email or email distribution list, however there are some important things to consider before taking this action: The system is designed to send notifications to the user that is responsible for the request. Having ...
PM: "One time only" request never got created
"One time only" PM instructions must be set to post at least one day in advance, so that the system can properly schedule them in the queue of upcoming PM jobs to be triggered. Tap here for "Edit PM" instructions for guidance on making the ...