Text / Images / Audio

Event description

Describes the purpose of the event.

This text is visible to the activator in the s.GUARD applications.

Restrict multiple active episodes

This setting defines how many episodes of the same event can be running in parallel.

If set to 0, the number of concurrent episodes will not be restricted at all.

Note: this setting only applies if the messages of the episodes are different. Having more than one episode with an identical message is never possible.

Silent trigger

The push notification will be delivered silently, without playing any sound.

Note: this setting is only relevant for the mobile applications.

Vibration trigger

If enabled, the mobile phone will vibrate on delivery of the notification.

Note: this setting is only relevant for the mobile applications.

Event sound

The sound which shall be played upon reception of the episode.

By clicking the play button next to the name of the sound, the currently selected sound will be played.

Note: this setting applies to both mobile applications and desktop client.

Pager alert pattern

Defines the alert pattern which is used on the pager upon receiving the episode:

Pattern x - matches the alert pattern which is programmed on position x on the pager device

Note: this setting only applies to Swissphone s.QUAD series C pagers which are connected via LTE to s.GUARD.

Time between notifications (seconds)

Time between push notifications in seconds.

Amount of notifications per episode

The max. amount of push notifications which will be sent to a recipient.

If set to 0, there will be no upper limit.

iOS critical notifications

If enabled, the push notifications will be sent to the iOS application as "critical notifications". This means that mute and not disturb modes on the iPhone will not be taken into account.

Always on top

If enabled, the desktop client will always remain on top of other applications after receiving an incoming episode. It is not possible to bring it to the background.

Note: this setting applies only to the desktop client

Maximize application

If enabled, the window of the desktop client will be maximized after receiving an incoming episode.

Note: this setting applies only to the desktop client

Allow lock screen (after timeout)

If enabled, after receiving an incoming episode and after the timeout expired, the user will see the Windows lock screen. If he logs in again and the episode is still active, he will immediately be shown the lock screen again.

Note: this setting applies only to the desktop client

Lock screen timeout (sec.)

Timeout in seconds for the setting "allow lock screen (after timeout)"

Note: this setting applies only to the desktop client

Allow lock screen (on close)

As soon as the episode is closed, the Windows lock screen will be shown to the user. He will have the possibility to log in again.

Note: this setting applies only to the desktop client

Allow lock screen (after confirmation)

As soon as the user confirms the episode, he will be shown the Windows lock screen. He will have the possibility to log in again.

Note: this setting applies only to the desktop client

Show location

Display a map (Google Maps) in the s.GUARD applications. The location where the activator was located when activating the episode is marked on the map.

Show activators location

Display a list with the recent locations of the episode activator within the s.GUARD applications. This can include both GPS coordinates and location information coming from Bluetooth beacons.

Show emergency instructions

If enabled, images (gif, png, jpg) which are assigned to this event will be displayed to the recipients of the episode.

Best practice: assign instructions or floor plans.

Upload emergency instructions

Allows to upload images which will be shown to the recipients of the episode (see above).

Already uploaded images can be reviewed and deleted.

Note: it is possible to upload different images for each language.

Event message

The message which is sent to the recipients when an episode is activated.

The messages are separated by channel. It’s possible to define different messages for each channel.

Best practice examples:

• Use placeholder ~message~ to display an ad-hoc text.
• Use ~reactionUrl~ to include a link where the recipients can give a reaction to an active episode.
• Use ~reactionCode~ to send a list of possible response codes within an SMS.

Use acronyms

If enabled, any acronyms which are contained in the message will be resolved according to the configuration in the Settings.

Use HTML

If enabled, a WYSIWYG editor will be displayed for the Application and Email Content event messages.

Push notification

The text of the push notification which will be sent to the s.GUARD applications.

The push notification texts also support all placeholders.

On / Off

If enabled, the s.GUARD applications will ask the user to enter an alert message when activating an episode.

Ad hoc event message

Default text for event message. Can be edited during activation.

Ad hoc user selection

If enabled, the s.GUARD applications will allow the user to choose which recipients (users / user groups) shall be notified when activating an episode.

Note: only recipients which are assigned to the event can be selected during episode activation.

Without interaction, activate event with pre-defined text after (sec.)

If the user does not enter an ad-hoc text / does not confirm the ad-hoc user selection, the episode will start automatically after expiration of the configured time.

0 means that no episode will be started automatically at all, the application will wait indefinitely for the user to enter the text / select the users.

Ad hoc Event countdown duration

Additional countdown which will start after entering the ad hoc message / confirmation of the ad hoc users.

Request action

Soundfile which will be played to request the recipient to perform an action. If specified, this soundfile will be used instead of the TTS prompt.

Soundfiles can be specified either by file upload or URL.

Message

Soundfile which will be played as message text to the recipient. If specified, this soundfile will be used instead of the TTS message.

Soundfiles can be specified either by file upload or URL.

Request security code

Soundfile which will be played to request the recipient to enter the security code. If specified, this soundfile will be used instead of the TTS prompt.

Soundfiles can be specified either by file upload or URL.

Text before safety code

If a safety code is configured in the event settings, this text will be read to the user before the safety code prompt.

Text after safety code

If a safety code is configured in the event settings, this text will be read to the user after successfully entering the safety code.

File

Instead of specifying a text (TTS), it is also possible to upload a soundfile for both scenarios.

Header

If specified, this text will be used as header of the reaction page, in case the user reacts by clicking on a ~reactionUrl~.