►
From YouTube: 6 04 Closing Message
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
So
one
thought
about
the
message
at
the
end
of
our
our
ticket
there,
which
is
really
along
those
lines
of
how
do
we?
How
do
we
close
it?
How
do
we
confirm
everything?
It's
just
to
note
that
I've
been
talking
about
this
standard
framework
for
a
message.
I
want
to
point
out
that
that
framework
doesn't
fit
at
all
if
you
leave
it
intact
at
the
end
of
a
ticket.
So
we
want
to
change
some
things
to
suggest
that
you
provide
what
I
call
the
enhanced
history.
A
It's
really
just
a
summary
of
here's
kind
of
what
we
went
through
and
it's
not
all
the
paths
that
we
followed
on
a
really
challenging
ticket.
It's
just
this
was
the
problem
we
fixed
it
this
way
you
know
and
then
there's
an
action
that
I
want
everyone
to
add
at
the
end
of
of
a
ticket
before
the
wrap-up
and
closing,
which
is
just
what
it
was
before.
A
You
know
the
thank
you
and
have
a
good
day
sort
of
thing,
but
that
that
action
there
is
the
thing
to
really
talk
about,
and
this
is
that
we
really
want
to
as
I've
been
showing
in
that
slide
at
the
beginning
every
day
we
really
want
to
ask
all
of
our
customers
to
take
the
survey
we
do,
for
whatever
reasons
get
pretty
good
percentage
of
responses
from
our
customers
on
the
survey.
A
Invitations
which
is
great,
doesn't
mean
we
don't
want
more
so
in
the
interest
of
getting
more
and
in
the
interest
of
getting
it
from
not
just
people
who
are
really
unhappy,
or
you
know
in
some
extreme,
where
they're
more
likely
to
fill
it
out.
We
want
to
ask
everyone
so
that,
hopefully
we
get
more
and
more
feedback
that
tells
us
specifically
what
we
did
well
and
what
we
did
poorly.
A
Please
always
ask
we
might
have
a
tendency
not
to
ask
if
we
feel
like
it
was
a
bad
experience,
but
that's
when
we
really
can
learn
the
most.
So
please
always
ask
please
try
to
find
a
nice,
simple,
brief
way
to
say
I'd
like
to
get
I'd
like
to
hear
the
good
and
the
badge
right.
Give
me
some
positives.
If
you
have
it,
give
me
some
constructive
criticism,
if
you
have
it
we're
really
trying
to
say
we're
open
to
all
of
it,
it
all
matters
to
us.
A
Let
people
know
that
it's
worth
their
time
by
telling
them
we
actually
read
these
this
week,
I'm
the
person
who's
reading.
All
of
the
the
sat
surveys,
for
example,
and
one
manager
does
it
every
week
and
we
do
use
them.
We
we
have
reports
about
them.
We
try
to
make
changes
based
on
them,
so
they're
important.
If
people
know
that
if
they
believe
that
they
might
be
more
likely
to
fill
out
the
survey
you
might
want
to,
let
them
know
that
it's
okay,
it's
not
going
to
be
bad
for
you.
A
B
Conditions
aside
from
that,
where
they
may
not,
because
I
think
zendesk
by
default,
does
not
send
an
asset.
If
you
know
I
could
be
totally
wrong
on
this,
but
I
thought
I
remember
something
about
like
if
a
you,
like
a
specific
user
or
where
the
ticket
is
tied
to
a
specific
email
address
as
the
requester
and
they
closed
multiple
tickets
within
24
hours,
you
may
not
get
one
for
each.
I'm
actually
not
sure.
A
A
I
I
can't
think
of
what
other
situations
there
might
be.
It'll
only
send
one
invitation.
So
if
you
have,
the
invitation
goes
out
24,
I
think
24
hours
after
solve.
A
Hopefully
we're
avoiding
that,
but
I
I
don't
think
there
are
other
exceptions.
Jason
collier
is
the
best
one
to
tell
us
that
if
you
want
an
individual.
A
I
was
actually
just
being
subtle
here.
I
see
I
use
the
word
customer
on
the
slides
and
in
get
lab
terminology,
the
customers
they've
all
paid
the
free
users.
Those
are
separate
things,
that's
not
true.
I
wasn't
being
that
solid
like.
I
did
not
think
about
that
when
putting
this
together
so
that
may
deserve
a
special
footnote
on
the
slide.