Items
Contacts
Feature Summary
The Contacts feature stores and organizes SMS-capable phone numbers and email addresses for use across GSatTrack. Each contact is a single delivery destination (SMS or email) that other portal features use for notifications and alerts.
How to Use
How-To: Add Contact
Go to the Navigation menu and click on ‘Add Item.’
Click on ‘Add Contact’
Fill out the information for the required fields, which are:
Name
Type (Email/phone number)
Fill out the information for any other optional fields
Click on ‘Create Contact’
How-To: Edit Contact
- Go to the Navigation menu and click on the ‘Manage’ icon
- Click on the ‘Contact’ icon
- Click on the ‘Edit’ icon next to the desired Garmin Form
- Make desired changes and click ‘Save Changes.’
How-To: Delete Contact
- Go to the Navigation menu and click on the ‘Manage’ icon
- Click on the ‘Contact’ icon
- Click on the ‘Delete’ icon next to the desired Contact
- Click ‘Delete’ on the popup window
Additional Information
Introduction to Contacts
A Contact is a stored SMS-capable phone number or email address. Contacts exist primarily to support the functionality of other portal features, first by streamlining the processes and activity of portal operators and also by giving Asset Managers control over communications within and outside the portal.
The portal’s contacts do not have multiple email addresses or phone numbers tied to them, as users would find in other types of software that manage people and their contact information. Each Contact in the portal should instead be considered a single delivery destination (SMS or email) for messages from the portal.
Contact Types
- Email: This is a standard email address. The portal will send messages to this type of contact via standard email.
- Free SMS: SMS text messages with no fees associated with the receiving number. The portal will send messages to this type of contact as plain text with no additional characteristics.
- Paid SMS: SMS text messages with fees associated with the receiving number. The portal will require users to accept all charges before it will send messages to this number, and notifications will be sent as plain text with no additional characteristics.
- Emergency Contact: This can be either an SMS or email destination; if indicated as an Emergency Contact, the destination address will automatically receive notifications from the portal whenever emergency protocols are triggered.
Contact Fields
- Rate Limits: Minimum minutes between notification messages from the portal, with separate options for standard and emergency notifications.
- Notification Language: Recipient’s language preference.
- Notification Speed Display: Speed units to be displayed in the notification information.
- Lat/Lng Format: Coordinate format for display in the notification information.
- Fuel Units: The notification information will display fuel units (liter, gallon, miles, kilometers).
- Timezone: Timezone to be displayed in the notification information.
- OpenPGP Public Key: This key allows the encryption of messages. It must be configured. See the OpenPGP article for details.
Contacts in the Manage Module
Once created, users can find a list of all Contacts in the Manage Module under Contacts. The page offers several options for interacting with the Contact list:
- Add Contact: Opens the Add Item page with the Add Contact form.
- Import Contacts: This opens the Bulk Uploads tool,allowing users to import contacts in bulk instead of loading them individually.
- Edit: Users can modify the information in the fields next to each contact.
- Delete: Next to each contact, users can delete the contact (this action cannot be undone).
- Send Test Message: Automatically generates a message from the portal and sends it to the listed destination. If the number is a phone number, the message will be sent as an SMS; if it is an email contact, it will be sent as a standard text email.
Contacts with Other Features
Several features utilize the Contacts list to perform actions or set up communication and alert systems related to device activity:
- Contacts and Alerts: When setting up an Alert, users can configure it to send notifications to any email address or phone number saved as a Contact in the portal. For more information, see the Alerts article.
- Contacts and Reports: Users can schedule certain types of Reports to run automatically and be sent to the Contact of choice upon completion. To use this feature, users must create a Contact for the email address to which they wish to export the Scheduled Report, making it an option on the Schedule Report form.
- Contacts and Users: Contacts exist in the portal as objects that can be assigned to users. The primary user on the account has to create/delete access for Contacts, while non-administrators can only access Contacts assigned to them.
Key Features
- Contact types — Supports Email, Free SMS, Paid SMS, and Emergency Contact destinations.
- Emergency contacts — Destinations flagged as emergency automatically receive notifications when emergency protocols are triggered.
- Per-contact preferences — Rate limits, language, speed units, coordinate format, fuel units, and timezone apply to each contact's notifications.
- Bulk import — Contacts can be imported in bulk via the Bulk Uploads tool instead of being added one at a time.
- Integration with Alerts and Reports — Contacts serve as notification targets for Alerts and scheduled Report delivery.
- Message encryption — An OpenPGP public key can be set on a contact to encrypt messages.
Use Cases
- Asset notifications — Send status-change and event notifications to the relevant contacts.
- Emergency response — Route automatic alerts to designated emergency contacts when emergency protocols trigger.
- Scheduled reporting — Deliver scheduled Reports automatically to a chosen contact.
- Encrypted delivery — Send messages to a contact's OpenPGP-encrypted email destination.
See Also
Supporting Features
Contact Email Encryption
SBD Relaying
Users
User Email Template