Skip to main content
Communication History Logs

Site administrators can view the status of communications sent to all users across the site

Charles Lynam avatar
Written by Charles Lynam
Updated over a year ago

HosPortal keeps a record of all communications sent to users, including direct emails, SMS messages, shift reminders and self-roster status updates. These are visible to all users about their own activity, and for site administrators to view the status of communications to all users at a site.

To review communications history

For a normal user: select 'Profile' under your name (see screenshot A) to see your own communications record. Then select the 'Communications history' tab (B)

For a site administrator: select the 'Communication history logs' tab on the Admin page to see any communications between to any users on HosPortal.

Filter for the communications you are looking for (C). You can filter by mode of communications (e.g. SMS and email), the message type (e.g. shift reminder, self-roster reminder), sender, recipient and date range.

Clicking on the message will show a copy of the message sent and some further transmission information.

Transmission confirmations

For emails HosPortal reports when an email was generated by HosPortal ('sent' - see screenshot D), when it was successfully delivered to the recipient and (providing the recipient's email client allows it to be tracked) whether the email was opened. These details are shown at the bottom of the message.

For SMS messages, HosPortal reports the sent and delivery times but cannot report whether the message was opened or read.

Self-roster communications

It is common for site administrators to want to confirm that users have had confirmation of the shifts that they were assigned at the end of a self-roster process. Self-roster reminders during the selection process and the confirmation emails at the end of the process will detail:

  1. each of the shifts that a user has selected

  2. each of the shifts that a user has been assigned by HosPortal's algorithm, if required to meet a quota

  3. performance against quota

  4. if the quota is not fulfilled, the gap to meeting the quota and a warning that this user is at risk of being assigned shifts later in the roster period if shifts become vacant.

Did this answer your question?