Determine Busy Hour From UCCE TCD

The busy call hour is a valuable piece of information in order to forecast how many phone lines you’re going to need as well as how many agents, however getting this information can be difficult and then ensuring that it’s accurate is a whole other matter.  Recently I ran into an issue and I wanted to get the busy hour for myself.  I don’t have any access to the provider records, so all I have is the TCD table… when all you have is a hammer the whole world looks like a nail.

First, I turned to Google, which pointed me to how to get the calls per second.  This is good information as you would imagine that the highest CPS would fall during the busiest hour.  The query mentioned is:

SELECT Time=CONVERT(char,DateTime,108), CPS=CONVERT(decimal(5,2), RouteCallDetailTo5/300.0)
FROM t_Logger_Meters
WHERE DateTime BETWEEN '01/01/2013 00:05' AND '01/02/2013 23:59'
ORDER BY Time

Second, I opened up SQL Studio and began running some queries and came up with the following:

SELECT DATEPART(HOUR, DateTime) AS [Hour of Day], COUNT(distinct RouterCallKey)
FROM t_Termination_Call_Detail
WHERE DateTime > '01/01/2013 06:00' and DateTime < '01/01/2013 20:00'
GROUP BY DATEPART(HOUR, DateTime)
ORDER BY DATEPART(HOUR, DateTime)
 
This query assumes that every new call will receive its own RCK, so we can use this as our counter.  Next, the query breaks up the select statement by hour.  Finally, put the output in Excel and make a pretty graph.  Some caveats, this is very generic and over counts.  It doesn’t care about transfers, outbound calls, etc.  Next, the query doesn’t look at the routing client, so if you have a lot of UCM generated calls this might not help you very much.
~david

No comments yet

On Bluesky

@dmacias.bsky.social on Bluesky

David Macias@dmacias.bsky.social

Anyone actually seen an outcome-based contract from a BPO or a CCaaS vendor? Those documents must run to encyclopedia length, no room for error on what an outcome is or how it's measured. Maybe the only ones winning this AI race are the lawyers.

1 reply · View on Bluesky

David Macias@dmacias.bsky.social

Magic Quadrant poll results: 23 votes, 15 leaned disagree, 8 agreed. The 2026 quadrant does not match the reality most of my network sees.

1 reply · View on Bluesky

David Macias@dmacias.bsky.social

New Five9 survey: 46% of customers rated their last chatbot experience positively, vs about two-thirds for a human. The top reason people bail on the bot? It repeatedly misunderstood them. Turns out the human exit isn't the failure mode, it's the feature.

1 reply · 1 like · View on Bluesky