All Collections
Use Cases
Gathering Feedback with In-App User Testing Scheduler
Gathering Feedback with In-App User Testing Scheduler

Integrate your scheduling app with your UserGuiding content to collect valuable insights.

Efehan avatar
Written by Efehan
Updated over a week ago

Use Case

Removing friction and focusing on proper design is the key to providing a good user experience. As Product Teams focus more on the functionality of a new feature, they might tend to get further away from how this feature can help their user base in general. This is where conducting user testing sessions become useful. How? By:

  • Collecting insights from different types of users to understand the target persona that can benefit the most from the latest improvements.

  • Gathering user feedback to foresee the issues/challenges that may occur for the general audience and take proper action.

This guide will focus on automating the process of reaching the target users and scheduling user testing sessions. We'll cover:

  • Creating the Guide & Integrating with the Scheduling App (Calendly)

  • Targeting the correct users

  • Testing the experience

  • What metrics will this impact?

The final look of your in-app scheduler will look similar to the example we created below:

Creating the Guide & Integrating with the Scheduling App (Calendly)

Let's begin by creating the actual content.

1-) Launch the Chrome Extension to Create a New Guide

  • Navigate to the platform page where you'd want your walkthrough to start and open the Chrome Extension.

  • Then, click + Guide, enter Guide's info, add a new step and select the "Side Notification" template under the Modal section.

Pro tip: Make sure to be clear & concise with what this Modal is about, and let users comprehend what's in it for them while you ask for their feedback.

  • Add a second step, select the "Side Notification" template, and add an HTML component. You may delete other components that come with this template to avoid confusing your users.

  • Paste the inline embed code that you obtain from your scheduling app. In this example, we used Calendly, but you can use any other app.

2-) Adding & editing the CTA

  • For the initial step, remove the requisite button, which ends the Guide on the Side Notification template by default, and add two custom buttons that:

    • Takes users to the next step so that they can schedule a call.

    • Ends the guide for those not interested in a user testing session.

3-) Triggering your feature announcement conditionally

You can control for which user segment and under which conditions your modal triggers. You can also select the page(s) where it would appear.

You can also set an appearance frequency for your prompt. For example, it could trigger once a week when a user from the selected segment arrives at the target page.

4-) Customize

UserGuiding gives you the ability to customize the walkthrough fully.

  • You can personalize the Modal by including the user's first name.

  • Visuals drive users' attention and can give a visual sense related to the content.

  • You can also fully customize the look & feel of the Guides with Customized Themes.

  • If you have a Theme you're ready to use, make sure this walkthrough is using it.

Targeting the correct users

For this specific use case, we wanted to segment users based on:

  • Being a customer.

  • Have completed the initial onboarding Checklist.

  • Had more than 20 Web Sessions.

Your segmentation conditions may be different from the above example. Feel free to set your own conditions by sending property to UserGuiding.

Once you decide on the segment, don't forget to set it to the content you've created.

Testing the experience

Setting the audience to Only Me will limit the content displayed for you and your colleagues.

You can navigate to a page where the support content should display, test it to see what it will look like, and publish it when you're ready.

What metrics will this impact?

  • Provide an opportunity for your Product Team to gather insights & feedback from your target users to release functionalities that satisfy their needs & expectations

  • Save time & engineering resources.

Did this answer your question?