In this short clip, Max gives a general overview of where SupportLogic begins, with sentiment analysis of your case history to surface the highest priority customer interactions from your data.
0:00
Your support team talks to your customers more than anyone else.
0:04
There's a wealth of information in those interactions that can be used to
0:09
understand customer health, to proactively engage with customers and ensure
0:14
that they're
0:14
getting the right service they need, to ensure that you're not walking into
0:18
meetings with
0:18
customers not knowing that the house is on fire, all of these types of things.
0:24
What you're looking at here, this is the console page within Support Logic.
0:28
This is a bit of a command and control center where you can see cases that have
0:32
had
0:32
recent activity and sentiment signals detected upon them.
0:37
Natural language processing is at the core of what we do.
0:40
We analyze and read the cases and we extract the voice of the customer in the
0:45
form of
0:46
a variety of distinct sentiment signals.
0:49
You can see right here these are frustration signals based on statements that
0:53
the customer
0:54
is making within cases.
0:55
But we look for a variety of different signals that we categorize.
1:00
Can be frustration, confusion, impatience, non-helpful responses, negative
1:08
sentiment.
1:09
These are all, the models are built specifically for support organizations.
1:14
So complex technical support, whatever it might be, our models are built to
1:21
understand
1:21
those interactions on a level that a generic AI model doesn't.
1:27
So it's kind of where our expertise here flows in.
1:31
And so these signals, right, they're very much, these are kind of emotional
1:35
signals,
1:36
like how a customer is feeling about a support interaction.
1:42
But we also analyze and look for what I would call more procedural language
1:46
that a customer
1:47
might use requesting an escalation, right, saying that their system is down or
1:53
that
1:54
their users or production users have been affected, that they're having a
1:58
critical issue
1:59
of some kind or expressing just urgency on a case, as well as asking for
2:06
updates, asking
2:07
to schedule a call or analyzing everything we surface these to you in near real
2:13
time so
2:13
that you can proactively engage on these cases and with these customers in
2:19
whatever capacity
2:20
you are doing so, whether that be in support, customer success, account
2:26
management allows
2:27
you to very much one, make sure that the team is working on what they should be
2:31
working
2:32
on and also making sure that you're able to engage with your customer, exec
2:37
sponsors
2:38
and leadership and let them know that your team is doing everything they can to
2:44
ensure
2:44
that their issues are being addressed and resolved in a timely fashion.