Custom Codes Mapping

Custom Event Mapping allows you to create personalized event codes alongside the 280+ official SIA alarm codes. This feature enables precise monitoring and alerting for equipment, zones, and scenarios specific to your installation.

Availability: This feature is available on Pro plan and above only.


Why Use Custom Codes?

Standard SIA codes are universal but generic. Custom codes let you:

Benefit
Example

Specific identification

TEMP_RACK1 instead of generic YT (System Trouble)

Intuitive naming

Use terminology that matches your organization

Equipment integration

Support non-standard or IoT devices

Clear descriptions

Provide context for responders

Example:

Instead of:  YT (System Trouble)
Use:         SRV_DOWN (Production server unreachable for 30 seconds)

Accessing Custom Codes

1

Go to Delay Rules in your dashboard.

2

Click Create Rule or edit an existing rule.

3

Custom codes, if added, appear at the top of the SIA codes table.


Creating a Custom Code

Click + Custom Code in the toolbar to open the creation form.

Code Format

Rule
Requirement
Examples

Length

2-10 characters

T1, TEMP_HIGH, DOOR_01

Characters

Uppercase A-Z, numbers 0-9, underscore

TEMP_1, DOOR_MAIN

Case

UPPERCASE only

βœ… TEMP_HIGH ❌ temp_high

Spaces

Not allowed

βœ… TEMP_HIGH ❌ TEMP HIGH

Note: You cannot use a code that already exists as an official SIA code (BA, FA, PA, etc.).

Description

Provide a clear, human-readable description (max 100 characters). This description is:

  • Displayed in your dashboard and event logs

  • Used in voice messages during calls

  • Included in technical emails

Good descriptions:

Call Action

Choose how the system should react when this code is received:

Action
Behavior

Delayed

Calls contacts after the configured delay

Instant

Calls contacts immediately

None

No call (use with Technical for email-only alerts)

Cancel

Cancels any pending delayed call

Technical Flag

The Technical checkbox sends an email to your technical contact. It can be combined with any call action:

Call Action
Technical
Result

Delayed

βœ…

Call after delay + Email

Instant

βœ…

Immediate call + Email

Cancel

βœ…

Cancel pending call + Email (for audit)

None

βœ…

Email only (no call)


Editing a Custom Code

1

Find the code in the Custom Codes section.

2

Click the ✏️ Edit icon.

3

Modify the description, call action, or technical flag.

4

Click Save Changes.

Note: The code name itself cannot be edited. To change a code name, delete it and create a new one.


Deleting a Custom Code

1

Click the πŸ—‘οΈ Delete icon next to the code.

2

Confirm deletion.

3

Click Save Rule to persist changes.


Plan Restrictions

Plan
Custom Codes

Starter

❌ Ignored (codes can be created in the interface but are not processed)

Pro

βœ… Fully supported

Business

βœ… Fully supported

Important: On Starter plan, custom codes can be configured in the dashboard interface, but they are completely ignored by the system. Only official SIA codes are processed. Upgrade to Pro to enable custom event mapping.


Use Case: IT Server Monitoring

Scenario: You want to be called if a production server (#16) goes down and isn't restored within 30 seconds.

Configuration

Field
Value

Code

16_DOWN

Description

Production server unreachable - intervention required

Call Action

Delayed

Technical

βœ… Checked

Delay Rule Settings

  • Delay: 30 seconds

  • Cancel code: 16_UP (server restored)

How It Works

Benefits

  • βœ… 30-second grace period β€” Avoids false alarms for brief network hiccups

  • βœ… Automatic cancellation β€” No call if server recovers in time

  • βœ… Technical email β€” IT team always notified, even if cancelled

  • βœ… Clear description β€” On-call technician knows exactly what's wrong


Mixing SIA and Custom Codes

You can freely mix official SIA codes and custom codes in the same delay rule:


Best Practices

Naming Conventions

Use a consistent pattern for your codes:

Pattern
Examples

TYPE_LOCATION

TEMP_SRVR, DOOR_WH

EQUIPMENT_ZONE

SENS_ZN1, CAM_PARK

EVENT_DETAIL

FIRE_KTCHN, LEAK_BASE

Action Selection Guide

Urgency
Action
Examples

Critical

Instant

Fire, medical, security breach

Important

Delayed

Server down, door forced, temperature warning

Cancellation

Cancel

Server up, system disarmed, issue resolved

Information

None + Technical

Battery low, maintenance due, audit log

Documentation

Keep a record of your custom codes:

Code
Description
Location
Action
Technical

SRV_DOWN

Prod server unreachable

Data center

Delayed 30s

βœ…

SRV_UP

Prod server restored

Data center

Cancel

βœ…

TEMP_DC

Temp > 35Β°C

Data center

Instant

βœ…


Troubleshooting

chevron-rightCustom code not workinghashtag
Cause
Solution

Starter plan

Custom codes are ignored on Starter β€” upgrade to Pro

Code not saved

Click Save Rule after adding the code

Wrong delay rule

Verify the connection uses the correct delay rule

chevron-rightCannot create custom codehashtag
Cause
Solution

Invalid format

Use only A-Z, 0-9, underscore (2-10 characters)

Code exists

Cannot use existing SIA codes or duplicate custom codes

Lowercase

Codes must be UPPERCASE

chevron-rightTechnical email not receivedhashtag
Cause
Solution

Starter plan

Custom codes (including technical emails) require Pro plan or above

No technical contact

Configure email in connection's Advanced Settings

Check spam folder

Technical emails may be filtered


RΓ©ference

β†’ Create your first delay rule β†’ Public API Reference β€” Send custom codes via API

Last updated