Event settings

Name

Name of the event. It will be shown to activators and recipients.

Event Icon

Event icon to visualize the type of event.

Border color

Border color which will be used to diplay active episodes on the s.GUARD applications.

Event State Set

Allows to select one of the event state sets which are configured for this tenant. The event state set defines the reaction options which will be offered to the recipients.

Note: even if no reactions are desired for this event, i.e. if none of the recipients has the right to react, it is mandatory to define an event state set.

E-Mail - Activate

Configure keytexts which will lead to episode activation if contained in the incoming e-mail.

If multiple keytexts are defined in the same line, either one of them can start an episode. They can be confirmed by the confirmation keytexts which are present in the same line.

I.e. one line in the keytext list defines pairs of activation / confirmation keytexts.

E-Mail - Confirm

Configure keytexts which will count as episode confirmation in case the episode had been activated by a matching "Activate" keytext.

SMS - Activate

Configure keytexts which will lead to episode activation if contained in the incoming SMS.

If multiple keytexts are defined in the same line, either one of them can start an episode. They can be confirmed by the confirmation keytexts which are present in the same line.

I.e. one line in the keytext list defines pairs of activation / confirmation keytexts.

SMS - Confirm

Configure keytexts which will count as episode confirmation in case the episode had been activated by a matching "Activate" keytext.

API - Activate

Configure keytexts which will lead to episode activation if contained in an activation API call.

If multiple keytexts are defined in the same line, either one of them can start an episode. They can be confirmed by the confirmation keytexts which are present in the same line.

I.e. one line in the keytext list defines pairs of activation / confirmation keytexts.

API - Confirm

Configure keytexts which will count as episode confirmation in case the episode had been activated by a matching "Activate" keytext.

Event activation number

Allows to select a phone number for activation of an episode via an incoming phone call.

Note: the activation phone number has to be previously configured in the Settings.

Incident number

This setting can be defined for events which have an event activation number assigned. If the incident number is specified, it will be used as the code to start an episode.

Example: if the same event activation number is used to activate various events, the caller will by default hear an announcement like "Press 1 to activate event A, press 2 to activate event B".

If an incident number is specified, the incident number will be used instead of the random numbering. E.g., if the incident numbers 20 and 30 are used, the user will hear "Press 20 to activate event A, press 30 to activate event B".

Use activator phone for calls

If enabled, the phone number of the activator will be used as Caller ID when calling recipients.

Event countdown duration

Configuration of timed countdown when activating an event from an s.GUARD application.

Shortcut

Legacy configuration, shall not be used any more.

Protect activity by code

This setting only takes effect if a private security code is set for the respective user in the user settings.

In that case, the user will have to enter the private security code to send a reaction to the episode.

Start episode via email channel while empty KeyText

If enabled, the episode can be activated by an incoming e-mail without matching key text.

In case an episode of another event can be activated by matching its key text, this event will not be triggered. It is considered a fallback if no keytext can be matched successfully for any event.

Event Outbound Phone Number

Phone number in international fromat without spaces, e.g. +19701234567.

If defined, this phone number will be used as caller ID for the recipients of the episode.

Note: this setting is only available if enabled by Swissphone suppport for that tenant.

Code verification

If enabled, a dynamically created 4 digit code will be shown to the user when trying to activate an episode in a s.GUARD application. The user then has to enter the same code in the app to start the episode

Note: this feature can be used to prevent accidentally activating episodes as it adds an additional layer of user interaction.

Event activation security

This setting defines who will be able to activate an episode via incoming phone call:

Activation not permitted - it is not possible to activate an episode from an incoming phone call

Permitted user with code - The event can be activated by incoming phone calls, coming from a phone number which is associated with a user who has activation permissions for the event. Additionally, the user needs to enter the safety code (see below) to activate.

Any caller with code - Any caller can activate the event when entering the safety code.

Permitted user without code - The event can be activated by incoming phone calls, coming from a phone number which is associated with a user who has activation permissions for the event. No safety code is required.

Permitted user without code, all others with code - The event can be activated by incoming phone calls, coming from a phone number which is associated with a user who has activation permissions for the event without entering the safety code. Additionally, the event can be activated by any other user when entering the safety code.

Any caller without code – Any caller can activate the event, without having to enter the safety code.

Safety code (Event act.)

Safety code that may be required for activating an event via phone call, depending on the setting "event activation security" (see above)

Start conference call

If enabled, a conference call will be initiated upon starting an episode. All recipients which are assigned to the event and which have a phone number for voice calls configured will be added to the conference call.

Conference call settings

Defines the procedure of initiating a conference call:

Regular including activator - if the activator started the episode via phone call, he will be put on hold and joined to the conference once all other recipients have reacted. If the activator started the episode via an application, he will be called on his phone number (if configured) once all the recipients have reacted.

Automatically start and stop, hold on activator - this setting is only to be used if the activator will start the episode via phone call. He will then be put on hold while the recipients are called. Once all recipients have reacted, they will be joined together with the activator to the conference.

Automatically start and stop, call back activator - if the activator started the episode via phone call, his call will be terminated. Then, the conference will be established. Once all recipients have reacted, he will be called back and joined to the conference. If the activator started the epiosde via an application, he will be called on his phone number once all recipients have reacted and joined to the conference.

Join Conference Call without confirmation

If enabled, the recipient will automatically joined to the conference call on answering the call from s.GUARD. He will not be asked for confirmation.

Finish call for last participant

If enabled, the conference call will automatically be terminated as soon as only one person remains in the conference.

Timeout (Sec.)

Defines the amount of time in seconds after which the episode will be stopped. The time is counted from the start time of the episode.

0 = one week

Number of confirmations

After the specified number of confirmations (i.e. positive reactions) is reached, the episode will be stopped

0 = All recipients

Note: to achieve that the episode will never be stopped by number of confirmations, set this value to be higher than the number of recipients.

After last notification was sent (sec.)

After all notifications have been sent out, and the time specified for this setting has passed, the episode will be closed.

0 = one week

Priority

Can be used to sort the events in the applications' activation screen by priority.

1 = top of the list

100 = bottom of the list

Tile height

This setting defines the hight of the event / episode tile in the s.GUARD applications, both when activating and receiving an alert.

1 = default height

2 = twice the default height

0.5 = half of the default height