---
title: Field Guide — Equipment, EFR & Troubleshooting Reference
description: Technical reference covering equipment specs, EFR status glossary, gateway/access point troubleshooting steps, zone naming rules, and app setup topics.
---
[Skip to content](https://go.sitemetric.com/sitemetric-knowledge-base/field-guide-equipment-efr-and-troubleshooting-reference#main-content)
English - United States
Show submenu for translations
- Home
- Products
- Pricing
- Blog
- Company
Open main navigation
Close main navigation
- Home
- Products
- Pricing
- Blog
- Company
- English - United States
Show submenu for translations
- Contact us
Contact us
How can we help you?
- There are no suggestions because the search field is empty.
1. [Sitemetric Knowledge Base](https://go.sitemetric.com/sitemetric-knowledge-base?hsLang=en-us)
2. [Core Support Operations](https://go.sitemetric.com/sitemetric-knowledge-base/core-support-operations?hsLang=en-us)
3. [Reference Guide](https://go.sitemetric.com/sitemetric-knowledge-base/core-support-operations?hsLang=en-us#reference-guide)
# Field Guide — Equipment, EFR & Troubleshooting Reference
## Reference for field equipment specs, Fleet Report status codes, and troubleshooting for badges and gateways
**Table of Contents**
---
# System Overview
20241028\_Sitemetric\_Service Checklist.pdf
!Sitemetric\_Badging\_Real\_Time\_Location\_System\_20210804\_NP (dragged).jpg
!Sitemetric\_Badging\_Real\_Time\_Location\_System\_20210804\_NP (dragged) 3.jpg
!Sitemetric\_Badging\_Real\_Time\_Location\_System\_20210804\_NP (dragged) 2.jpg
!Sitemetric\_Badging\_Real\_Time\_Location\_System\_20210804\_NP (dragged) 4.jpg
## Equipment Frequencies
We have standard WiFi equipment running in one of the standard 2.4 Ghz or 5.0 Ghz spectrums.
We use Bluetooth (BLE specifically) equipment running in the standard 2.4 Ghz frequencies.
Access Points and Gateways operate in the Low ranges of 902 Mhz to 928 Mhz.
Sites with a cellular Cradlepoint on-site will be using standard cellular 4G, LTE, or 5G frequencies, depending on cellular network availability.
---
# Field Equipment Requirements
Equipment Type: Gateways, Access Points, Omnidirectional and Directional Locators, BLE Badges, RFID, NFC
- **Power Requirements**: Gateways (120V), Access Points (120V or Solar), Omni (2 AA Batteries)
- **Configuration**: Net tokens, provisioning to a site
- **Range**: Distance from one device to another
- **Obstruction**: Machinery, materials, weather, etc obstructing the pathway between equipment
- **Coverage**: Enough equipment to cover a given area
- **Capacity**: Ratio of equipment to the number of people to be detected badges
- **Compliance**: People actually wearing a badge
- **BLE Battery Voltage**: > 2.5V
---
# Equipment Fleet Report (EFR)
## EFR Glossary of Terms
- **Red:** Several Heartbeats missed; the device is likely offline. Check for device changes, loss of power, or poor signal coverage.
- **Green:** The device is actively sending heartbeats.
- **Gray:** No traffic history detected for the device. Verify the device is installed, has power, and the mac address is correct.
- **Blue:** Unprovisioned device is likely in the same room as the device name given. (LB Name for Unprovisioned Access Points, AP Name for Unprovisioned Location Beacons)
**HBER (Heartbeat Error Rate)** 0% means 0 of the last 4 messages from the device were missed. An error rate of 25% indicates that 1 of the last 4 heartbeat messages was not received. An HBER with an “\*” next to it indicates the device has never sent a heartbeat to the system.
**RSRQ (Reference Signal Received Quality)** RSRQ = (N \* RSRP) / RSSI measured over the same bandwidth. RSRQ is a C/I type of measurement and it indicates the quality of the received reference signal. The RSRQ measurement provides additional information when RSRP is not sufficient to make a reliable handover or cell re-selection decision.
**RSRP (Reference Signal Received Power)** RSRP is the power of the LTE Reference Signals spread over the full bandwidth and narrowband. A minimum of -20 dB SINR (of the S-Synch channel) is needed to detect RSRP/RSRQ.
**RSSI (Received Signal Strength Indicator)** For Location Beacons and Access Points, RSSI is an estimated measure of the power level that a device is receiving from an Access Point or Gateway, respectively. At low values (larger negative value) signal wireless data rates get slower and/or transmissions cannot get through. For Gateways, the carrier RSSI measures the average total received power observed only in OFDM symbols containing reference symbols for antenna port 0. The total received power of the carrier RSSI includes the power from co-channel serving & non-serving cells, adjacent channel interference, thermal noise, etc.
**Avg(Average)** The average is calculated from the last 10 samples. \*\*\*\*
## Public/Private Net Tokens
**Private token: 17d9cb43**
**Public token: 4f50454e**
Gateways: Can easily be switched between public and private tokens. Simple cloud-based API switch. The device may not even need to be connected.
1. Definitions:
1. Public network token: May receive detections from other nearby locations (e.g., call it less than 1 - 2 miles)
2. Private network token: Is a network token dedicated to Sitemetric, so detections should only flow to Sitemetric physical sites
2. Detection Equipment Ordering:
1. "New equipment" (i.e., access points and gateways) can be configured to be on \***either**\* the private or public network token. So if we have a job site that is on the public network token, we can order new equipment to be on the public network token. Then as that site is de-commissioned, we can re-configure the equipment to be on the private network token and deploy to another site.
3. Site Deployments:
1. When deploying detection equipment to physical sites -- \***we should not mix public**\*/**private** network token detection equipment. We just need to make sure the detection equipment is:
1. Either on the public network token; or
2. private network token
2. For all new physical site deployments (i.e., physical sites we have not deployed any equipment yet) we should use equipment configured to be on the **private network token -- this should provide cleaner data flow.**
4. Remote check for public/private tokens: TBD
## EFR General Guidelines to Consider
- Access Point RSSI should be between -105 and -60
- Gateway RSSI should be between -105 and -60
- Location Beacon RSSI should be between -80 and -85.
- Never mix GW or AP that are on different network tokens together at the same site. When these devices are mixed, the Access Point will appear as Gray in Air Finder.
- Rain will make the quality of the data flow between the equipment go down
---
## EFR Troubleshooting Steps
**Omni Point is red (or gray) in the fleet report**
- **Lost**: Has the device been removed, lost, stolen, etc?
- **Range**: Is the distance between Omni and Access Point < 50’ to 80’ and is the Access Point green?
- **Obstruction**: Are large metal objects obstructing the Omni and Access Point connection?
- **Weather**: Is there heavy rain, high wind, etc?
- **Omni Battery**: Is the battery dead or covered in corrosion?
- **MAC**: Is the MAC Address entered correctly in the fleet report?
- **Dual Token**: The token between the Omni and Access Point may need to be checked by Link Labs
**Suggestions:**
- Relocate Omni Point closer to the Access Point.
- Reset or change Omni Point Battery
- Contact Link Labs to check Dual Token
- Replace Omni Point
---
**Access Point is red (or gray) in the fleet report**
- **Lost**: Has the device been removed, lost, stolen, etc?
- **Power**: Does the Access Point have power?
- **Range**: Distance between Gateways and Access Points: ~1/4 mile
- **Obstruction**: Are large metal objects obstructing the Access Point and Gateway connection?
- **Weather**: Is there heavy rain, high wind, etc?
- **MAC**: Is the MAC Address entered correctly in the fleet report?
- **Token**: Does the Access Point token match the Gateway token?
**Suggestions:**
- Relocate Access Point closer to the Gateway.
- Contact Link Labs to change token
- Replace Access Point
---
**Gateway is red (or gray) in the fleet report**
- **Lost**: Has the device been removed, lost, stolen, etc?
- **Power**: Does the Gateway have adequate cell coverage?
- **Weather**: Is there heavy rain, high wind, etc?
- **MAC**: Is the MAC Address entered correctly in the fleet report?
- **Token**: Does the Gateway token match the Access Point? (Note: may still be green)
**Suggestions:**
- Open the Gateway and check internal connections.
- Relocate Gateway to get better cell coverage.
- Contact Link Labs to change Token
- Connect Gateway to router with Ethernet cable plugged into the LAN port and contact Link Labs
- Replace Gateway
---
# System Capacity
**Access Points**:
- About 20 messages/minute is about the normal full average load for an access point.
- It takes a little under a second for the access point to handle a connection from a tag.
- Sitemetric’s current settings of 8-second location update rate, in theory, 3 tags constantly moving (reporting a new location) could fully load an access point.
- Normally you are probably looking at something more like 20-30 tags moving (changing locations) at the same time per access point.
- Based on the heartbeat rate an access point can handle about 400 stationary tags.
**Gateways**:
- 6-8 thousand messages an hour is normal capacity.
- A gateway can be saturated at about 8-12 fully loaded access points but can have up 1-2 hundred access points connected if the traffic is spread out.
- Gateways and Access Points should not be any closer than ~15’
## Best practice recommendations:
- Gateways and Access Points should not be any closer than ~15’
- One GW for every 15-30 APs
- One AP for every 5-8k square feet (70’ x 70’ to 90’ x 90’)
- For tags in storage, 1 AP for every 300-400 tags.
- Out-of-network (out of AP range) tags use battery faster than in-network.
- “Looking for network” scans use a lot of energy relative to most other tag operations.
- 20 Uplink Messages per Access Point per Minute
- 8000 Uplink Messages per Gateway per hour
- It would be very difficult to saturate an Access Point with Location Beacons.
- Around 300 Omni Points per AP (as a high-end estimate)
- Our Omni Points send 1 uplink message every 15 minutes.
- 1 AP can handle 20 uplinks per minute
- 20 uplinks per minute \* 60 minutes = 1200 uplinks/hour/AP / 4 uplinks/hour/LB = ~300 LBs/AP
\*Note: You’d want to color this with estimated tag traffic, but LBs are really really small loads on the system.\*
---
# Troubleshooting a Gateway
\*If a gateway is not functioning open up the casing and inspect the 3 PC boards, they can pop out due to transit, shipping, knocked over etc.\*
1 LED = Power
> 1 LED, LL can fix most things by connecting to a router.
## Re-seat the Radio Card Instruction
- Open the gateway up (4 Philips screws)
- Slide off the lid
- There is a card inside with a foam attachment (that’s the heat sink, DO NOT REMOVE), that is the Radio Card that may be having issues
- There are two tabs that hold the cards into place, pull them back and the card should pop up. (You may want to put light upward pressure on the card with one finger while poking the tabs back with my other hand.)
...then give it the ole Nintendo cartridge treatment:
- Unplug the card
- Blow off any dust
- Firmly re-plug it in
- Re-assemble everything inverting the instructions above
- Power the gateway up.
## Change Battery
- If Gateway will not connect and has cell coverage, you may need to replace the LR44 internal battery
## Connect with an Ethernet Cable
- Connect a DHCP-enabled network router to the gateway’s LAN Ethernet jack (the one closest to the serial connector).
- Submit a ticket with Link Labs informing them that the Gateway has been plugged in and asking them to troubleshoot the device.
## Gateway Troubleshooting Flowchart (from Link Labs
---
# Troubleshooting Badging Issues
There are a few variables to consider when assessing any badging-related issues.
1. **Reporting**: What reports are being used and do the users understand how to read the reports?
2. **Compliance**: Are workers wearing badges?
3. **System**: How is the system set up and is it working properly?
4. **Badges**: Do the badge batteries have enough voltage to make detections?
### Compliance
\*Observe who is enforcing badging compliance. Some things to look out for:\*
- Are badges being worn/carried by workers?
- Do the superintendents wear their badges?
- Are badges being left in cars?
- Are there many stationary/overnight badges?
### Site Setup
\*Review the type of system that has been deployed\*
- Scan only
- BLE only
- Scan + BLE
### Scanning
\*If scanning is being done on the site, determine who is doing the scanning\*
- Sitemetric Onsite Personnel (ex. DCO)
- Customer (ex. Site Safety)
- Self-scanning station
### System Performance
\*If you observe adequate badging compliance, the next step is to look into the connectivity of the hardware\*
- Who is responsible for the maintenance of the equipment?
- Check the Fleet Report: What is the status of the field equipment? (See earlier System Hardware section)
### Battery
\*If badges are being scanned but not detected elsewhere on site, and the system is connected, there may be an issue with the badge battery.\*
- What are the last 10-20 voltage readings? If less than 2.5 volts, the badge should be replaced
- What are the dates of the last 10-20 BLE detections?
### Renewals
\*If badges do need to be replaced, determine who is in charge of badge renewals.\*
- How are workers contacted and instructed to replace their badges?
- Where should they go to replace a badge?
- Who will be replacing the badges?
- Are there enough badges onsite to do the replacements?
---
# Turkey Giveaway Scanner
- We’ll set up a dedicated scan station that will allow workers to scan in once for the turkey giveaway.
- The scanner will display green to confirm eligibility (turkey not yet received) and red to deny access (indicating they’ve already received their turkey).
> Please note a few restrictions:
1. There will be only one scan station (iPad, scanner, scan gun).
[https://sitemetric.slack.com/archives/C023T761N01/p1731682977045599?thread\_ts=1731442485.382429&cid=C023T761N01](https://sitemetric.slack.com/archives/C023T761N01/p1731682977045599?thread_ts=1731442485.382429&cid=C023T761N01)
# Zone Naming
## Guidelines for naming zones
### Currently, spaces are automatically removed
- Dashes (-) need to be placed between each word for zone names to appear legible on any reports.
> 💡 Field techs may or may not, add the dashes in their descriptions. In these instances, the dashes need to be added when provisioned in the Admin.
## Zone Names
### Trailers
- **Field-Office** — No longer use “Trailer” or “Trailer City”
### Fence line
- **Project-Entrance** — No longer use “Main Entrance”
- **Man-Gate** (Gates for people, not vehicles)(Not “Main” Gate)
### Buildings with more than one level
- **Level-(1)**
- **Level-(2)**
- **etc**
## Additional workarounds
### Currently, due to the coding necessary to remove all the `LEADING` NO.1, 2, 3 etc., and `TRAILING` OP, AP, SAP, etc., the following naming convention needs to be used
- Zone names can not start with the letters NO
- The main issue is with the word `North`.
- You may need to be creative. Instead of North Fence, try Fence-(North). This may also work, but would need to test (North Fence)
- Zone names can not end with a number
- Zone names (probably) can not end with OP, AP, or SAP.
- Haven’t seen this yet, but seems likely.
> 💡 When there is time, hopefully, we can rename all zones and update the reporting to no longer need these work-arounds
---
# Sitemetric App - User Setup
## Creating a User Login
> 💡 Activation Link expires in 7 days
<< Add steps to create a user login here >>
---
## Scanner App Not Showing up
> 💡 You have to either log out and log back in or wait until the access token gets renewed. For instant access, logging out/back in will always fix it. Deleting and re-installing will accomplish the same.
---
## Allowing Users to assign badges to and edit a worker profile
> 💡 Add “**workforce**”, “**site-workers**”, and the users site to the “**Site Access**” list.
User Steps: Updating worker profile pic (Do not use this image to send to any customers)
# Safety Notes
User Steps: Adding notes to a worker profile
We can also add a report to see all safety notes:
# Allowing Users to remove another worker’s site access
> 💡 Add “**site-workers**”, and the users site to the “**Site Access**” list.
---
# Mass-Texting (Sitemetric App)
## SMS Opt-Out Keywords and Stop Words
Learn more about how Telnyx processes SMS opt-outs and handles stop words
Written by Telnyx EngineeringUpdated over a week ago
## What are SMS Opt-Out Keywords?
Telnyx automatically processes incoming messages and recognizes English-language stop words. Stop words are specific words such as STOP or UNSUBSCRIBE that signal that a person no longer wishes to receive messages from you.
When Telnyx identifies a stop word, the person's phone number is added to the opt-out list and you will no longer be able to send messages to that number. **Any further messages from your account that are sent to a number on the opt-out list will not be processed.**
Coming soon: You will soon be able to retrieve all phone numbers that are on the opt-out list.
**Telnyx recognizes the following English-language stop words:**
- stop
- stopall
- stop all
- unsubscribe
- cancel
- end
- quit
Please note that stop words are only recognized if they are the only words in the message. For example, "stop all" is recognized but "please stop all messages" would not be recognized.
**To restart messages the number that opted out has to send any of the following opt-in keywords to the exact same number they opted out from:**
- start
- unstop
### Number pool
Note that to be able to restart messages, the end user needs to send the opt in keywords above to the exact same number they opted out from. When using our number pool feature you might not get clarity as what number they opted out from since it you used several numbers to send messages out. You should be able to find the opt out SMS in your MDRs by filtering for number that opted out, this way you can easily determine the number where the opt in needs to be sent to.
## Who handles the auto response from an opt out?
By default, Telnyx will handle the auto response. If a user of your services decides to opt out via one of the above stop words towards your numbers, Telnyx will detect this and automatically send out a generic unsubscribed message from the number that received the opt out message.
**Generic Messages**:
- "You have successfully been unsubscribed, you will not receive any more messages from this number. Reply START to re-subscribe."
- You have successfully been re-subscribed to this number. Reply STOP to unsubscribe. Msg&Data Rates May Apply.
However, It is possible to allow for custom block rules and auto responses on a per messaging profile basis but recommend contacting our sales team ([sales@telnyx.com](mailto:sales@telnyx.com)) to discuss this further.
## Texting Errors
If a user receives a **500 erro**r when trying to send a message, that most likely means the message is too large. Previously, it would look like it worked, but the messages would just stay in the queued state forever. This is an improvement in that at least it doesn't silently fail, but we're working on getting some front-end improvements out for a permanent fix. Until then, if someone gets the error, advise them to shorten the message or separate the spanish and english as two messages. A quirk to know about sms messages: the moment you use one extended character, such as a spanish accent character or a unicode emoji, the size of the message (in character count) you can compose halves. It drops from about 1400 characters to 700 characters.
## Primary Language
Many many languages have been added to the messaging module including HT = Haitian Creole. When receiving a text message, workers can reply `LANG` to the message which will provide them with a full list of languages to choose from. They can simply respond with `HT` to begin receiving all text messages in Haitian Creole.
Reply with a language code ar = Arabic bg = Bulgarian bn = Bengali bs = Bosnian cy = Welsh de = German el = Greek en = English es = Spanish fa = Persian fi = Finnish fr = French fr-CA = Canadian French he = Hebrew hi = Hindi hr = Croatian ht = Haitian Creole hu = Hungarian it = Italian ja = Japanese ko = Korean lt = Lithuanian lv = Latvian mn = Mongolian no = Norwegian pl = Polish pt = Portuguese ro = Romanian ru = Russian sk = Slovak sl = Slovenian sr = Serbian sv = Swedish th = Thai tr = Turkish uk = Ukrainian vi = Vietnamese zh = Chinese
---
# Slack Invite
1. In the Slack app, click on “Sitemetric” in the upper left.
2. Select “Invite people to Sitemetric”.
1. Enter their email address in the To Field.
2. Select “Guest” under “Invite as”.
3. Select the site’s reg channel under “Add to channels”.
4. Leave “Allow them to be added to more channels…” unchecked.
5. Leave “No limit” under “Set a time limit”.
6. Optionally add a custom invitation message.
1. Please download this Slack app for Sitemetric. We created a dedicated channel for your project as an easy way to submit registration requests and more. This is also a fast and convenient way to immediately reach our Sitemetric team for support. If you have any questions, do not hesitate to ask. @MichaelGilsinan
7. Click “Send”.
# Site Analytics
# Mustering & Roll Call
**\`Roll call:\`**
Doesn’t make you pick a ‘zone’
Doesn’t sync across devices.
It’s more of an informal attendance, so it’s used, for example, in morning meetups when the GC may get everyone together.
**\`Mustering:\`**
Reports into the server
Syncs across devices
Treated with a higher priority in our backend.
# Badge Station Set-up
**\`Laptop:\`**
When setting up the laptop, a generic email is used, eg BadgeStation23@outlook.com
**\`Link to Dropbox "Badge Photo" folder:\`**
[https://www.dropbox.com/scl/fo/r1qcituxl3z1tb03ha0hv/h?rlkey=3vcmutoyxmng9puuoa14rj90p&st=abn4i024&dl=0](https://www.dropbox.com/scl/fo/r1qcituxl3z1tb03ha0hv/h?rlkey=3vcmutoyxmng9puuoa14rj90p&st=abn4i024&dl=0)
Any badge station should be able to access the link.
Once the Badge Station clicks the link, a request will be sent to Dropbox admins.
Then the Badge Station should be able to join the folder.
# Merging Worker Profiles
1. Open the Merge Wizard from the All Workers tab
1. Copy the Sitemetric ID's that you want to merge, paste them into the search bar and add profile to merge
1. once you've added all the profiles to merge click "Continue to Step 2"
2. Click/Highlight the information from each profile you would like to retain and carry over to the new merged profile
!image (3).png
1. Continue to Confirmation
2. Verify all worker information is correct
3. Click Confirm & Submit
4. Done
# Procore Integration
Each ‘night’ (really, 4 am the next day) we gather all the detection data on the site from the previous day. We attribute each worker’s hours to their company (subcontractor) so we arrive at something that looks like this:
Acme Company, 10 workers, 70 total hours.
The idea is that each morning the logs from the previous day will be populated in the Manpower section and then you can edit those logs as you see fit.
Part of our setup process is to match the companies in your Procore project with the ones in Sitemetric. This is so that the entries are the same as if you selected the company when manually entering the information.
We do not override any manual entries that have been made. We first check if there are any existing entries for the company. If there are, then we do not add our data. Since we are doing this at an early hour, more than likely we will be the first to make the log entries. You are free to continue with your manual process for the same companies if you choose. You can even delete the entries created by the integration.
The main thinking behind this strategy is that utilizing the integration to populate the Manpower log will reflect actual worker hours and eliminate a lot of manual entry on your part.
# Changing site\_id (or creating a new site to replace an old site)
- Create the new site:
- If you **do not** want to create new Slack channels, ensure the Slack Channel field does not start with `site-`. Use `icomm-` or any other prefix to prevent new Slack channels from being created.
- Inform Nate and the Data Entry Team of the change. They will:
- Update forms and QR codes.
- Transfer site access from the old site to the new site for all workers.
- Remove site access from the old site.
- Update worker badges to reflect billing to the new site
- Inform the Devs of the change. They will:
- Update integrations.
- Update any detections at the old site with the new site\_id.
- Handle any other backend tasks.
- Update all Slack channels with the new site\_id.
- Verify all steps are completed and confirm with Data Entry and Devs that it is okay to change the old site's status to `archived`.
- [Reports](https://go.sitemetric.com/sitemetric-knowledge-base/reports?hsLang=en-us)
- [Integrations](https://go.sitemetric.com/sitemetric-knowledge-base/integrations?hsLang=en-us#main-content)
- [How-To Guide](https://go.sitemetric.com/sitemetric-knowledge-base/integrations?hsLang=en-us#how-to-guide)
- [SOP](https://go.sitemetric.com/sitemetric-knowledge-base/integrations?hsLang=en-us#sop)
- [Internal - Reporting & Data](https://go.sitemetric.com/sitemetric-knowledge-base/internal-reporting-data?hsLang=en-us)
- [Support Request Types](https://go.sitemetric.com/sitemetric-knowledge-base/support-request-types?hsLang=en-us#main-content)
- [General Inquiry](https://go.sitemetric.com/sitemetric-knowledge-base/support-request-types?hsLang=en-us#general-inquiry)
- [Device & Hardware](https://go.sitemetric.com/sitemetric-knowledge-base/support-request-types?hsLang=en-us#device-hardware)
- [Out of Scope](https://go.sitemetric.com/sitemetric-knowledge-base/support-request-types?hsLang=en-us#out-of-scope)
- [Installations & Onboarding](https://go.sitemetric.com/sitemetric-knowledge-base/support-request-types?hsLang=en-us#installations-onboarding)
- [Platform & Application](https://go.sitemetric.com/sitemetric-knowledge-base/support-request-types?hsLang=en-us#platform-application)
- [Data & Reporting](https://go.sitemetric.com/sitemetric-knowledge-base/support-request-types?hsLang=en-us#data-reporting)
- [Account & Billing](https://go.sitemetric.com/sitemetric-knowledge-base/support-request-types?hsLang=en-us#account-billing)
- [Internal - Agent & Bot Guidance](https://go.sitemetric.com/sitemetric-knowledge-base/internal-agent-bot-guidance?hsLang=en-us)
- [Product & Platform](https://go.sitemetric.com/sitemetric-knowledge-base/product-platform?hsLang=en-us)
- [Notifications & Messaging](https://go.sitemetric.com/sitemetric-knowledge-base/notifications-messaging?hsLang=en-us#main-content)
- [SOP](https://go.sitemetric.com/sitemetric-knowledge-base/notifications-messaging?hsLang=en-us#sop)
- [How-To Guide](https://go.sitemetric.com/sitemetric-knowledge-base/notifications-messaging?hsLang=en-us#how-to-guide)
- [Troubleshooting Guide](https://go.sitemetric.com/sitemetric-knowledge-base/notifications-messaging?hsLang=en-us#troubleshooting-guide)
- [Core Support Operations](https://go.sitemetric.com/sitemetric-knowledge-base/core-support-operations?hsLang=en-us#main-content)
- [SOP](https://go.sitemetric.com/sitemetric-knowledge-base/core-support-operations?hsLang=en-us#sop)
- [Reference Guide](https://go.sitemetric.com/sitemetric-knowledge-base/core-support-operations?hsLang=en-us#reference-guide)
- [Troubleshooting Guide](https://go.sitemetric.com/sitemetric-knowledge-base/core-support-operations?hsLang=en-us#troubleshooting-guide)
- [Handbook](https://go.sitemetric.com/sitemetric-knowledge-base/core-support-operations?hsLang=en-us#handbook)
- [Directory/Catalog](https://go.sitemetric.com/sitemetric-knowledge-base/core-support-operations?hsLang=en-us#directory-catalog)
- [Reporting & Data](https://go.sitemetric.com/sitemetric-knowledge-base/reporting-data?hsLang=en-us#main-content)
- [Reference Guide](https://go.sitemetric.com/sitemetric-knowledge-base/reporting-data?hsLang=en-us#reference-guide)
- [Troubleshooting Guide](https://go.sitemetric.com/sitemetric-knowledge-base/reporting-data?hsLang=en-us#troubleshooting-guide)
- [Directory/Catalog](https://go.sitemetric.com/sitemetric-knowledge-base/reporting-data?hsLang=en-us#directory-catalog)
- [SOP](https://go.sitemetric.com/sitemetric-knowledge-base/reporting-data?hsLang=en-us#sop)
- [How-To Guide](https://go.sitemetric.com/sitemetric-knowledge-base/reporting-data?hsLang=en-us#how-to-guide)
- [Admin Portal How-Tos](https://go.sitemetric.com/sitemetric-knowledge-base/admin-portal-how-tos?hsLang=en-us#main-content)
- [How-To Guide](https://go.sitemetric.com/sitemetric-knowledge-base/admin-portal-how-tos?hsLang=en-us#how-to-guide)
- [Handbook](https://go.sitemetric.com/sitemetric-knowledge-base/admin-portal-how-tos?hsLang=en-us#handbook)
- [Directory/Catalog](https://go.sitemetric.com/sitemetric-knowledge-base/admin-portal-how-tos?hsLang=en-us#directory-catalog)
- [Forms](https://go.sitemetric.com/sitemetric-knowledge-base/forms?hsLang=en-us#main-content)
- [Troubleshooting Guide](https://go.sitemetric.com/sitemetric-knowledge-base/forms?hsLang=en-us#troubleshooting-guide)
- [Directory/Catalog](https://go.sitemetric.com/sitemetric-knowledge-base/forms?hsLang=en-us#directory-catalog)
- [Reference Guide](https://go.sitemetric.com/sitemetric-knowledge-base/forms?hsLang=en-us#reference-guide)
- [Devices & Hardware](https://go.sitemetric.com/sitemetric-knowledge-base/devices-hardware?hsLang=en-us#main-content)
- [SOP](https://go.sitemetric.com/sitemetric-knowledge-base/devices-hardware?hsLang=en-us#sop)
- [Reference Guide](https://go.sitemetric.com/sitemetric-knowledge-base/devices-hardware?hsLang=en-us#reference-guide)
- [How-To Guide](https://go.sitemetric.com/sitemetric-knowledge-base/devices-hardware?hsLang=en-us#how-to-guide)
- [Site & Campus Management](https://go.sitemetric.com/sitemetric-knowledge-base/site-campus-management?hsLang=en-us#main-content)
- [Reference Guide](https://go.sitemetric.com/sitemetric-knowledge-base/site-campus-management?hsLang=en-us#reference-guide)
- [SOP](https://go.sitemetric.com/sitemetric-knowledge-base/site-campus-management?hsLang=en-us#sop)
- [User Access & Accounts](https://go.sitemetric.com/sitemetric-knowledge-base/user-access-accounts?hsLang=en-us#main-content)
- [Reference Guide](https://go.sitemetric.com/sitemetric-knowledge-base/user-access-accounts?hsLang=en-us#reference-guide)
- [Troubleshooting Guide](https://go.sitemetric.com/sitemetric-knowledge-base/user-access-accounts?hsLang=en-us#troubleshooting-guide)
- [SOP](https://go.sitemetric.com/sitemetric-knowledge-base/user-access-accounts?hsLang=en-us#sop)
- [App Features & Product Documentation](https://go.sitemetric.com/sitemetric-knowledge-base/app-features-product-documentation?hsLang=en-us#main-content)
- [Reference Guide](https://go.sitemetric.com/sitemetric-knowledge-base/app-features-product-documentation?hsLang=en-us#reference-guide)
- Home
- Products
- Pricing
- Blog
- Company
[](https://go.sitemetric.com/?hsLang=en-us)
[mailto:email@email.com](mailto:email@email.com)
Copyright © 2026, www.sitemetric.com