The ultimate goal of this deployment is for the client to be self sufficient in the process. The PMO will have limited involvement as support and Product Management will both assist new clients in these deployments. Below is a list of tasks that need to be completed by all parties and attached is a VISIO document covering order and responsibilities.

Add additional users – This person will be the initial user created on the system. They will be responsible for creating users to complete the remaining tasks to deploy the solution. Roles are available to limit the access granted to each individual user created.

Add a Premise Client – This person will input the server name where the Premise Client will be installed. This is typically the VHT server that hosts the VHT Platform Toolkit web service. They will also download the credential file to provide to the VHT engineer to place on the server.

Create Widgets – Widgets will need to be created in the system. The widget will tie the code that is ultimately embedded in the site with a template that controls the look and verbiage of the offering as well as the segment that will be used for routing the call.

Create Templates – Templates control the look and verbiage of the offerings that are presented on your website. There are defaults available, but you will likely want someone familiar with HTML and CSS to provide formatting tweaks to make the offering appear seamless on your page. They will be able to preview the offering on your actual page without it being visible to the public. A business resource may be desired to review and approve the look and verbiage of the offering.

Assign Templates to Widgets – Once a template is created and it is identified which widget it should be assigned to; it will need to be selected in the widget configuration. This is often completed by the person that creates the templates.

Assign Segments to Widgets – The system needs to know where to route the callbacks. This is done by assigning a segment that is used in VHT Callback to the widget. Often times, this association is made by someone from Telephony Operations or an employee that is familiar with the DNs that are in use with VHT Callback.

Test Widget – The templates have likely been tested already, but it is desirable to preview the actual widget on the page. As with the templates, this can be done without it appearing to anyone browsing the site and is only visible in the browser of the person reviewing it. Unlike the template preview, this is a real widget that will allow calls to be added to the VHT system. Any callbacks requested from it will be routed to their appropriate DN and agent.

Embed Widget Code – Once all parties are happy with the look and functionality of the widget, it will need to be embedded into the actual web page. This is typically done by whoever administers changes to your website.

This is what was achieved and what was omitted in this how-to.

CloudConversationBridgeDeployment.vsd