Enabling the web callback template for callbacks

After you create a web callback request page, you need to enable your web callback page to generate callback requests for your queues. This is done by adding an application pool for web callbacks and adding web callbacks as an application for your website in IIS and specifying in config.js which web callback workflow to use. Optionally, the default messages contacts receive after successfully submitting a callback or if their callback request fails to submit can be changed.

Before the procedure, you must have
To enable the web callback template for callbacks
  1. Add the web callback application pool and configure the application settings
  2. Add the web callback as an application to your website
  3. Set the Enterprise Server for callbacks
  4. (Optional) Change the default web callback subroutine
  5. (Optional) Change the default success and failure messages
To add the web callback application pool and configure the application settings
  1. Start IIS Manager.
  2. Under Connections, select Application Pools.
  3. In the Actions pane, select Add Application Pool….
  4. Under Name, add a name for the pool.
  5. Under .NET Framework version, select the most recent version of .NET Framework 4.5.
  6. Under Managed pipeline mode, select Classic.
  7. Click OK.
  8. Select the Application Pool and in the Actions pane, select Advanced Settings….
  9. Configure the settings to match the figure below.
    Figure 1. Web callback Application Pools Advanced Settings


  10. Click OK.
To add the web callback as an application to your website
  1. Start IIS Manager.
  2. In the Connections pane, navigate to Default Web Site.
  3. In the Actions pane, click View Applications.
  4. In the Actions pane, click Add Application….
  5. Under Alias, provide an alias.
  6. Click Select….
  7. Select the web callback application pool and click OK.
  8. Under Physical path, click … and navigate to the folder containing web.config and click OK.
  9. Click OK.
To set the Enterprise Server IP address for callbacks
  1. Navigate to config.js and open in a text editor.
  2. Locate the following line of text:

    var Config.EnterpriseServerAddress = "localhost";

  3. Replace localhost with your Enterprise Server's IP address.
  4. If the Enterprise Server was configured to use SSL during installation, locate the following line of text:

    var Config.EnterpriseUsingSSL = false;

  5. Replace false with true.
  6. Save and close the text editor.
To change the default web callback subroutine
  1. Navigate to config.js and open in a text editor.
  2. Locate the following line of text:

    var Config.OutboundCallbackSubroutineID = "B0AA4E0E-A97D-461E-A7F9-E32026C1FA40";

  3. Replace the value with the GUID of the subroutine from SQL.

    The GUID can be obtained from tblConfig_VWM_Subroutine in SQL. See the procedure below for instructions on how to obtain this information.

  4. Save and close the text editor.
To obtain web callback subroutine information from SQL
  1. Open SQL Server Management Studio or another SQL Management program.
  2. Query the following select statement:

    select Pkey,Name from tblConfig_VWM_Subroutine

  3. Find your value for your web callback subroutine.
To change the default success and failure message for the web callbacks
  1. Navigate to config.js and open in a text editor.
  2. Locate the following lines of text:

    var Config.SuccessMessage = "Thanks, we will get in touch with you shortly.";

    var Config.FailureMessage = "Sorry, we are having difficulties right now. Please try again.";

  3. Replace "Thanks, we will get in touch with your shortly." with the desired message for a successful callback submission.
  4. Replace "Sorry, we are having difficulties right now. Please try again." with the desired message for a failed callback submission.
  5. Save and close the text editor.
Parent topic: Configuring the web callback template