Plan bundles for customers

To plan and determine the necessary bundle and feature requirements:

• Identify user types within potential customers and determine requirements for each user type.

• Design bundles with feature/phone type combinations that will satisfy your requirements of user types.

See tables for details:

• Table 1 Supported Phone Sets

• User Bundle Features by Service and License Type:

  • Table 2 MiCloud Business Virtual

  • Table 3 MiCloud Business Multi-Instance

• Phone Types by Service Type :

  • Basic IPT License

    • Table 4 Basic IPT MiCloud Business Virtual

    • Table 5 Basic IPT MiCloud Business Multi-Instance

  • Standard IPT License

    • Table 6 Standard IPT MiCloud Business Virtual

  • Table 7 Standard IPT MiCloud Business Multi-Instance

  • Entry UCC License

    • Table 8 Entry UCC MiCloud Business Virtual

  • • Table 9 Entry UCC MiCloud Business Multi-Instance

  • Standard UCC License

    • Table 10 Standard UCC MiCloud Business Virtual

  • Premium UCC License

    • Table 11 Premium UCC MiCloud Business Virtual

  • Contact Center Agent

    • Table 12 Contact Center Agent MiCloud Business Virtual

    • Table 13 Contact Center Agent MiCloud Business Multi-Instance

  • Table 14 Management Portal Administrator Bundle Features

Considerations

• User Bundle phone features are dependent upon the service type and license type selected for the type of user.

• Up to three phone types per bundle can be configured, depending upon the service type and license type selected for the type of user for the bundle.

  When you downgrade a user bundle from Management Portal, for example a user going from 3 phones down to 2, the MiCollab Client API will cause the user's status to be deleted and recreated. The user will need to log out of MiCollab Client, log in again and manually recreate their routing rules (set which devices will ring in different states).

• Phone types and feature profiles are also dependent upon the service type and license type selected for the type of user (see Table 2, “Phone Types by Service Type,” )

• When selecting UCC user bundles, and creating MiCollab Client Service users through Management Portal, Management Portal will strip out any domain names from the username field before saving it to MiCollab. However, the user will receive a welcome email from MiCollab Client Service with the login ID to be <username>.<Enterprise domain name>. It will be necessary to inform MiCollab Client Service users that they need only to log in with their user ID, not including the domain name.

• When MiCollab Client Service users have been created, and after being put in service, there is a subsequent change to a user or a service, that user will receive a logout request on their MiCollab Client application.

• When a MiCollab Client user changes their credentials in their MiCollab Client, and subsequently those credentials are changed within Management Portal, Management Portal will overwrite the credentials on the MiCollab Client for that user.

• If a MiCloud Business Multi-Instance user has been created (a SB Entry UCC Bundle) with Twinning, and the user's firstname, lastname, as well as their email address is edited via Management Portal, then their IMAP Account Login in the Voicemail tab must be changed manually in the Edit User form in the Management Portal customer admin portal if the Embedded UM Enabled option is selected.

• PC MiNet Softphone phone types are programmed on the MiCollab Client MBG.

• When users with MiCloud Business Virtual bundles are created, languages are set by default based on the MiCollab default language for applications such as MiCollab Client.

• When users with MiClould Business Mutli-Instance bundles are created, Management Portal can set the language for applications such as MiCollab Client because the MiCollab server is not involved in configuring those applications.

• Modifying a user with a bundle containing the Hot Desk or ACD feature to one with a non-Hot Desk or non-ACD feature is not permitted. Modifying a user with a bundle containing a non-Hot Desk or non-ACD feature to one with a Hot Desk or ACD feature is not permitted. Only changes between non-Hot Desk or non-ACD bundles, as well as bundles that contain the Hot Desk or ACD features are permitted.

• Users assigned bundles with Mobile Softphone, PC Softphone, Generic SIP, Hotdesk, or ACD Phone Types will not have their Call History display within their Management Portal page.

• Provide access to site administration features on the portal.

• Determine the Class Of Service (COS) numbers that will be used for each Feature Profile (determine Day/Night1/Night2 service).

• Record the Feature Profiles with COS numbers and feature combinations for each Feature Profile.

  Tip

  Part of designing a bundle is to design a Feature Profile that will define the phone set features that a bundle will provide to the assigned user. A Feature Profile is essentially registered as a Class of Service (including Day/Night1/Night2 time of day settings).

Table 1 Supported Phone Sets

User Bundle Features by Service and License Type

Table 2 MiCloud Business Virtual

Table 3 MiCloud Business Multi-Instance

Phone Types by Service Type

Table 4 Basic IPT License - MiCloud Business Virtual (MLB)

Table 5 Basic IPT License - MiCloud Business Multi-Instance

Table 6 Standard IPT License - MiCloud Business Virtual (MLB)

Table 7 Standard IPT License - MiCloud Business Multi-Instance

Table 8 Entry UCC License - MiCloud Business Virtual (MLB)

Table 9 Entry UCC License - MiCloud Business Multi-Instance

Table 10 Standard UCC License - MiCloud Business Virtual (MLB)

Table 11 Premium UCC License - MiCloud Business Virtual (MLB)

Table 12 Contact Center Agent - MiCloud Business Virtual (MLB)

Table 13 Contact Center Agent - MiCloud Business Multi-Instance

Table 14 Management Portal Administrator Bundle Features