►
From YouTube: Support Ops Sync - 2022-08-30
Description
Support Ops Sync - 2022-08-30
A
B
It
was
so
good,
it
was
amazing,
it
was
yeah.
I
went
to
maui
this
year.
Instead
of
last
year,
we
went
to
oahu,
which
is
a
little
more
like
kind
of
corporate
and
touristy
this
year
we
did
just
all
beaches
and
hikes
and
nature
and
stuff,
so
it
was.
It
was
great
waterfalls
and
jumping
off
of
rocks
and
stuff.
So
perfect.
C
B
A
A
A
C
A
C
I
mean
for
for
me,
I
think
if
you
can
arrive
in
like
the
evening
or
late
afternoon,
wherever
then
you
can,
then
you
can
force
yourself
to
stay
up
and
usually
you
end
up
sleeping
a
little
bit
better,
but
I've
also
found
that,
like
after
two
days
it
wears
off
and
you're
back
to
your
normal
time
zone
and
all
you
can
do
is
suffer
so
it's
like.
I
don't
know.
A
A
C
A
A
I'm
still
working
with
a
few
key
sales
members
to
get
a
few
key
orgs
to
agree
to
be
our
beta
testers
for
that,
so
we'll
kind
of
see
how
that
goes.
Hopefully,
all
the
ones
we're
looking
to
have
beta
testers
do
because
they
are
ones
that
are
kind
of
pretty
consistently,
not
happy
with
the
current
managed
contact
management
way.
We
do
things
so
and
they
all
do
have
account
management
projects
set
up,
so
that
is
also
nice
but
the
backend
stuff.
A
So
hopefully,
it'll
be
to
a
point
where
ops
barely
has
to
do
anything
for
these,
which
is
the
ideal
thing.
Ideally,
I
want
you
to
have
to
do
nothing.
It
should
just
work,
but
there
are
going
to
be
weird
cases
where
there's
no
sold
to
because
something
synced
weird
into
salesforce,
where
we
will
have
to
interact
and
actually
do
something.
A
So
I'm
going
to
work
out
all
that
stuff,
but
yeah,
so
nothing
going
into
you
know
nothing
set
in
stone
right
now,
but
the
plan
is
to
kind
of
work
out
that
beta
test
get
feedback
iterate
and
then,
hopefully,
by
fiscal
year,
24
the
start
of
fiscal
year.
24.
Have
this
something
we're
using
globally
for
zendesk
global
federal
is
still
going
to
use
their
method
of
contact
syncing
up
until
it
becomes
unable
to
do
that
method.
A
Cool
me
and
lyle
talked
with
legal
and
finance
about
data
retention,
and
finance
gave
us
180
days
is
pretty
much
all
they
need,
but
legal
said
because
of
contract
law
in
some
countries
it
could
be
up
to
seven
years
in
some
rare
countries,
even
more
because
of
that
we
decided
we're
not
going
to
look
into
removing
users
that
have
tickets,
because
there's
just
way
too
many
variables.
At
that
point,
we'll
shift
focus
to
removing
users
with
no
tickets.
A
You
know
because,
obviously
they
have
no
tickets,
they
don't
need
to
be
a
user
and
then
greatly
expired
words,
which
is
a
new
term
that
we
are
working
on
the
definition
of
basically
an
org
that
is
so
far
expired.
We
do
need
that
org
in
place,
the
users
and
their
tickets.
Would,
you
know,
obviously
still
be
there.
We're
just
talking
about
the
awards.
Specifically
style
has
a
question.
C
A
I
assume
that,
like
there's
a
redaction
app,
but
there
is
no
automated
way
or
scripted
way
we
could
actually
bring
down.
We
could
redact
comments.
We'd
have
to
use
that
app
on
every
ticket
and
even
then
I
don't
think
you
can
do
that
on
a
closed
ticket.
I've
never
actually
tried
to
redact
an
attachment
on
a
closed
ticket.
A
A
B
A
Attachments
by
the
way
we
define
customer
data,
but
I
think
we
should
ask
we
could
ask
people
to
clarify
on
the
issue
we
have.
I
know
finance
doesn't
look
at
attachments,
so
I
think
we
just
need
legal
to
clarify.
If,
like
is
this
just
about
their
attachments
or
their
ticket
content
itself,
based
on
the
wording
dan
said
or
eugene,
whoever
it
was.
That
commented,
I
think
it's
literally.
C
Yeah
I
the
the
thing
that
I'm
concerned
about
ultimately
is
like
both
with
ticket
data
and
attachments
is
just
security.
There
have
been
ins
not
not
within
gitlab,
but
in
the
globe
there
have
been
instances
of
support
portals,
getting
compromised
and
then
key
data
from
support
tickets
and
attachments
being
used
to
compromise
a
network.
C
A
A
C
C
A
A
B
B
A
C
A
A
C
C
A
A
I've
got
fancy
spreadsheets
that
take
the
data
we
put
in
them
and
generates
nice
little
report
areas
that
we
can
then
use
to
determine
churn
rate
stuff
like
that
or
I
guess
it's
not
turn
rate.
If
they're
a
prospect
buy
rate,
whatever
term
is
used
for
that,
yeah
we'll
actually
be
getting
that
committed
into
a
process
and
all
this
stuff
I'll
make
sure
the
detail
like
as
opps
here's
the
things
you
need
to
look
into
right
now.
A
The
ops
workflow
is
very
basic
because
it's
just
talking
about
how
to
actually
do
it,
not
necessarily
here's
what
you
need
to
check.
Here's,
how
you
expire
them
all
that
fun
stuff,
so
yeah
I'll,
commit
that
fun
stuff
to
actual
workflow
and
then
probably
make
a
training,
module
and
level
up.
Since
that's
our
new
learning
tool.
A
A
I'm
gonna
try
to
make
that
as
balanced
as
possible,
so
I'm
hoping
to
have
that
done
by
friday
and
then
once
we
kind
of
have
that
in
place,
I'll
make
issues
or
I'll
do
one-on-ones
or
something
with
each
of
y'all
to
be
like
alright,
so
you're
primary
responsible
for
these
things,
I'm
gonna
walk
you
through
what
you
need
to
go.
Do
on
your
projects,
issue
templates
and
stuff
like
that.
A
A
A
A
A
Yeah
I'll
ask
again
next
week
just
get
feedback
on
how
you
all
felt
with
that,
but
I
thought
it
was
a
cool
little
small
coding
task.
I
could
give
y'all
there's
not
like
a
whole
lot
to
it,
but
it's
an
experience
to
kind
of
you
know
play
around
a
little
bit
with
ruby.
What
I
want
to
know
is,
while
you're
doing
it
if
you're
like,
I,
don't
understand
exactly
what
this
is
doing.
Let
me
know
I
want
to
kind
of
do
a
little
session
and
we'll
I'll
walk
you
through
like
okay.