►
From YouTube: Support Ops - Zendesk - Trigger positioning
Description
Jason Colyer, Support Operations Manager, takes us through managing Zendesk trigger positioning
A
So,
let's
go
ahead
and
share
the
screen,
get
started
to
start
you're
gonna
go
to
the
admit
panel,
which
the
gear
icon
here
and
then
you'll
need
to
go
down
to
triggers
under
business
rules
towards
the
bottom.
A
A
You
know
this
is
one
two
three
four
five,
six,
if
there's
inactive
ones
that
were
also
in
the
same
category,
they
retain
their
position
id
so
something
to
keep
in
mind,
at
least
for
the
you
know,
sync
repo
stuff,
where
we
actually
do
put
the
position
id,
which
is
an
integer
into
the
values,
but
there's
actually
a
couple
ways
you
can
do
this,
and
one
of
them
is
to
you
know,
select
hover
over
a
category
and
click
it
and
tell
it
to
edit
order,
at
which
point
you
can
edit
the
categories
order,
and
you
can
say
yeah.
A
So
if
we
go
to
like
the
needs
fork
stage-
and
we
want
to
take
this-
this
is
test
two
trigger
here
and
we
want
to
move
it.
We
can
actually
click
this
and
there's
edit
order.
So
that's
what
we're
going
to
want
to
click
once
doing
this.
It
allows
you
to
drag
and
drop
it
to
where
you
need
to
put
it.
So
we
can
move
this
to
all
kinds
of
places
and
then
once
you're
done
with
that,
you
simply
click
save
this
particular
case.
A
I
didn't
make
any
changes,
there's
also
the
add
trigger
below
that
you
can
use,
which
is
a
little
kind
of
different.
By
doing
it.
It
lets
you
make
a
new
trigger
and
it'll.
Add
it
below
it's
a
bit
of
a
strange
concept
since
by
default,
that's
where
zendesk
is
going
to
put
new
triggers
in
that
category
anyway.
A
Positioning
is
important,
especially
for
triggers,
as
they
are
event
not
time-based.
Several
of
these
are
likely
to
try
to
run
at
the
same
time,
so
understanding
the
order
in
which
they
run
is
very
important,
and
the
way
that
works
is
each
category
is
going
to
run
independently
of
itself
and
the
order
they
kind
of
run.
A
It
is
what
will
show
there,
so
the
creation
stage
is
going
to
run
its
triggers
first,
since
it's
at
the
top
and
from
there
it's
going
to
run
them
in
this
order
set
channel
received
at
received
that
to
web
forms,
so
on
so
forth,
going
down
the
list.
The
reason
this
is
important
is
like
looking
at
these
top
ones
where
it's
set
channel
two.
A
Obviously
we
don't
want
all
of
those
running
on
tickets
at
the
same
time,
right
because
they're
very
different
situations,
the
conditions
may
not
be
the
same,
but
the
idea
here
is
if
a
ticket
were
to
have
two
of
them.
That
would
coincide
such
as
the
set
channel
to
web
form
and
set
channel
to
emergency
if
both
of
those
were
supposed
to
run.
At
the
same
time,
both
the
conditions
have
been
gained.
The
two
web
form
one
will
run
first
and
then
to
emergency
and
then
so
on
and
so
forth.