HowTo: Set up a custom chat request page

INFORMATION

MiCC Web Chat comes preconfigured to use a pre-chat page to capture a user name, email address, and an optional topic to request a chat. The user name and email address are required, and as stated, the topic is optional.

You may have a system in place that has already captured this information in order to have a user logged in to your website/application and as such would like to forgo having your users have to re-enter this information if/when they want to engage in a chat.

To this end, the preconfigured pre-chat can be bypassed via some configuration and then submitting the correct query string parameters to the chat system.

CONFIGURATION

Open up your chat client configuration file and edit the following 2 parameters for either the default configuration and/or whichever queue configurations you have setup that you want to by-pass the pre-chat page for.

1. Locate the "UsePrechatArea" parameter and set it to "false". This parameter tells the system not to render the pre-chat page.

2. Locate the "PrechatDataFromUrl" parameter and set it to "true". This parameter tells the system to look at the chat request url and validate that a name, email and optional topic are present in the url to be used to request and render a chat.

NOTE: in 8.0 the chat client configuration file in CCMWa is called Chat.public.config.DEFAULT.js and in 8.1 it is called chat.public.config.js.

URL SUBMISSION

Configure your website/application to render the chat request url with the required parameters. A request to the ccmwa chat url will require the queue id, along with the name, email, and optional topic. For example, if your website was www.wickedtix.com and was fully configured for MiCC web chat, then the url submission for user jon at myaddress@wickedtix.com would look like this:

http://www.wickedtix.com/ccmwa/chat/26F1A5C3-DD2C-45FF-BE75-2BC7B85012D0?name=jon&email=myaddress@wickedtix.com&topic=Something%20to%20talk%20about

NOTE: If you omit to include a topic in the url, ensure the "RequireTopic" parameter in your client chat configuration is set to false. If it is set to true, then you will need to pass this in as well.

APPLIES TO

MCC Version 8.0 and newer