►
From YouTube: Support Ops Sync - 2022-12-06
Description
Support Ops Sync - 2022-12-06
A
A
We
would
instead
just
make
a
plug-in
on
the
Super
App
instead
of
making
a
whole
new
app
and
having
20
000
apps,
so
we'll
be
I'll,
be
working
with
Dylan
on
that
stuff
link
projects
as
they
come
about,
like
I
finished
the
super
app
in
the
basic
Club
it
plug.
It
love
it
wow,
plug-in
philosophy,
logic
like
last
week
on
Friday,
so
it's
so
very
new
yeah.
A
So
more
details
will
come
on
that
as
they
become
available,
working
to
figure
out
a
place
to
put
notification
data
stuff
like
this
ticket's
about
to
breach
or
this
ticket
was
unassigned
or
whatever.
However,
much
of
a
scope
of
notification,
we
want
so
we're
working
on
figuring
out
a
place
to
put
it
anyway
for
it
to
be
accessed
so
that
people
can
utilize
that
data
in
whatever
means
they
want
to
build
a
bot.
Look
at
it
once
and
go
pretty
cool
close
pretend
it
never
existed
in
the
first
place.
Etc.
A
So
we'll
figure
that
out
kind
of
giving
us
the
month
of
December
to
work
with
the
support
team
to
figure
all
that
out,
that's
not
to
say
anything's,
changing
right
at
the
end
of
December.
That's
just
I've,
given
us
December
to
figure
out
all
the
little
details
before
we
start
figuring
out
implementation
and
all
that
the
zendesk
global
renewal
is
proceeding
as
planned.
We
might
be
jumping
up
a
level
from
professional
to
Enterprise
I.
Clearly
can't
talk,
I'm,
I'm,
saying
weird
words.
Well,.
A
A
If
we
did
go
to
a
three-year,
what
it
would
mean
is
we
don't
have
to
do
yearly
renewals,
but
what
we
will
do
is
add,
you
know,
do
add-ons
as
needed,
for
you
know
the
plan
so
adding
more
users
instead
of
doing
it
once
a
year.
We
could
do
it
in
smaller
batches
which
ultimately
will
save
the
company
money.
A
Another
thing
I've
just
kind
of
noticed
this
so
I
wanted
to
kind
of
I
kind
of
talked
with
another
manager,
and
we
kind
of
figured
out
a
tactic
we
want
to
use.
We
often
see
questions
concerning
if
the
round
robin
for
Global
is
working
properly,
I've
seen
them
a
lot
in
slack,
and
the
root
of
that
I
think
is
because
they
look
at
the
queue
sizes
in
zendesk
and
of
course,
they
look
different
because
they're
not
showing
pending
they're,
not
showing
solve
they're,
not
showing
close.
A
Don't
show
a
full
picture,
they
show
new
open
on
hold,
so
they
show
current
workload
versus
workload
has
already
been
done.
I
want
to
shift
Focus
to
instead
trying
to
figure
out
how
we
can
help
address.
What
might
be
the
root
of
the
question
like
where
that
question
is
coming
from,
so
to
do
this,
what
I
want
us
to
start
doing
is:
do
a
quick
check
on
the
project
make
sure
it
is
working?
Obviously,
we
want
to
make
sure
it's
working.
A
A
Back
but
you
should
be
seeing
changes
to
that
file
after
you
confirm
it's
working,
go
ahead
and
confirm
that
it
is
working
to
the
agent
and
then
ask
them
if
there's
something
worrying
about
the
current
workload.
Distribution
I
give
a
general
example,
but
I
encourage
y'all
to
use
you
know
whatever
wording,
you
think
appropriate.
Something
like
hey,
Bob
I
did
a
quick
check
and
can
confirm
the
round
robin
is
working
properly.
Is
there
something
worrying
you
about
the
current
workload
distribution,
very
clunky,
so
figure?
A
You
know
word
of,
however,
you
see
fit,
but
if
something
is
worrying
them
about
it,
like
the
question
is
stemming
from
I
feel
my
team
is
over
stressed
or
I'm
concerned
that
now
this
other
team
is
getting
way
more
work
and
they
can't
handle
it
or
whatever
it's
a
good
time
to
get
like
a
support
manager
kind
of
involved
in
the
threads.
So
we
can
kind
of
address
that
route
issue
we
want.
You
know
we
want
everybody
to
be
happy
and
stress-free
as
much
as
possible.
A
So
if
there
is
a
place
of
stress
or
unhappiness
that
that
question
is
coming
from,
we
obviously
want
to
address
that
I
feel
just
by
answering
yeah.
It's
working
we're
missing
that
opportunity.
So
I
kind
of
want
us
to
take
the
extra
step
there
and
do
that
while
I
see
you
typing,
do
you
want
to
vocalize
yeah.
B
Is
there
an
opportunity
where
we
can
get
in
front
of
this,
where,
like
I,
could
put
something
in
the
support
we
can
review,
whereas,
like
this
week,
we
distributed
this
many
tickets
to
each
queue
and
then
do
that
every
week?
And
then,
when
the
question
comes
and
be
like
yes
and
we
report
on
it
every
week,
yeah.
A
So
I
think
we
could,
if
we
so
desired,
it's
not
hard
to
look
to
get
history
of
a
file
now,
admittedly
being
that
that
runs
every
like
five
to
ten
minutes.
It's
a
lot
of
get
history
to
look
through
for
the
course
of
a
week.
It's
not
to
say
we
couldn't,
but
we
could
I
think
having
once
we
set
that
number.
The
first
time
like
on
Friday,
okay,
it's
500
from
that
point
forward,
it'll
be
a
little
easier
because
we
can
look
at
the
current
volume
and
say
it
increased
this.
A
Many
so
I
think
you
know
that
first
week
will
be
the
hardest.
But
after
that
we'll
be
fine.
I
do
still
think
we
should
do
that
of.
We
can
point
to
hey
yeah.
No,
we
report
on
this
every
week
and
all
that
you
can
tell
it's
working,
but
I
do
still
think
we
should
confirm.
It
is
currently
working
and
then
kind
of
use
that
opportunity
to
seek
out
if
there
is
something
bothering
or
worrying
for
the
agent.
B
A
I
have
pointed
at
least
one
or
two
of
the
Agents
of
hey.
Look
the
counter's.
Actually
here
you
can
go,
look
at
it
anytime
and
see
that
it
is
working
so
like
there
is
the
self-service
method
they
can
do,
but
I
I
feel
like
I
want
to
use
that
opportunity.
If
there's
we
can
answer
it,
but
I
feel
like.
We
should
also
continue
the
discussion
to
figure
out.
C
Jason
I
was
thinking
about
if
you
can
have
a
not
an
app
but
a
ticker
of
the
tickets,
incoming
and
tickets
on
going
on
the
top
of
it
so
like
being
tackled,
and
this
will
help
understand
that
yep
there
is
actually
a
workload
and
being
continuously
working
on.
Like
the
Lyle
said
that
we
have
a
proactive
thing
going
on,
they
don't
have
to
worry
about.
A
A
Until
we
get
to
the
point
where,
like
we
feel
like
everybody's
aware
right,
yeah,
so,
let's,
let's
maybe
I'll,
go
ahead
and
make
an
issue,
and
we
can
kind
of
start
working
on
that
and
figuring
out
how
we
want
to
address
that,
even
if
it's
as
simple
as
catting
the
file
and
running
the
JQ
parser
on
it.
So
it
looks
pretty
but
I
think
we
can
look
at
a
way
to
kind
of
help
that
out
a
bit.