Contact Verification in Telematics Guru
Contact verification requirements and process in Telematics Guru.
Written by Daan de Waard
Updated at October 19th, 2026
Table of Contents
Contact Verification exists to improve the reliability and security of automated communications in Telematics Guru. This ensures that recipients are validated and receive the notifications expected.
Contacts have a visible verification status for email and mobile details, with clear warnings shown when unverified contacts are selected for notifications such as Scheduled Reports, Maintenance Schedules, and Alerts.
Verification uses magic links. When verification is requested, a link is sent by email or SMS, and the recipient confirms on a landing page to complete it. The recipient can complete verification independently; no one needs to enter a code or stay present.
Users can verify their own contact details from the Manage Account page, while users with the Address Book Manage role can request verification on behalf of others directly from the Address Book.
An example of the Scheduled Report modal, demonstrating verified contacts (Green tick) and an unverified contact (Blue question mark) in the 'Linked Recipients' list.
Note: All existing contacts are treated as historically verified, and new contacts are verified using magic links sent by email or SMS, which the recipient opens and confirms.
Unverified contacts added after this implementation will not receive notifications.
How verification works
- Magic links, not codes. Verification is completed by the recipient opening the link and confirming on a landing page. There is no code to read back, and the administrator does not need to be present.
- Per contact method. Email and mobile are verified separately. Verifying one does not verify the other.
- Manual sending. Saving or changing contact details never sends a verification request on its own. You must click Verify to send a link. (The exception is user invitation setup, which verifies the email automatically.)
- Cooldown. After a request is sent, the Verify button is greyed out for 60 seconds. To resend, wait for the cooldown to pass and click Verify again.
- Link expiry. A magic link expires 24 hours after it is sent. An expired link shows an invalid-or-expired page with no resend option and does not verify the contact method.
- Resending. Sending a new request invalidates all earlier links for that contact method; only the newest link is valid. Opening a superseded link shows the same invalid-or-expired page.
Verifying a User Account
When a user account is created, an invitation link is sent out. Completing account setup through that invitation verifies the user's email address automatically, so no separate email verification is needed afterwards. During setup, the user can also complete an optional mobile verification step.
Existing users can initiate verification at any time as follows:
- Navigate to the Account → Manage Account page.
- Click the ‘Verify’ button for either or both the email address and mobile number.
Email Verification
- A magic link is sent to the user's email address.
- Open the link and confirm on the landing page to complete verification.
- Observe the success message. The email address is now verified.
Mobile Number Verification
- Navigate to the Account → Manage Account page.
- Enter the mobile number, including the country code, and click the ‘Verify’ button beside the mobile number. A magic link is sent by SMS.
- Open the link and confirm on the landing page to complete verification.
Third Party User Email and Mobile Verification
Admin users with the Address Book Manage role can request verification on behalf of others directly from the Address Book. The recipient completes verification themselves; you do not enter a code.
- Navigate to Admin → Address Book.
- Locate the contact requiring verification.
- Click Verify for the email address or mobile number. A magic link is sent by email or SMS.
- The recipient opens the link and confirms on the landing page. Once confirmed, the contact method is verified.
Tip: Verification belongs to the contact method within a single TG server instance. Verifying an email address or mobile number verifies it for all Address Book entries using that same method in that instance. The same method verified in one instance is not verified in another and must be verified separately there.
Changing a verified contact method
Replacing a verified contact method with an unverified one leaves the replacement unverified, and saving the change does not send a verification request. Click Verify to send a magic link for the new email address or mobile number.
If an alert recipient's verified contact method is replaced with an unverified one, the recipient stays subscribed to the alert, but delivery through that contact method is suppressed until it is verified. Once the replacement is verified, delivery resumes and the recipient does not need to be added to the alert again.
Email Bounce List
When looking at a contact, during setup for an Alert for example, you may notice an icon indicating that the email address is on the bounce list. This means TG will no longer attempt to send emails to that address while it remains on the bounce list. Being on the bounce list means that after repeated attempts the indicated email address was not successful in receiving emails from TG. The bounce list state simply makes that visible in the interface, and indicates that TG has given up attempts at delivery to an address that is effectively undeliverable.
Important
An email address being on the bounce list doesn't reflect upon the trustworthiness of the contact. It simply means the email notification provider set against the org currently considers the address undeliverable, usually due to repeated delivery failures or similar send errors.
Where this appears in Telematics Guru
You may see 🚫 bounce list indicators in places such as the Address Book and when selecting recipients for notifications.
