Setup closure tags

Closure tags are the labels operators select when closing an alarm in ZenMode. Every closed alarm requires a tag — this data feeds into analytics and reporting.

Configure tags before operators go live. Closure tags should be set up before operators begin handling alarms. If no tags exist when an operator attempts to close an alarm, the Close Alarms modal shows a Create closure tag button — clicking it opens the Configure tags dialog — click the tag icon button in the top-right area of the Alarm Center (next to the WORK MODE toggle) to open it. The alarm cannot be confirmed until at least one tag exists.

Add a closure tag

1. In the Alarm Center (Admin mode), click the tag icon button in the top-right area next to the WORK MODE toggle. The Configure tags dialog opens.
2. Click the Tag name field and type the name for your tag.
3. Press Enter. The tag appears as a pill in the list below the input.
4. Repeat steps 3–4 for each additional tag.
5. Click Update to save your changes.

Operators see the updated tag list the next time they close an alarm in ZenMode.

How operators select a closure tag

When closing an alarm in ZenMode, the Close Alarms modal includes a Closure tags required dropdown. Operators can either select an existing tag or type to create a new one:

• Select from the list — click the dropdown to see all configured tags and pick one.
• Type to filter — typing narrows the list to matching tags. Only Super Admins can create new tags via the Configure tags dialog in the Alarm Center.

Remove a closure tag

1. In the Alarm Center (Admin mode), click the tag icon button in the top-right area next to the WORK MODE toggle. The Configure tags dialog opens.
2. Click the × icon next to the tag you want to remove.
3. Click Update to save your changes.

Tips for designing a good tag set

Keep the list concise so operators can select quickly. Useful starting categories:

• False alarm causes: vegetation, lighting, weather, other motion
• Real alarm types: intrusion, suspicious activity, vehicle, vandalism
• Workflow outcomes: escalated, dispatched, verified with customer

Tag name field

What are tags used for in Alarm Center and how do I design a good tag set?

Tags label every closed alarm with an outcome. They feed into analytics breakdowns and customer reporting. A good tag set covers: false-alarm causes (vegetation, lighting, weather, motion-other), real-alarm types (intrusion, suspicious activity, vehicle, vandalism), and workflow outcomes (escalated, dispatched, verified-with-customer). Keep the list concise so operators can select a tag quickly.

Press Enter to add each tag

Is there a faster way to add many tags than typing each one?

Today, no — tags are added individually via the Press Enter input. Bulk tag import is on the roadmap. The current pattern is to plan the tag set offline (a spreadsheet works), then run through this dialog once and type them in. Tag order matters slightly: tags appear in operator dropdowns in the order you add them, so list the most-used outcomes first to save operator clicks.

Update button

Do I need to click Update for the tags to be applied?

Yes — Update is the commit step. Tags you’ve added in this dialog are local until you save. Once saved, operators see the updated list of tags in their closure dropdown on the next alarm they close. Existing closed alarms retain whatever tag they had at the time — no retroactive change. If you remove a tag, alarms previously closed with that tag still display it as a historical value but no new alarms can use it.

Close button

What happens if I close Configure Tags without saving?

If you have pending changes (added or removed tags), Close prompts you to confirm discarding them. Confirming reverts every change and operators continue seeing the previous tag set. Cancelling the close keeps the modal open so you can save or keep editing. Tags only persist after clicking Update — so close-without-save is a safe escape hatch if you started a tag set redesign and decided to roll it back.