The custom feed allows you to implement Wisp anyway you envision in. Most commonly, this means embedding an icon in a header. It's a more technical implementation, but there are several benefits that come with it to consider.

  • Full brand integration - your visitors won't feel like they're opening an app.
  • Higher engagement - see 2.5 x the engagement of the floating feed.
  • Completely customizable - adopt the style of your site and optimize for mobile.

Below is an example of the custom feed as a fixed part of the site's header. You're free to place it anywhere, but the top right of your site would follow conventional user-experience practices.

There are no limits to styling how the feed button appears. For instance, it doesn't have to be an icon, you can turn text into the home of your feed. Here's a full text navigation with an 'inbox' label for Wisp.

Another important design consideration we enable accounts for responsiveness. Since their site is responsive, their nav collapses into a hamburger menu (or menu drawer) with a few other icons on smaller displays.

If your site aims to have an even more simple on mobile, you'll likely need to tuck more away in a menu. For this reason, Wisp allows you to display the red notification badge in multiple places, as if to create a click trail for your visitors that leads them to the feed.

This shop uses Wisp inside their menu on mobile.

When you open the menu, you can see the the feed through the continuation of the red badge.

It was really important to us that Wisp can fee like a part of your site instead of a widget, if that's what you want.

Even though it's a bit more difficult, the custom feed is our most popular implementation of Wisp. You can see why - and we're here to help you get there.


If you want to learn more about implementing the custom feed, check out the doc 'Setting Up the Custom Feed'.

Did this answer your question?