Topic
This article describes how automated SMARTWeather notifications select recipients, why some contacts who appear to be outside a weather alert area still receive messages, and how group membership and geocoded contact data affect delivery. It also outlines how to review contact and template configuration when investigating unexpected SMARTWeather recipients.
Description
SMARTWeather sends automated notifications using geocoded addresses and membership data stored in contact profiles. The system compares the geocoded location of each contact to the geographic shape of the weather alert issued by the weather service. If a contact’s geocoded location falls within that shape, a template that is configured to alert contacts impacted by that weather type will send the notification to that contact. Everbridge Smart Weather alerts are triggered based on contact addresses, and the system uses geocoding to determine which contacts should receive alerts within a specific polygon. Contacts with addresses near or within the alert zone will automatically receive notifications, provided their stored addresses are geocoded and fall within the alert polygon that the system selects for that weather event.
Automated weather alerts use two primary criteria to select recipients:
Geographic selection: contacts whose geocoded location falls inside the weather alert polygon.
Group membership: contacts that belong to designated group(s) configured in the alert template.
Contacts may still receive weather alerts for locations that seem unexpected. Common reasons include use of map-based location tools, stored coordinates that place the contact inside the alert area, and group configuration:
A contact may have used a “Find your location on a map” function and selected a different location than intended. If that selection is geocoded inside the affected area, the contact will be included.
A contact record can contain coordinates that place the contact inside the alert’s affected area. If the address text appears to be outside the area but the stored coordinates are inside the polygon, the contact will be treated as inside the alert zone.
A contact can receive an alert because they are part of a group included in a notification template that triggers alerts for specific regions. In this case, they may be notified regardless of their own geocoded position.
For location-based alerts, a contact may be alerted if their last-known location or the cell tower they were connected to is inside the alert area. Contacts with travel records can be included if an alert overlaps a travel entry. Alerts that include building polygons can notify contacts assigned to those buildings. Reviewing contact addresses, travel records, and building assignments helps determine why a contact was included in a particular notification.
To verify and adjust which contacts receive SMARTWeather alerts, administrators should review weather-alert templates and Member Portal subscription settings. Reviewing template configuration confirms which groups and rules are configured for specific weather events, and reviewing subscription settings confirms which alert types contacts have signed up to receive. This combination of geocoded addresses, last-known or travel-related locations, building assignments, and template group configuration explains why some contacts receive weather notifications for areas that may not match their apparent address or current physical location.