[cisco-voip] [External] IPCC best practice

[Charles Goldsmith]

Agreed with TIm, it's just simpler to involve less systems if you can.
With 12.0 UCCX and higher, the calendar function is a nice addition, no
more XML files for schedules.

On Wed, Aug 19, 2020 at 7:37 AM Johnson, Tim <johns10t at cmich.edu> wrote:

> It seems to me that there's not a "best practice" label for most
> scenarios. When I started with UCCX, we went to a call handler first to
> provide us with an easy way to provide a schedule, and a familiar way for
> the customer to record a greeting. Later, we ended up building the schedule
> into our script and directing calls to the trigger. That's my preference,
> just to involve less systems.
>
> Tim Johnson
> Voice & Video Engineer
> Central Michigan University
> Call me: +19897744406
> Video Call me: johns10t at cmich.edu
> Fax me: +19897795900
> Meet me: http://cmich.webex.com/meet/johns10t
>
>
> -----Original Message-----
> From: cisco-voip <cisco-voip-bounces at puck.nether.net> On Behalf Of
> fred at browardcommunications.com
> Sent: Wednesday, August 19, 2020 8:19 AM
> To: cisco-voip at puck.nether.net
> Subject: [External] [cisco-voip] IPCC best practice
>
>
> Hello, I just have a quick question.
> When setting up a call center for a SMB, Is it best practice to have the
> main number go to a unity call handler 1st, with caller input going to uccx
> triggers, or is it considered best practice to have the main number go
> right to CCX?  I have seen both ways.
>
> Thank you.
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200819/9686bdd2/attachment.htm>