Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Scroll export button
scopecurrent
template-id0fa09813-8b86-460a-aa1d-ef450a80e9ce
quick-starttrue
add-onScroll PDF Exporter

...


DeviceBackOfficeHelperHopperSalesFloorHopperSalesFloorHopper + AISuperHopper + AI
Ideal for: For SIP devicesAdministration and support users who don't face customers Customer care, contact center, users who need access to integrations Retail assistants who work on the shop floorRetail assistants who work on the shop floorManagers and supervisors
Free minutes for outbound calls100 min3000 min3000 min3000 min3000 min3000 min
SMS included100 sms200 sms1000 sms1000 sms1000 sms1000 sms
Chats and videoconferencing
Using x-bees apps
Adding guests to conversations
Integrations
Personal contact-me link, meeting scheduler, website widget
Website widget setup
Max number of devices / callsUp to 1 device / 2 callsUp to 10 devices / 4 callsUp to 10 devices / 8 calls

Up to 10 devices / 8 calls 
(max 2 calls on DECT headset) 

Up to 10 devices / 8 calls
(max 2 calls on DECT headset)

Up to 10 devices / 8 calls 
Contact center events logging
DECT headset included
Internal broadcast channel

Customer service powered by AI prompts

Wallboard and analytics


Note

Note:

  • Before WMS Beta 6.04.20230920.1:
    You need to assign "Business" license to all the users who need "x-hoppers-SalesFloorHopper" and "x-hoppers-SalesFloorHopper_AI" licenses.
    Possibility to assign all types of x-hoppers licenses on PBX for each single user is coming soon. 

  • Starting from WMS Beta 6.04.20230920.1:
    The relevant licenses can be assigned to users via WMS -> Users -> Edit user -> License type field. See more in PBX Licensing and Activation - Admin guide (section "Assign correct license type to each user").

    Warning

    Current limitation: Users that have x-hoppers-HelperHopper / x-hoppers-SalesFloorHopper + AI licenses, need to be assigned x-hoppers-SalesFloorHopper license in WMS.


...

  1. The user is asked to say their name
  2. The user should pronounce the name and surname
  3. The system looks for the user and assigns the headset to the user

Each time the headset is placed into the charger, it gets unassigned and gets Service license type in the system. 

Note

Important: For the feature to start working on the headsets, follow one of the following procedures:

a) After enabling the feature, when using the headsets for the first time, users need to lift the headsets from the charger -> place into the charger -> lift from the charger again.

b) Alternatively, before performing the upgrade and activating the feature, unassign headsets via WMS (Devices -> choose device and click Assign to user -> in the Extension field, choose “unknown”). Then, when users lift the headsets from the charger, they need to press the Call button first.  

Enable user verification by voice

Also, you can configure the logic of verifying users' identity by voice footprintWhen this feature is enabled, during user authorisation the system compares the voice of the user with user voices previously saved in the system and in case of a match, allows authorisation. This eliminates the risk of user logging in under a different name.

See instructions for below:

Note

Note:

  • The support starts from WMS Beta 6.06

1. Install the specific libraries to enable verification of identity by voice using the following command: 

Code Block
pip install librosa

2. Set up a Dialplan to allow employees leave their voice footprints in the system, which will later be used for verification.

You can download the Dialplan example here: x-hoppers_auth.bkp

Once the Dialplan is set up, employees should call the number provided in the Dialplan and follow the audio instructions to record their voice footprints.

Note

Note: Each new employee should follow the procedure first, before trying to log in to the headset, as in case user voice footprint is missing in the system, authorisation will not be allowed.

2. Add the following variable to WMS -> Dialplan -> General Settings -> Set dialplan variables field and click Save:

Code Block
XHOP_VOICE_AUTH=yes 

Image AddedWhen the feature is enabled, upon lifting the headset, users are prompted to say their name and surname. The system matches the pronunciation with user records and assigns the headset. Each time the headset is placed into the charger, it gets unassigned and gets Service license type.


5. Configure Dialplan 

Modify the users dialplan as follows: 

...

Note

Note:

  • The support starts from WMS 6.03.20230630.3. 
  • The feature works only if there is an x-hoppers license available on the PBX.

...

Record in-store conversations (listen in CDR-View)

Starting from WMS 6.03.20230630.3, it is possible to record in-store conversations and listen them via CDR-View. The recording starts when user unmutes himself in the conference and begins talking.

...