📩 Move Emergency Contacts from 1.8-Style Events to 2.5+ Contacts
📩

Move Emergency Contacts from 1.8-Style Events to 2.5+ Contacts

Quick Reference QR-AE-005 · Audio Enhancement EPIC · Rev 1.2 · Oct 2026

After upgrading to EPIC 2.5 or later, move text and email recipients out of the old event actions and into Contacts, then point each event at a contact group.

📄 View or download this guide as a PDF

Click the PDF icon below to open it right here in your browser. In the viewer, use Download (top right) to save a copy, or the printer icon to print it.

🤝

Written by: Brad Roy, VSC Director of Operations · Verified against: AE EPIC 2.5 Admin Manual DC-40654.0824; EPIC Release Notes 2.5.4.2 to 3.2.5; EPIC 3.2 User Management Enhancements DC-41278.0726 · Applies to: EPIC servers upgraded from 1.8 to 2.4, now on 2.5 or later (screenshots: VSC demo, VSC High School)

Before EPIC 2.5, each event kept its own list of email and text recipients inside its sendEmail and sendSms actions. From 2.5 on, people live in Contacts, sorted into contact groups, and each event just picks the groups to notify. The upgrade doesn't move the old recipients for you.

⛔

Do this before editing any events. AE: when migrating from a version before 2.5, notification recipients must be moved by hand to a contact list and then added to events. If administrators edit events after updating to 2.5 but before migrating contacts, event contacts may be lost. Write down every event's recipients first.

1️⃣ Find the old recipients

  1. Log into EPIC. Go to Settings › Events › Advanced.
  2. Open the event drop-down and select your event. This example uses SAFE Alert.
  3. Find the action that holds recipients: sendEmail (email) or sendSms (text). Copy the recipients down if you haven't yet.

Settings › Events. The Advanced button is at the top right.

2️⃣ Clear them

  1. Click the edit pencil on the action, select all of the recipients in Enter Recipient and delete them.
  2. Click Update Action. Repeat for each event that sends email or text.

Advanced › the sendEmail action. Clear Enter Recipient, then click Update Action.

3️⃣ Create your contacts

  1. Go back to the regular Event Builder by clicking Events at the top, then click Contacts.
  2. Click Add Contact and fill in the name, email, mobile number and job title.
  3. Pick the Contact Group(s). The group decides which notifications a contact receives.
  4. Click Add Contact.
Contact groupWho belongs in it
SchoolPrincipals and building-level administrators
DistrictNeighboring building principals (if not using District View), SROs, superintendents, operations
SupportPeople who know EPIC's back end. Typically used for system-monitoring events, like devices going offline.

Events › Contacts › Add Contact. Pick the group(s) and click Add Contact. The mobile number is redacted.

💡

On EPIC 3.2 and later: the Contact List is merged into Settings › System Settings › User Management. Click Add Local User. For someone who only gets alerts and never logs in, set User Group to Contact. Enter an Email and/or Mobile Number (at least one, or they get nothing), assign one or more Contact Groups (School Administration, District, Support, School Staff) and click Add. The other steps don't change.

4️⃣ Add a Messages action to each event

  1. Go back to the Event Builder (the arrow left of Contacts, or Events at the top).
  2. Click the event to notify on, for example SAFE Alert.
  3. Scroll down, open Immediate Actions (also labeled Then these actions will happen) and choose Messages - Send text and email notifications.
  4. Select the Contact Group(s) that should receive it.
  5. Edit the Email Subject and Message if you want. The defaults are good. Insert tags (variables) as needed (table below).
  6. Set when it runs. Start with previous runs it at the same time as the action above.
  7. Scroll to the top and click the green Save button.

Immediate Actions › Messages - Send text and email notifications.

The Messages action: contact group, subject, message, insert tags, and Start with previous.

EventWhat triggers it
SAFE AlertPaired alert: the person pressed both sides of their own microphone, or a SAFE button was pressed
SAFE Alert - non-pairedBoth sides of a microphone pressed outside its own room, or both sides of a badge. Starts triangulation on the front-office kiosk.

5️⃣ Message variables (insert tags)

TagWhat it inserts
{schoolName}School name (for example VSC High School)
{roomName}The Room Name from Map Setup (not the Display Name)
{eventName}Name of the event (for example SAFE Alert)
{deviceName}Device name set in Devices (for example VHS-105-MS700)
{mapName}Map name: usually the building, or a floor or section
{zoneName}Zone name (listed in EPIC's binding variables)
{ip}Device IP address (listed in EPIC's binding variables)
{dateTimeOfEvent}Date and time the event was triggered
{emailActionUrl}Link back to EPIC. For a SAFE Alert it can offer escalation to Lockdown (VSC understanding).
{alertName}Alert name. Usually the same as {eventName} (VSC understanding).

Field tips

  • Won't save? If EPIC reports missing fields or invalid data, check the entries outlined in red. Sometimes default entries are there with no values. Delete them and save again.
  • A contact only gets an event's messages if one of their groups is picked in that event's Messages action.
  • Send a test from one event after the move and confirm each group gets the email and text.
  • EPIC 3.2+: make sure someone is in the default Support (missing-badge emails) and Maintenance Contact (offline-device emails) assignments.
🔧

VSC note: Upgrading a district from an older EPIC? Ask VSC to plan the contact move with the upgrade so no event loses its recipients. Questions: VSC Customer Service, (248) 926-2540 · [email protected].


📚 Sources & credits

  • Compiled by Brad Roy, VSC Director of Operations. Procedure and field notes from VSC's demo server (VSC High School).
  • Audio Enhancement: EPIC Release Notes 2.5.4.2 through 3.2.5 (pre-2.5 contact migration warning); EPIC 2.5 Admin Manual DC-40654.0824, Contacts and contact groups (p. 70), Messages action (p. 66); EPIC 3.2 User Management Enhancements DC-41278.0726 (contacts in User Management, Contact user group, contact groups, default contacts).
  • EPIC Advanced action editor, Binding Variables list (screenshot 9/16/2025). Screenshots: VSC demo; mobile number redacted.