If you haven't read part 1, you should probably start there! http://blog.datalicious.com/call-center-tracking-using-omniture-site-cata
Where to begin setting this up? As with all analytics and tracking, there are many ways to approach the problem, but below is our preferred solution as it fits so easily with the existing online architecture. If call centre staff are indeed able to use a modified version of the online store, the steps below will slash wasted time, improve call to sale conversion as well as bring your phone and online tracking together into a single reporting view.
Step 1 - The basic linkConfigure your call center software such that an answered phone call will trigger the opening of a URL. To avoid opening lots of new windows, you should give the window a name, if the name is the same, each call will trigger in the same window.
Step 2 - Where the magic happensCall center software has access to lots of information, the number dialed, the callers number, who answered the call, the time the user has waited in the queue, any menu selections, the calls unique ID, etc. There is no limit to what is available. You need to look at all the information and decide what is relevant (both for tracking and sales optimisation). Once you've decided what is relevant, you need to pass this information in the URL triggered when a call is answered. Example below:
http://callcentre.example.com/redirect.php?cc=yes&caller=5551231234&dialed=1800123123&id=1234567890&queue=350&agent=samsmith Step 3 - Now what?So you've completed the most important step, you've passed all the key information seamlessly between two previously independent systems. Now it's time to use it. The redirect.php is a script written to deal with the information passed. This is not only for capture in Site Catalyst, but also for directing the Agent straight to the right product or content to save time. This happens effectively instantaneously.
Examples:- Take the sales agent straight to the product page associated with the number dialed.
- Apply appropriate discounts based on known customer information
- Populate fields with customer information to save time
Step 4 - What about the tracking?
The redirect script will send the agent to the appropriate page with all the appropriate site catalyst data as URL parameters. You can then use the
getQueryParam plugin to extract these parameters and direct them into the correct Site Catalyst variables.
Typically an Agent will sit on their computer all day, that's no good as the one session will stay alive. To start a new one in Omniture for each call, set the visitor ID to be equal to the unique ID of the call. This will ensure each call appears as a visit in your reports. Usually you would put this ID into an eVar as well, so you can use classifications to import additional data later.
To differentiate call centre traffic to the online traffic, set an eVar and persist it (you must have the get and persist plugin installed), this will allow you to break out call centre traffic with a vista rule later if required. All your Agents traffic will be marked.
Some information you'll want in eVars: Typically i would put the Agents name, the number dialed and any customer ID as a first start. Products, Events on the modified call center interface should follow the logic of online where possible, so they can be easily compared, ie checkout, order, registration, etc.
Before you know it, you'll have some very rich information on your call center. This is only the beginning though, some more advanced segmentation and targeting techniques will be discussed in part 3, along with data imports to close the information loop.
Comments [0]