►
From YouTube: 4 04 Bring the Customer with You
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
A
Okay,
so
this
is
around
the
idea
that
you
need
to
do
more
than
just
give
the
customer
next
steps
or
show
them
the
solution.
We
talked
about
that
a
bit
earlier,
as
we
looked
at
the
what
and
the
how
right,
there's
the
what
of
the
solution
but
the
how
how
do
you?
How
do
you
bring
that
to
them?
Our
focus
is
a
little
bit
different
here,
but
it's
closely
related
to
that.
A
A
You
got
to
know
their
level,
you
have
to
understand
their
current
needs
and
their
situation
do
they
have
time
and
interest
in
in
really
following
along
with
your
thinking
as
you're,
going
how
much
detail
do
you
want
to
go
into
in
doing
that
so
you're
going
to
bring
into
play
all
these
things
we've
been
talking
about
as
you
try
to
keep
them
working
with
you,
because
there's
a
lot
of
benefit
to
that.
You
don't
want
to
lose
them.
A
You
don't
want
them
to
not
understand
where
you're
going
and
maybe
they
you
know
they
put
their
hands
up
and
say
whoa,
I
you
know,
that's
I
don't.
I
don't
want
to
do
that,
because
that
doesn't
make
sense
to
me.
Well,
you've
lost
them,
then
you
didn't
didn't
bring
them
along
and
they
can
say
worse
things
than
that,
certainly
so
think
about
your
normal
update
to
a
customer
in
the
ticket.
A
As
I've
read
through
a
lot
of
tickets
in
the
past
several
months
and
in
previous
jobs
as
well.
Most
of
the
time
I've
seen
people
writing
in
the
ticket.
Something
like
please
send
me
this
log
file
and
that's
that's
not
the
whole
message,
but
that's
the
whole
step
right
there.
Just
please
send
me
the
log
file
to
bring
the
customer
along.
A
You
might
want
to
write
something
a
little
bit
more
like.
Oh,
this
error
message
that
you're
getting
originates
from
this
part
of
the
product
when
this
kind
of
thing
is
going
on.
So
I'd
like
to
look
at
the
log
file
that
will
show
me
what
that
part
of
the
product
is
doing,
and
I
can
learn
about
what's
causing
it.
Please
send
that
to
me.
A
You
can
probably
do
that
in
a
more
succinct
way
than
I
I
just
did
in
that
example.
But
right
the
message
is:
don't
just
ask
them
to
do
certain
things.
Tell
them
with
each
thing
you're
asking
why
why
it
matters
and
there's
many
different
ways,
you
can
go
about
that
some
people
will
do
it
step
by
step.
I
want
to
understand
this
thing,
so
please
do
that.
A
I
want
to
see
what
happens
when
you
when,
when
these
steps
are
taken
to
see,
if
we
see
the
same
problem,
so
would
you
please
do
that
other
people
lay
out
all
the
steps
and
then
at
the
end,
they
summarize.
These
things
are
all
about
getting
me
more
data
to
narrow
down
the
problem
and
some
people
summarize
first,
it
doesn't
matter
to
me
as
long
as
it's
all
in
there.
A
I
do
very
often
also
see
support
engineers,
including
a
lot
of
questions
and
thoughts
when
writing
to
a
customer.
This
is
the
stream
of
consciousness
style
message
or
the
storytelling
message
and
to
be
clear
telling
the
story
can
be
really
important,
because
that
is
part
of
explaining
things
you're
taking
them
through
your
thought
process.
A
A
A
B
A
Okay,
so
a
little
bit
more
about
bringing
the
customer
along
with
you
and
this
time,
looking
back
to
our
prior
conversation,
about
it
being
a
call
so
using
all
your
skills,
be
prepared,
as
we
talked
about
so
much
as
much
as
possible.
That
helps,
but
also
use
your
listening
skills.
This
is
time
to
catch
when
you're
on
a
call.
A
It's
that
interactive
opportunity,
then
to
hear
what
they're
saying
really
understand
it
and
use
that
understanding
to
just
speak
to
them
at
their
level,
understand
their
needs,
bring
them
along,
and
let
them
know
that
you,
you
understand
their
needs
and
then
try
to
use,
even
in
that
oral
context,
your
same
foundations
for
a
good
message
start
that
call
with
clarifying
this
is
what
we're
talking
about
recap.
The
agreed-upon
purpose
and
agenda
give
a
little
bit
of
history.
A
If
there
is
any
about
what
got
you
here,
why
you
came
to
the
call
where
you
are
now
what
you
plan
to
accomplish
in
the
call.
These
are
all
good
things
to
to
roll
into
the
communication
in
the
call
keeps
that
customer
aligned
with
you
and
moving
along
with
you,
and
then
you
wrap
it
up.
As
I
talked
about
earlier,
you
get
to
the
end
of
the
call
calling
second
game
get
to
the
end
of
the
call,
and
you
do
want
to
talk
about
what
did
you
do
during
the
call?
A
B
It
okay,
I've
never
done
this,
but
I
just
just
random
thought
here:
would
it
be
okay
to
record
customer
calls,
so
other
engineers
could
look
at
them
too.
A
You
would
need
to
ask
the
customer
for
permission
first.
Certainly
if
you
were
on
a
call
with
somebody
in
the
u.s
federal
space,
I
wouldn't
even
bother
asking
just
don't
do
it,
but
there
there
could
be
a
lot
of
concerns
there
and
you
might
want
to
run.
The
entire
concept
by
illegal
harass
has
a
thought
to
offer
on
that.