It's been nearly 2 years since I was involved in an aborted jump to Jive.
I believe that they had looked at 8x8, Nextiva and Fuze, too.  I came into
my current position in the middle of the transition working with my now
predecessor in the IT Manager roll for a 40-50 person CPA firm with two
locations.  During testing we found our internet service was insufficient
to the task, mainly because of jitter and lag.  I'm throwing some shade at
my predecessor, but I knew cable internet was insufficient to the task.
So, my only advice is to have rock solid internet service and redundant
service to boot.  One thing that my predecessor didn't think about was that
if the internet does go down entirely, that they won't be able to make
internal calls.  I pulled the plug on the project because Jive's on
boarding process was horrible, our internet service wasn't going to be
changing anytime soon, and the inability to make internal calls during an
internet outage (which happens more than I'd like) is kind of a deal
breaker.  Jive's redundancy for secondary internet connections was kludgy
as hell and broke more than once during testing, too.  When I pulled the
plug on Jive I looked more heavily into Nextiva, but, at the time, they had
the same inability to ensure internal calls during an outage, so we
ultimately backed away from the project.  Also, I think we were a bit too
big for Jive, based on my discussions with Nextiva and Fuze.



On Wed, Jan 31, 2018 at 9:14 AM, Joey Smith <[email protected]> wrote:

> On Wed, 31 Jan 2018, Bud Durland wrote:
>
> > First, apologies for the OT post, but I´m sure there are people in
> > this group that have crossed this bridge before me.  Our purchasing
> > guy is evaluating keeping our on-prem phone system vs. going with a
> > cloud provider like 8x8.  I'm looking for input from anyone who has
> > real-world experience making the change, or changing (back) from cloud
> > to on-prem.  Please contact me off-list with war stories or on-line
>
> I'd be interested in the dialog...  OT or nah..
>
>
>
>
>
>

Reply via email to