Cisco Courtesy Callback (CCB) and CCE Hours of Operations
A project from last year requested that CCB not be provided if the expected wait time (EWT) was longer than how long this group was going to be open. The other requirements was to try and do it without using a custom element so they could better support the application if I was no longer around. There were two challenges with this request. First, getting the hours of operations. Second, parsing through that data to figure out if the EWT would be greater than close time or not. This blog will not provide the whole solution, but it should give you enough to be able to piece things together to fit your needs.
Getting the Hours of Operations
Assuming you're running Contact Center Enterprise (UCCE/PCCE) 12.x, Cisco has an API to get the business hours using a GET request to https://{CCEAdminFQDN}/unifiedconfig/config/businesshour/ and using basic authentication you can see this:
[caption id="attachment_953" align="alignnone" width="833"] GET Request Business Hours[/caption]
Let's take a closer look at the payload. Let's focus on the two parts that are marked with ###.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><businessHour><refURL>/unifiedconfig/config/businesshour/5000</refURL><changeStamp>0</changeStamp><configuredStatus><status>0</status></configuredStatus><name>TestHours</name><runTimeStatus>1</runTimeStatus><runTimeStatusReason>Week Day open reason</runTimeStatusReason><specialDaySchedules/><timezone><refURL>/unifiedconfig/config/timezone/v2/5023</refURL><displayName>(UTC-06:00) Central America</displayName></timezone><type>1</type><weekDaySchedules><weekDaySchedule><refURL>/unifiedconfig/config/businesshour/5000/weekdayschedule/5000</refURL><changeStamp>0</changeStamp><endTime>17:00</endTime><startTime>09:00</startTime><dayOfWeek>1</dayOfWeek></weekDaySchedule><weekDaySchedule><refURL>/unifiedconfig/config/businesshour/5000/weekdayschedule/5001</refURL><changeStamp>0</changeStamp><endTime>17:00</endTime><startTime>09:00</startTime><dayOfWeek>2</dayOfWeek></weekDaySchedule><weekDaySchedule><refURL>/unifiedconfig/config/businesshour/5000/weekdayschedule/5002</refURL><changeStamp>0</changeStamp><endTime>17:00</endTime><startTime>09:00</startTime><dayOfWeek>3</dayOfWeek></weekDaySchedule><weekDaySchedule><refURL>/unifiedconfig/config/businesshour/5000/weekdayschedule/5003</refURL><changeStamp>0</changeStamp><endTime>17:00</endTime><startTime>09:00</startTime><dayOfWeek>4</dayOfWeek></weekDaySchedule><weekDaySchedule><refURL>/unifiedconfig/config/businesshour/5000/weekdayschedule/5004</refURL><changeStamp>0</changeStamp><endTime>17:00</endTime><startTime>09:00</startTime><dayOfWeek>5</dayOfWeek></weekDaySchedule></weekDaySchedules></businessHour>
The runTimeStatus tells us if the Business Hours are currently opened or closed and the next part tells us what the hours of operations are for each day. Based on your use case you an just use the runTimeStatus to make a decision to offer CCB, but if you need to check if EWT is greater than close time, then we need to do a bit of extra work.
Parsing Through the Data
First, using an action element you first need to convert the XML into an array:
At this point we have an array containing all the close hours, we have what time we closed today, and finally we have how many seconds from midnight we're going to close. Now you can make some calculations to figure out if you should offer CCB or not.
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.
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.
Remember when every vendor said AI's focus was not to reduce agent count? Well how about it reducing your agent license count?
Zoom CX is moving to one spend pool for seats, apps, and AI. A seat you can count. A draw-down pool is their meter, and renewals just got harder to justify.
A VC firm read 67 SaaS earnings calls and concluded AI is great for SaaS valuations. Anyway, the underlying numbers on outcome pricing and MCP growth are worth your time if you read past the pitch.
No comments yet