Use Cases · 5 min read

How Fullstory helps TravelPerk give first-class customer service

Justin Owings
Posted June 30, 2017
How Fullstory helps TravelPerk give first-class customer service

Today’s Fullstory use-case comes from TravelPerk, a free web app that allows you to book and manage your business travel, helping with price comparisons and centralizing invoicing and reporting (and can also be integrated with tools like Expensify).


An in-app screenshot from the TravelPerk app, a free web app that allows you to book and manage your business travel.

Chris Roy, Lead User Experience Designer at TravelPerk, shared how his team and others at TravelPerk use Fullstory session replay and click maps to investigate Rage Clickssupport customers through contextsolve bugs in JIRA, and more.

Read on to see how TravelPerk is putting Fullstory to work.

How TravelPerk uses Fullstory

Notes from Chris Roy, Lead UX designer at TravelPerk

Going Live With Customers Using Fullstory

Having just installed Fullstory on TravelPerk, we were on a call with a new client who — midway through the call — sounded like she was struggling with something on the site. Within moments, I was able to show via Fullstory’s live stream exactly what she was doing. I showed the live playback to our Account Director and he was amazed. He muted the call and said, “How can you see that!?”

Going live was great as it allowed us to course-correct the client without having to go offline, dig into some numbers and event tracking, and then get back to her.

With Fullstory we could see exactly what she was doing while still being on the call with her. It was like screen sharing but without the painful set up.

Integrating Fullstory With Intercom and Zendesk

Another benchmark moment was when I went crazy with integrations and had Fullstory connected with Intercom, Trello, Google Analytics, MixPanel, Slack, and Zendesk[1]. I ran a couple of workshops just to run through the tool and specifically how our Customer Support Agents could troubleshoot in depth with any questions or comments which they received.

A typical support ticket would involve a lot of back and forth trying to clarify the steps that user took when they stumbled upon an issue. Problem is a lot of things are done by users subconsciously, so it is not easy to recall all the minute details — the details that really help when debugging. Now, with the click of a button, a Customer Support Agent, Product Owner, or Designer can see exactly what happened during the session, including the ability to see any console logs or additional meta data that could help find the source of an issue — and do it all within moments, not hours or days.

Looking for Patterns in Behavior

Another thing I personally love to do as a UX Designer is watch a couple of sessions and spot patterns where it looks like people are struggling. This may start with the Rage Click filter[2], for example.

After seeing someone struggle with a part of the UI, I can then run a search on that part of the TravelPerk application and watch a bunch of other sessions. With very little effort, you can easily spot some friction points that could otherwise go unnoticed. It is a real game-changer in the sense that you can proactively solve problems[3] before people start telling you about them.

TravelPerk Rageclick

Here a TravelPerk user had a “dead click” on an element within the app.

Solving Low Net Promoter Scores (NPS) With Fullstory and JIRA Integration

In a similar light, we recently received an NPS score of 6 from a customer (which is not a regular thing), so I quickly jumped in to replay the session.

To my horror, I saw that the customer tried to input the same information into a form 8 times. She tried logging out and in and coming back to that screen but it kept failing to accept her input. A quick search on Fullstory and I realised that 12 other people had been affected by this bug. Using the JIRA integration¹, I immediately raised a critical issue and we had it fixed and in production within hours.

Trying to figure out this issue “the old way” could have taken days, frustrating a lot more customers. This is where the tool really pays back on the investment.

To the Future!

In addition to the above, I have also used Page Insights at times to understand aggregated behavior on a page — it can be a good guide for spotting dead link patterns or key interactions within a given context.

Click Maps

A screenshot of Page Insights Click Maps for the TravelPerk app.

I am super excited to see how Fullstory progresses even further as I think what you have delivered so far is a real breath of fresh air in the analysis of product performance.

Being a UX Designer, it also gives me a vast wealth of “what people do” vs “what people say” content which can be great when you are looking to make decisions on new features or improvements.

Chris further shared that when TravelPerk originally looked at Fullstory they only expected to use Fullstory Free; however, after using the features of Fullstory Pro, Chris easily convinced his company to subscribe. We couldn’t be more excited to hear of the success TravelPerk has had with Fullstory.

Justin OwingsFormer Director, Content

About the author

Justin Owings was previously the Director of Content Marketing at Fullstory.

Return to top

Related posts

Blog Post
TEI study finds Fullstory delivered 451% ROI for an enterprise organization

Discover the four major benefits of Fullstory’s DXI that helped an enterprise retailer gain millions in value.

Read the post
Blog Post
How DailyPay uses Fullstory’s intelligence, integrations, and insights for better CX

Find out how 9 DailyPay teams are using DXI to transform their customer insights and feedback loops.

Read the post
Blog Post
Trading site performance for DX insights? Here’s why you don’t need to

Find out how we built the Fullstory data capture script to ensure it doesn't impact page speed, and hear from major retailers who've proved it.

Read the post