Release 22.04 of CareAR Assist delivers the following new features and capabilities:
- Enhancements to Join by Session Code
- UI/UX Enhancements
- Web API Enhancement
Enhancements to Join by Session Code
Within Application Join with Session Code
There are two options that are now supported
- Join by session code without authenticating. In this scenario, the user either has no Assist account or does have an account but has chosen not to login. We will present the opportunity to input session code at the top-level screen prior to login; and
- Join by session code after logging. This capability is for the user who has already authenticated and is logged into the Assist app. The typical use case is the field service use case.
There will be no fundamental change in the way the session code is shared with the guest or in the flow that a user executes to join a session using a session code.
Changes to the Session Code
We’ve extended the session code from four characters to six characters. Also, with the six-character session codes, the alpha characters are now case insensitive; this will make it easier to verbally communicate the session code.
Session Code Entry at Join Page
We updated the “join” page that’s served up at https://carear.com/join to accommodate the six-character session code.
Note that the Next button is made available once exactly 4 or 6 characters have been entered.
These enhancements and changes to the session code benefit customers in the following ways:
- Users who wish to use the Assist native app and join a session they’ve been invited to can join by session code by interacting with the app to enter the session code and avoid the join page at https://carear.com/join.
- Users can launch the app and then immediately enter the session code.
- The lengthened session code improves security for our services.
- With the session code no longer being case sensitive, it’s simpler for host users to communicate to guests and it’s easier for guests to enter the session code.
We expect that there will be users hosting sessions using previous releases of the app where the session code generated has four (4) characters. We will honor and process the previous format of the session code in this release.
Copy/Paste Session Link
Hosts can retrieve link to the session from the Participants screen while in a live session, copy it, and paste it into alternative messaging applications (e.g., Teams, iMessage, or WhatsApp) to invite guests. The benefit to host users is easy retrieval and distribution of a session code using an application other than email or SMS.
Display QR Code
When a session host also wants to join the session using smart glasses, they can display the QR code for the session from the Participants screen while in a live session. The benefit to host users is that they can more easily and quickly join a session using smart glasses.
Support for Mobile Numbers with Separation Characters
We’ve loosened the input requirements on mobile numbers to allow for separation characters (i.e., “.”, “ “, or “-“) to be entered. This is especially helpful when copying and pasting the mobile number from another application, like a CRM or service management tool.
Updated Recording Notice
We revised the recording notice (the message all users in a session see) that’s popped up when a session recording is started to read as follows:
This session is being recorded. By continuing to participate, you are consenting to being recorded and you agree not to use this app to film or record video or audio of any people except for the participants in this session.
Auto-Close Session for Host
Once a session is ended by the host, Assist now returns the host to the home screen automatically after 5 seconds. A visual countdown timer is presented to the host to indicate the time remaining before the action. This benefits the host who may not know that a simply clicking on the background screen will return them to the home screen.
CareAR Web API Enhancement
We have updated the CareAR Web API to allow the callbackURL to be base64 encoded. While we will accommodate a text encoded URL, we recommend that developers implementing third party integrations to use this updated encoding method.
The benefit to third party developers is that they no longer have to register their callbackURL with CareAR operations.
This update is not a breaking change to the CareAR WebAPI. Third party integrations (i.e., “Custom WebAPI Connectors”) implemented prior to release 22.04 will continue to function in this release.