Chat with us if you have any questions!

Frequently Asked Questions

To send a link to a specific FAQ, add ?faq=[number] to the end of the URL. Example:

Chime FAQ

Verify SQL authentication

  1. Open SQL Server Management Studio with an account that has admin privileges to the server instance
  2. Connect using Windows Authentication
  3. Right-click on the SQL Server instance name and click Properties
  4. Select the Security page
  5. Under Server authentication, verify that SQL Server and Windows Authentication Mode is selected
  6. Click OK
  7. Expand Security
  8. Expand Logins
  9. Right-click on 'sa' and click on Properties
  10. On the General page, set the SA password to something that you can remember
  11. Click on the Server Roles page and verify that 'sysadmin' is selected under Server roles
  12. Click OK

Setup SQL for remote connections

  1. Open SQL Server Configuration Manager
  2. Under SQL Server Configuration Manager (Local), expand SQL Server Network Configuration
  3. Select 'Protocols for [SQL_instance_name]'
    ex: 'Protocols for SQLEXPRESS'
  4. Enable 'Named Pipes'
  5. Enable 'TCP/IP'
  6. Right-click on 'TCP/IP' and go to Properties
  7. Click on the 'IP Addresses' tab
  8. For all sections verify the following:
    TCP Dynamic Ports: None, no data
    TCP Port: 1433
  9. Click OK
  10. If you receive a warning message that the changes won't take effect until the service is restarted, click OK
  11. Under SQL Server Configuration Manager, click on SQL Server Services
  12. Right-click on 'SQL Server [SQL_instance_name]
    ex: 'SQL Server (SQLEXPRESS)'
  13. Click on 'Restart'
  14. If restarted successfully, you can close SQL Server Configuration Manager.

Setup Firewall Exception for SQL

  1. Open Network and Sharing Center
  2. Click on Windows Firewall
  3. Click on Advanced Settings
  4. On the left-hand side, click on Inbound Rules
  5. Click on 'New Rule'
    When the New Inbound Rule Wizard comes up, do the following:
    1. Select 'Port' for the Rule Type
    2. Click Next
    3. For Protocol and Ports, select TCP
    4. Select 'Specific Local Ports', and specify 1433
    5. Click Next
    6. For Action, select Allow the connection
    7. Click Next
    8. For Profile, select all three (domain, private public)
    9. For Name, specify the name of the rule
    10. Click Finish
  6. Verify that the new rule shows up in Inbound Rules and verify that the port number is correct
  7. You can exit Windows Firewall.

Instant Chime does leverage the Microsoft Lync® UCMA APIs, but does not require a trusted app configuration. Our Chime ‘queues’ login on behalf of a named Lync® entity (i.e. a SIP enabled user in Active Directory) so each queue will require a unique SIP login to Lync®. However, since our queues access Lync® via these named entities, we call the SIP users dispatchers, then Chime does not require a complex trusted application configuration.

If you are getting a SIPEPS error when accessing the application, the most likely cause is the absence of the UCMA 4.0 Runtime APIs. You can download the installer from Microsoft® here.

If you receive a 403.14 error after installing Chime on Windows Server 2008R2, it may be an issue related to ASP.NET referencing the .NET 2.0 framework when it needs to reference the .NET 4.0 framework.

This problem can be solved by updating the script maps. See MSDN ASP.NET IIS Registration Tool for more information

We find that running the following commands in the command prompt on the server clear this issue quickly.

Note: This may update all applications to .NET 4.0

                                cd \
                                cd Windows\Microsoft.NET\Framework64\v4.0.30319
                                aspnet_regiis -ir

You can download the UCMA 4.0 Runtime from Microsoft® here.

Right now, Instant Chime supports Lync 2013® in an ‘on premise’ deployment. If you require Lync 2010® support, please contact our sales group and discuss your deployment and requirement.

One of the main benefits of Instant Chime is the ability for an agent to handle multiple chat requests at one time. Many of our customers configure their agents to handle 2 concurrent conversations at a time, however, this is an easy option to configure and agents may be configured to handle up to 5 concurrent conversations.

Yes – since Microsoft Lync® provides an excellent infrastructure for both application sharing, and video conferencing, Chime can escalate service desk request using both video and application sharing.

We have designed Chime with the core idea that it should take less than 30 minutes to IM enable a service desk – or help desk. So, once Chime is installed and configured, it does not require any additional programming to bring a queue online – and Lync® enable a help desk. Of course, many customers have requirements for customer web chat clients, interaction with existing CRM systems, or custom routing options, which may add some work to the enablement process.

This will be based on the number of agents behind each service desk queue and the number of inbound IM conversations. However, 30 queues per Chime server is a totally reasonable estimate – and this should be able to support a large scale enterprise service desk.

Yes – Chime provides multiple manager level dashboards as well as interactive charting and reporting modules. The Chime dashboards are designed to provide a line of business manager with a real time, and historical snapshot, of the queue and the service desk activity. With the dashboard, managers can easily view inbound IM traffic as well as trending topics (such as which problems are creating help desk requests).

Yes – many of our customers utilize ASA to calculate agent efficiency as well as Microsoft Lync® click to chat IM queue performance.

The Chime trial is a 30 day evaluation including all of the Chime features for up to 5 queues and 50 experts. At the end of 30 days your trial license can be easily converted to a purchase license without reconfiguring queues or losing data.

Chime comes with 15 standard reports including call volume by queue or expert, average speed to answer, first call resolution rates, and more.

Reports may be customized depending upon your organizational needs and whether the data is captured. Let the Instant development team know what type of reporting you are interested in gathering and they will determine the best course of action for reporting.

Yes, Chime dashboards visually display top keywords in a tag cloud to help managers identify the most common issues or identify any new topics that may emerge due to new tools or software deployed across the enterprise.

