nt from my iPhone
>>>>
>>>> On Aug 19, 2020, at 9:16 AM, Lelio Fulgenzi wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>&g
;
>>>
>>>
>>>
>>>
>>>
>>> +100 for Anthony!
>>>
>>> 😊
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *From
>>>>> Sent from my iPhone
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Aug 19, 2020, at 9:00 AM, Matthew Loraditch
>>>>> wrote:
>>>>>
>>>>>
>>>>>
443.541.1518* <443.541.1518>
>>
>> w: *www.heliontechnologies.com* <http://www.heliontechnologies.com/>
>>
>> |
>>
>> e: *mloradi...@heliontechnologies.com*
>>
>>
>> <http://www.heliontechnologies.com/>
>>
>
gt; From: Anthony Holloway
>>> Sent: Wednesday, August 19, 2020 10:48 AM
>>> To: Lelio Fulgenzi
>>> Cc: Matthew Loraditch ; Charles
>>> Goldsmith ; cisco-voip@puck.nether.net
>>> Subject: Re: [cisco-voip] [External] IPCC best practice
>>>
>
nt:* Wednesday, August 19, 2020 10:48 AM
> *To:* Lelio Fulgenzi
> *Cc:* Matthew Loraditch ; Charles
> Goldsmith ; cisco-voip@puck.nether.net
> *Subject:* Re: [cisco-voip] [External] IPCC best practice
>
>
>
> *CAUTION:* This email originated from outside of the University of
>
Charles Goldsmith
> ; cisco-voip@puck.nether.net
> Subject: Re: [cisco-voip] [External] IPCC best practice
>
> CAUTION: This email originated from outside of the University of Guelph. Do
> not click links or open attachments unless you recognize the sender and know
> the content is saf
+100 for Anthony! 😊
From: Anthony Holloway
Sent: Wednesday, August 19, 2020 10:48 AM
To: Lelio Fulgenzi
Cc: Matthew Loraditch ; Charles Goldsmith
; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] [External] IPCC best practice
CAUTION: This email originated from outside of the
t; e: *mloradi...@heliontechnologies.com*
>
>
> <http://www.heliontechnologies.com/>
>
>
> <https://facebook.com/heliontech>
>
>
> <https://twitter.com/heliontech>
>
>
> <https://www.linkedin.com/company/helion-technologies>
>
>
<https://www.linkedin.com/company/helion-technologies>
>
> *From:* cisco-voip *On Behalf Of *Charles
> Goldsmith
> *Sent:* Wednesday, August 19, 2020 8:39 AM
> *To:* Johnson, Tim
> *Cc:* cisco-voip@puck.nether.net
> *Subject:* Re: [cisco-voip] [External] IPCC best practice
@puck.nether.net
Subject: Re: [cisco-voip] [External] IPCC best practice
[EXTERNAL]
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 A
: www.heliontechnologies.com | e: mloradi...@heliontechnologies.com
From: cisco-voip On Behalf Of Charles
Goldsmith
Sent: Wednesday, August 19, 2020 8:39 AM
To: Johnson, Tim
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] [External] IPCC best practice
[EXTERNAL]
Agreed with TIm, it's just simpl
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 wrote:
> It seems to me that there's not a "best practice" label for most
> sc
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
14 matches
Mail list logo
