►
From YouTube: Service Desk Q&A with Candidate Experience
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
A
B
A
A
You
email,
our
alias,
and
that
way,
regardless
of
who
is
you
know,
working
with
anybody
from
the
team
can
pick
that
up
because
it's
generally
going
to
be
last-minute
right
now,
it's
really
hard
do
to
email
volume
to
sift
through
and
find
those
emails
quickly
and
also
to
find
if
anybody
has
responded
to
them
quickly,
so
on
average
I
think
in
eight
hours
we
receive
about
150
emails
and
so
trying
to
sift
through
that,
even
if
you
create
labels
and
all
that
kind
of
fun
stuff
finding
the
response
is
especially
hard.
A
So
we
had
considered
a
you
know
like
a
helpdesk
ticket
system
and
then
stumbled
upon
the
gitlab
service
desk
and
was
like
hey,
let's
dog
food.
If
we
can,
this
looks
like
this
might
solve
our
problem,
but
that's
what
we're
hoping
to
kind
of
clarify
and
then
maybe
work
through
some
of
the
questions
we
have
after
watching
the
demo
yep.
B
So
I
guess
first
of
all,
I
should
say
like
service
desk.
Like
is
you
know,
there
are
sort
of
some
use
cases
we're
working
some
use
cases
where
it
won't
so,
like
obviously
a
Gil
lab.
We
try
and
use
our
products
as
much
as
possible,
it's
easier
for
us
if
we
can
use
our
products
as
much
as
possible,
because
we
get
better
feedback
and
also
it's
like
reducing
the
number
of
places
you
have
to
check.
B
A
Personally
think
it
will
work
so,
for
my
understanding
of
it
is
if
they
email
it
will
create
an
issue.
We
just
need
to
figure
out
what
project
those
issues
need
to
kind
of
live
in,
and
then
we
can
respond
directly
out
of
the
issue
to
say:
okay,
I
got,
you
know
your
rescheduled
request,
I've
cancelled
the
interview,
I'll
be
looking
at
calendars
and
we'll
send
you
know
a
new,
updated
interview
shortly
and
then,
generally
speaking,
we'll
be
able
to
close
the
issue
right
away
once
we
send
that
response.
A
B
So
one
thing
about
where
the
project
goes,
that
is
worth
considering
so
I
think
it
get
lab.
We
normally
treat
most
things
as
public
as
possible
and
if
they're,
not
public,
they're,
mostly
visible
within
the
company
as
much
as
possible,
but
candidate
names
are
typically
an
exception
to
that
I.
Think
really,
you
know
when
we
say
I'd
like
to
reschedule
for
somebody
on
slag.
You
say
you
know,
don't
put
the
name
in
the
channel
late
diem,
the
name
and
the
way
my
permissions
working
get
lab
is
that
we
have
a
group
like
get
lab.
B
Comm,
like
you
know,
which
contains
our
website
and
like
our
people,
Ops
repositories
and
a
lot
of
stuff
and
everybody
get
lab.
Is
a
member
of
that
group
and
you
can't
restrict
you
can
have
subgroups,
but
you
can't
restrict
people's
permissions.
As
you
go
down
groups,
you
can
only
give
them
more
permissions.
B
B
A
Actually
I
was
wondering
like:
can
we
I
think
this
is
for
sure
the
way
we
want
to
go?
Can
we
actually
set
up
the
project
while
we're
online
together
and,
like
start
start,
it
now
is
that
possible,
yeah.
B
B
B
B
B
B
So,
actually
you
don't
have
access
to
see
what
the
surface
TSK
email
address
is.
But
I
can?
Oh,
no.
Actually
you
can
see
it
if
you
go
to
the
service
desk
on
the.
If
your
issues
on
the
left
and
then
there's
a
service
desk
email
address
there,
so
what
I'm
going
to
do
is
I'm,
just
gonna
send
an
email
to
that
and
just
check
if
it
all
works.
Okay,
cuz,
it's
rich
and
there's
nothing
like
demoing
like.
B
A
Booked
and
I
think,
while
we're
waiting
for
that
Chantal
I
was
thinking
of
labels
that
we
would
need
to
create
I,
don't
know
if
you
kind
of
given
that
any
thought,
but
I
thought
like
a
no-show
we're
scheduled,
withdraw.
Thank
you.
What
are
some
of
the
other
top
reasons?
People
email
us
so
no-show
reschedule,
withdraw
and
a
thank
you.
B
So
one
thing
I
was
going
to
say
which
I
just
realized
was
dumb
was
that
you
could
just
like
start
without
labels
and
might
build
up
from
there,
but
you
already
a
bunch
of
emails
to
this,
so
that
you
already
know
like
how
you'd
want
to
label
this
stuff.
If
you
refresh
it
should
be
there.
I
can't
see
it
cuz
I'm,
not
a
member
of
the
projects,
but
you
should
be
able
to
see
it
perfect.
C
B
The
person
who's
created,
this
request
can't
see
it,
which
is
something
I
think
that
it's
been
requested
like.
If
the
person
is
a
get
live,
user
who's
created
it,
then
they
should
be
able
to
see
it.
It's
C
Roloson,
but
she
won't
show
up
by
default
because
she's
nice,
but
she
won't
be
able
to
see
it
either.
B
Yeah
so
I
get
both
of
those
there's
no
confidential
notes
at
the
moment,
but
I
can't
like
I,
mean
that's
fine
right
like
for
this
case.
It's
not
a
problem
that
you
know
can't
see
them
so
yeah
I'm,
just
gonna
real
quick
share,
my
screen
just
to
show
that
that
will
work
just
in
case
anybody
was
like
and.
B
A
B
A
A
Absolutely
because
I
think
I
mean
it's
fine,
because
it's
you
know
still
branded
as
get
love,
but
I
think
it
would
be
awesome
if
we
could
call
out
that
it's
you
know
from
the
recruiting
team
and
then
my
other
question
about
this
is:
what
reporting
do
you
think
we
can
pull
out
so
I
would
assume
I
would
need
to
do
a
data
team
request
and
work
with
like
Emily
or
somebody
to
pull
information
from
this
so
like
who
responds
the
most.
How
quickly
were
responding
all
those
kinds
of
fun?
Metrics?
A
B
We
do
have
some
of
those
that
the
quality
team
of
building
inside
get
lab
itself
because
we
have
you
know
we
want
this
to
be
part
of
the
product
itself,
but
it
depends
on
what
metrics
you're
looking
for
so,
for
instance,
who
responds
the
most.
If
you
just
assign
things
when
you're
working
on
them,
then
you
can
just
look
at
the
list
of
flows.
Issues
like
count,
yeah,
filter
by
assignee
and
see
IQ.
You
have
the
most
or
whatever
I'm.
A
B
B
B
A
B
A
B
Okay,
so
if
you
go
to
the
project's
homepage,
yep
so
by
default
in
get
lab-
and
you
might
have
changed
this
like
for
your
notification
settings
but
like
by
default
for
most
people,
what
they
get
is
they
get
an
email
when
they
are
participating
in
something
so
someone's
already
mentioned
them
or
they
like
commented,
or
they
created
the
issue
in
the
first
place
or
whatever.
But
if
you
want
to
get
an
email
for
all
comments
and
all
activities
on
the
projects,
there's
a
little
bell
icon
up
there,
where
it's
the
star
zero
at
the
top.
B
So
you
got
the
clone
the
star
and
the
little
bell
icon.
If
you
click
that
that's
your
notification
settings
so
watch
gives
you
everything.
What
you
might
want
instead
is,
if
you
had
custom,
so
watch
means
that
you
would
get
an
email
when
a
new
issue
is
created.
When
an
issue
is
closed.
When
someone
else
commented
on
an
issue.
What
you
might
just
want
is
new
issue,
and
then
you
can
also
fail
pipe
lenses
or
any
mastics.
You
might
be
running
pipelines
on
this
project,
but
yeah.
B
So,
like
new
notes
would
be
new
comment,
but
you
don't
want
an
email
for
every
new
comment.
You
and
you
want
the
standard
emails
you
get
for
comments
on
issues
you're
participating
in
or
where
someone's
mentioned
you.
But
if
you
add
this
and
you'll
get
an
email
for
every
single
new
issue.
That's
created
on
this
project,
so
you'll
be
in
the
in
the
loop
there
and
as.
A
A
A
C
Okay,
so
we
all
get
an
email
when
the
issue
is
created,
then,
whenever
so,
let's
say
like
April
tackles
it
and
she's
decided
that
she's
been
overcome.
It
ten
like
for
me
to
like
stop
getting
notified
because
April
has
not
taken
it.
So
I
just
have
to
kind
of
like
switch
off
our
notifications
thing
so.
B
Is
that
if
you
you're
only
an
email
when
the
issue
is
created,
so
then
to
get
further
emails
on
that
issue?
You
would
have
to
like
participate
in
the
issue
somehow,
either
by
April,
mentioning
you
or
somebody
mentioning
you
or
by
you,
commenting
yourself
by
you
going
and
subscribing
to
the
issue.
So
you
wouldn't
get
emails
about
the
other
stuff.
You
actually
might
want
to
also
subscribe
to
close
issue.
I've
just
realized,
because
if
you
only
get
the
open
issue
ones,
then
you
might
like
see
your
inbox
and
be
like.
B
A
B
Honestly,
the
way
the
way
I
would
use
this
is
probably
like
you
know.
You
don't
need
the
new
issue
email
if
you're
gonna
like
go
and
refresh
the
project
list
every
so
often,
but
if
you
do
use
the
email
notification
thing,
I
would
most
use
that
as
like.
If
there
are
any
new
issues
like
since
I
last
checked,
my
email
I
should
go
and
look
at
the
issue
list
in
the
project
rather
than
sort
of
flying
by
and
work
from
the
inbox,
because,
like
it's
hard
to
keep
others
in
sync
yeah
and.