Each queue may be configured with customized canned messages for your enterprise. These may be displayed to the seeker or agent at a variety of engagement points in the conversation. For example, when a chat message is submitted, at specified time intervals when there is a gap in the chat conversation, based on most popular requests, and a when chat is ended to name a few.

Chime can support virtually any language. Chime allows you to define languages, and associate text resources for each language.

We recommend a dedicated server to host the Chime application server. This can be either physical, or virtual, and we support Windows Server 2008R and newer. We typically see Chime deployed on virtual servers and we use virtual servers internally (i.e. using Hyper V).

You don’t need to install any additional software on a front-end. We do have a Lync® Windows Client Extension setting that can be applied to each agent provisioned in the system. The Lync® CWE setting will allow Chime to position information about the seeker in a window attached to the agent’s Lync client.

You need to change the Server authentication from Windows Authentication mode to SQL Server and Windows Authentication mode. Here is an reference which shows the appropriate steps »

  1. Click the Queues tab
  2. Go to Queue Settings either from the queue's dashboard or by clicking the gear icon on the right side of the row for that particular queue.
  3. Click on the Advanced tab
  4. Click on the 'Edit this URL' button (only visible if you have enabled the Agent Context Window)
  5. You will see {ServerIP}/Chime/Session/SessionTools?sessionGuid={SessionGuid}
  6. You need to replace {ServerIP} with {ServerFQDN}. You can do this by simply deleting 'IP' and typing 'FQDN'.
  7. Once you have made the change and see {ServerFQDN}/Chime/Session/SessionTools?sessionGuid={SessionGuid} - press Save in the Text Editor
  8. Press Save in the Queue Settings
  9. Close the Queue Settings
  10. If necessary, repeat for any additional queues
Browser Manager Panel Web Client Agent Context Window Lync® Web App Support
IE9 1
IE8 1
IE7 1
Firefox 3
Chrome 3
Safari 1 3
iOS Safari - Mobile 2 1 3
iOS Safari - Tablet 3
iOS Chrome - Mobile 2 3
iOS Chrome - Tablet 3

1 Unable to send files and/or rate agent.

2 Small screen size causes some layout issues.

3 Opens in separate window.

See the media below for detailed instructions. Also see for more information.

Yes. Chime supports federated seekers and agents. Click here for a PDF of instructions.
No. Chime supports Skype for Business® which is not the same as Skype.
Currently there are 3 options:
  1. Use Chime Hub. Chime Hub is a cloud based service that acts as a proxy for your Chime deployment. It is easy to set up and use, but contains a subset of features and might not have everything you need.
  2. Set up a reverse proxy. Using a reverse proxy would allow your web client to have all of its features, but is a little more difficult to set up. Here is a PDF of the steps for setting up an Apache reverse proxy server.
  3. Stick a portal page in the DMZ. A benefit of this choice is it gives you the entire web client feature set, however, it is not as secure as the previous 2 options.
If we can assist with any of these options, please let us know at
Yes, this can easily be turned on by a Chime admin in the Admin Settings. Enabling Windows Domain Authentication will prompt web seekers to enter their Windows credentials before being able to use the web client. This setting is only tied to the individual web client, and will only take effect for any queues using that particular web client. In the Agent Context Window, agents will see an 'Authenticated' label in the Details tab next to the seeker's name and question.

  1. Go to Admin > Settings > Web Clients
  2. Click on the 'Edit Client' button for the web client you wish to edit.
  3. Check the box 'Authenticate Web Seeker using Integrated Windows Domain Authentication'
Yes! Just click the icon in the top-left corner of the page and select one of the three available backgrounds. That's it!
We have a great web page How to Deploy a Queue that has several examples of exposing the Chime web client (and more) in different ways.

Virtual Agents FAQ

This error is most commonly caused by the presence of the ExtensionLibrary.dll with your Virtual Agent in the Plugins folder. Check that C:\Program Files\Instant Technologies\Chime For Lync\Plugins does not contain the ExtensionLibrary.dll. If it does, remove this reference and reload the Virtual Agents.
By default, each Virtual Agent is given 3000 milliseconds (3 seconds) to perform its work. In other words, anytime Chime calls some method on the Virtual Agent, it's given 3 seconds to return or else it's disconnected. Since we don't want misbehaving Virtual Agents delaying a seeker from being connected with an expert, we disconnect Virtual Agents if they exceed their timeout limit. If you think your Virtual Agent needs more time to integrate with another service follow these steps to increase the timeout value:
  1. Use SQL Server Management Studio to view the Chime database
  2. Open Tables and right-click dbo.VirtualAgents > edit top 200 rows
  3. For the Virtual Agent you would like to increase the timeout value for change the Timeout value from 3000 to 5000 (3 to 5 seconds). This is the next recommended timeout value and works for all Virtual Agent SDK samples.
  4. These changes will take into effect immediately within the Chime system. You won’t need to restart.
Logging within a Virtual Agent can be tricky. Two different logging strategies are recommended. The first is logging from a Virtual Agent before it has been loaded into Chime. If your Virtual Agent integrates with an external system, this might be logging when you are authenticating with that system. These logs should be written to a local text file and should only pertain to the steps that are taken before the Virtual Agent has been loaded in Chime. After a Virtual Agent is successfully loaded in Chime, the IVirtualAgent.SetPluginManager method is called and a reference to the IPluginManager object will be passed to the Virtual Agent. After this point the second logging strategy should be used. The second strategy is to call the IPluginManager method LogMessageInChime. The advantage of this logging method is that the logs from the Virtual Agent will be seamlessly integrated with the Chime logs, which makes trouble-shooting easier. You can specify the level of logging as well (Error, Warn, Info, Debug) to make the messages more meaningful.