ARCOS Platform Enhancements
IdeaBank: Added “Alerts via SMS” Option
What is changing:
ARCOS has updated the Alerts functionality to allow users with Verified SMS enabled devices to receive Alerts via SMS messaging. The previous SMS option, email2SMS gateways (“phonenumber@vtext.com”) could take hours to deliver if at all, depending on the wireless carrier. This update is a more reliable alternative to ensure delivery of SMS Alerts.
NOTE: Users who enable this option for a phone number AND that same phone number set up to receive an SMS via the email2SMS gateway will receive two SMS messages. To receive True SMS messages only for a phone number, delete the email address associated with email2SMS gateway set up and check the Alerts via SMS box.
The “Alerts via SMS” option appears within the Device Information section of the Employee Modify page
as well as the Devices section on the My Account page for users who have a Verified SMS enabled device.
Mobile users can enable from their device in the My Account > Devices > Edit Device page.
Administrators can enable “Alerts via SMS” using HRI1 202 records by setting the value to “1”.
Users can also enable “Alerts via SMS” by send/updating via API. The employee endpoint smsAlerts has been added to the basic GET and PUT methods. Set the value to “1” to enable.
Once enabled, users who have been subscribed to Email Alerts will receive the alerts via SMS. This is to
replace the email to SMS capability that customers have been using (example: number@vtext.com).
NOTE: The changes for SMS Alerts will be deployed to QA in the 23.22 (5/19) and will be deployed to
Production in the 23.24 (6/15). The 23.24 release will also include updates to the SMS Conversion Report,
stay tuned.
Who is involved:
This feature is being enabled for all customers that currently have SMS enabled.
What you need to do:
No further action is necessary to implement this change.
ARCOS Callout Enhancements
Enhanced Employee Release CallBack Logic
What is changing:
ARCOS has enhanced Employee Release Callback logic. The initial call will be closer to the time that was set up when this was implemented. Prior to the change employees were receiving the callback 30-40 minutes before the configured callback window.
For example, if the Employee Release Callback rule is setup to call the employee back after 2 hours within
minutes of their window (maybe before or after):
Employees will continued to be called back an hour later, if they don’t answer the initial call. If an employee answers and says they’re still working, ARCOS will call back 4 hours later, as it does today.
NOTE: Updates only include the timing of the CallBack; functionality remains the same.
Who is involved:
All ARCOS customers using the Employee Release CallBack feature will receive this update. Contact Professional Services to add Employee Release CallBack functionality.
What you need to do:
No further action is necessary to implement this change.
ARCOS API Enhancements
Updated Crew Sync API
What is changing:
ARCOS has updated the cm/sync/crews/ API call to include the following results:
• WebID
• VruID
• Email1
• Phone1
Example:
<member crewld="17443" id=" 16649" name="Tester> Ra" webld="ratester2" vruld="86425" email="ksol- got@rostermonster.com" phone="(111) 111-1111 ">
The Email is taken from the user’s account email address. If an account email address is not listed, then we return the email address in the email1 field.
The Phone is device in call order sequence 1.
Who is involved:
All ARCOS API will receive this update.
What you need to do:
No further action is necessary to implement this change.
Comments
0 comments
Please sign in to leave a comment.