Introduction

The secure messaging service enables a tenant to securely interact with their recipients. It enables this by providing:

A stand alone application that allows a user (with an admin role) to send and receive messages.
API and UI components that facilitate other DTP applications the ability to leverage the service.
A tenant API to allow non DTP applications to leverage the service.

Recipients can be messaged through four different message types (Known as Recipient Type).

Authenticated - The recipient receives an email notifying them they have a secure message and can then access the platform using an identity provider (such as username and password, IMOS, Government Gateway etc.).
Organisation - The recipient receives an email notifying them they have a secure message and then using an Organisation Portal can view the secure message. Organisation messages can optionally be sent 'Organisation Wide'.
SMS Verification - The recipient receives an email notifying them they have a secure message and then must authenticate with a verification code sent via SMS to their mobile phone.
Email Verification - The recipient receives an email notifying them they have a secure message and needs to authenticate with a verification code sent to their email inbox.

Once verified, the recipient can view the secure message. The Admin user, is then able to see the 'status' of the message such as;

'Sent': The admin has sent a secure message to a recipient having used the recipient email and telephone number.
'Read': The recipient has successfully verified their identity and opened the message.
'Response Submitted': The recipient has replied/responded to the secure message. This is an optional function, that can be managed by the Admin in the message configuration menu.
'Complete': Once the communication between the recipient and admin has ended, the message thread can be marked as 'Complete', this disables the reply option on the recipient side of the message thread.

Recommended when sending secure messages to external recipients where credentials are known (such as login ID, Government Gateway ID, IMOS ID etc.), enabling them to be identified. This recipient type is suited to secure messages that have repeated individual recipients, require a message history and messages that require more rigorous verification.

Recommended when sending messages to individuals/multiple users within configured organisations. A configured organisation will have its own platform portal, enabling users to login and view the secure messages. It can be used to send messages to an entire organisation 'send and forget' or individuals within an organisation. This recipient type also facilitates a message history and is a equally secure form of verification as authenticated.

When sending secure messages to external recipients such as members of the public and where basic information is known. This recipient type is suited for sending 'one-off' messages to external individuals. Closed loop messages are commonly used in this recipient type.