Skip to main content

 

So you’ve got your content , maybe it’s onboarding checklists, feature guides, or help articles — and you’re ready to surface it through the new KC Bot.

But then you hit the decision point:

Should I use a Task List or a Content Group?
Should the layout be List, Grid, Card, or Thumbnail?

These aren’t cosmetic choices.

They directly impact how your users discover, engage, and act on the content you’ve worked so hard to build.

Here’s how to decide - based on your user’s goals, not just what “looks nice.”

 

Step 1: Start with User Intent

 

Ask:

🧭 What is the user trying to do at this moment in their journey?

Examples:

  • Just signed up → They need a path
     
  • Visiting a new feature → They need clarity
     
  • Struggling with an error → They need resolution
     
  • Curious to go deeper → They need learning resources
     

That intent is your anchor. Now let’s match it to structure.


 

Step 2: Choose the Right Widget for the Job

 

 Task List

Use when you want to guide action , like a mini playbook.
Great for onboarding steps, setup flows, and habit-forming tasks.

  • Good for: “Do this now” moments
     
  • Avoid if: Content is passive or read-only
     
  • Only one Task List is shown per user  based on rules and priority
     

Content Group
 

Use when you want to organize information for discovery.
Perfect for help docs, feature guides, and videos.

  • Good for: Browsing, learning, exploring
     
  • Avoid if: You need structured progression
     
  • You can include up to 5 content groups per bot
     

Search

Use when you have a large help base or users prefer to explore.
Pairs well with either widget above.


 

Step 3: Pick the Layout Based on Content Type

 

Once you’ve picked a Content Group, here’s how to choose its layout:

Use Case

Best Layout

Why It Works

Step-by-step guides or onboarding

List

Presents clear order; easy to follow from top to bottom

Multi-topic content (e.g., by stage)

Grid

Balanced, scannable, and structured for multiple categories

Educational or visual content

Card

Emphasizes visuals and calls-to-action

Quick links, updates, or tools

Thumbnail

Small and punchy; ideal for visual quick-hits

 

 

Choosing the Right Layout & Structure for Your KC Bot

 

 Pro Tip: Combine Layouts with Targeting

 

Goal / Use Case

Recommended Widget

Best Layout

Why It Works

Onboard users step-by-step

Task List

List

Helps guide users through a structured set of actions with check-off progress

Group feature guides or best practices

Content Group

List or Grid

List for clear reading order; Grid for quick scanning by topic

Surface help docs or FAQs

Content Group

List

Offers a sequential or category-based reading experience

Showcase educational videos or tutorials

Content Group

Card or Thumbnail

More visual layouts for engaging, click-to-learn content

Group content by lifecycle stage (adopt, expand, etc.)

Content Group

Grid or List

Cleanly organizes resources into defined stages or themes

Highlight quick links to product updates/tools

Content Group

Thumbnail

Visual layout draws attention and encourages quick clicks

Support self-service exploration

Search Widget

Search UI

Great for large libraries where users prefer to search than browse



Want to show different content to Admins vs. End Users?

Use audience rules to show only relevant Task Lists or Content Groups per role.

 

User Scenario: A new Admin logs in for the first time.
Your Intent: Get them activated and exploring.

Workflow:

  • Start with a Task List:
     
    • “Set up your first group”
       
    • “Invite users”
       
    • “Explore reporting”
       
  • Follow with a Content Group (Grid Layout):
     
    • “Admin Help Center”
       
    • “Feature Guides”
       
    • “Best Practices Library”
       

This gives them both guided direction and flexible discovery, in the same bot.

Here is how we put them together to stack various types of resources in different layouts:

 

Different Layouts, for different reasons!


With that, let’s dig deeper into more workflow and use case scenarios in our next post :-) 


There is a update on Layouts : We got a new one - Tile Layout!
 



Where you can use it?

  • To offer goal-based onboarding (e.g., "Learn the basics", "Become a power user")

  • To structure role-based enablement (e.g., Admins vs. Managers)

  • To centralize training or certification journeys

  • To drive progressive engagement across maturity stages

     

    Title: Unlock Your Product Knowledge

  • Onboarding Basics → Links to setup guides + walkthroughs

  • Advanced Reports → Analysis use cases, sample reports

  • Segments Mastery → Deep dives into user segmentation

  • Tips & Tricks → Productivity hacks, pro moves, shortcuts


Will keep adding as we get more of these enhancements :-)

Stay tuned!

 

I have a couple of follow up questions about Task Lists. It looks like the Task List will only surface 3 tasks/items, and requires the user to click through to drill down to additional items in the task list. Is that correct, and if so, can that be configured, e.g. show 5 or 6 elements in a task list on the highest layer of the bot?

 

Second question: if a given user completes all of the tasks in a Task List, is that list still accessible to them for future reference? The documentation implies that users won’t see completed task lists, but I wanted to confirm. Thank you!


@rschlette - The new content groups show only the first 5 items, and then the user must click to see more items. 


@rschlette -
Yes to both. Task List widget only shows 3 items and completed lists are hidden from the user. The widget itself gets hidden once all eligible lists are completed by the user.

Good news though! We are exploring options to give users more flexibility in how many items are displayed per widget on the homepage. And to also provide a way to show completed lists in the Task List widget.

We're evaluating how this option should be given and we’d love your input. We've outlined a few options in the attached PDF for reference, do let us know your thoughts.

A few questions we'd appreciate your feedback on:

  • Should this control exist at the bot level, widget level, or group/list level?

  • Would it be helpful to allow granular control, where only certain widgets are collapsed or expanded?

  • Should this setting specify a custom number of items, or should it simply be a toggle between 'Show All' and a fixed default (3/5)?

  • For the Task List widget, would it be good to show all eligible lists to the end user at once, even if they are completed or not?

​​@jadkins.iiq ​@katherine.guenoun we’d love to hear your thoughts as well! Feel free to reply here or let us know if you'd prefer to hop on a quick call to discuss this in more detail.

Thanks!


Thank you, ​@rithvikvarma. For context, most of our multi-bot products are presenting bots that are virtually identical except for content that is differentiated by use case, market segment, or both. So where one of our products has 12 bots (3 use case variations in each of 4 market segments), a scenario where we could put audience logic around the content group(s) would take us down to 1 bot for that whole product.

 

This is where the interest in task lists is rooted: audience logic for content, not the whole bot. My questions about Task Lists were largely about how to misuse/repurpose it since we can't put audience logic around Content Groups.

 

To your questions:

Should this control exist at the bot level, widget level, or group/list level?

Control at the group/list level makes the most sense. This would allow use to have Task Lists that are hidden once complete (like annual compliance tasks, etc) and others that persist as an evergreen reference (like new user onboarding steps). Ideally the latter would go into a Content Group widget if that could be made conditional.

 

Would it be helpful to allow granular control, where only certain widgets are collapsed or expanded?

Yes, it's great to be able to use widgets like categories to organize large amounts of information, but there will always be one widget (for our purposes) that should be fully expanded at the top level of the bot, i.e. the KCB 1.0 'onboarding' tab.

 

Should this setting specify a custom number of items, or should it simply be a toggle between 'Show All' and a fixed default (3/5)?

A toggle between 'Show All' and a fixed default seems sufficient.

 

For the Task List widget, would it be good to show all eligible lists to the end user at once, even if they are completed or not?

Referring back to my opening notes about context, for us the Task List is just a way to get audience logic around the bot content, instead of the whole bot. In a scenario where we could put audience logic on the 2.0 bot's Content Group widget, the current functionality of the Task List is great (hide once completed). The only reason I'd be interested in showing completed Task Lists is because it let's us show that content based on audience logic (essentially misusing it as a conditional Content Group).

 

Thanks again, and I'm happy to provide additional feedback if it's helpful.


@rschlette in the Bot, you can use Audience Logic in Recommendation widget.

There are three widgets for Content today

  1. Content Group - This is to be used when you have content for all users and it supports layouts and better content arrangement
  2. Recommendations - This is to be used when you want to target content based on audience criteria and also benefit from the layouts and content arrangement like in Content Group widget
  3. Task Lists - This is more of a checklist where as an admin you are able to track the progress of tasks and provide a more structured method for users to understand flows. Here similar to Recommendations you can have audience based targeting of the list

 

For your use-cases Task List and Recommendation widget should help achieve what you would like to for content curated for specific audience targeting. Let me know if it does not address what you want to.

 

Thanks


  • Should this control exist at the bot levelwidget level, or group/list level? Group/list level, so we can select which lists can be revisited and which are  one and done, e.g. event promo

  • Would it be helpful to allow granular control, where only certain widgets are collapsed or expanded? Yes

  • Should this setting specify a custom number of items, or should it simply be a toggle between 'Show All' and a fixed default (3/5)? Show all vs. fixed default works for our use cases

  • For the Task List widget, would it be good to show all eligible lists to the end user at once, even if they are completed or not? If a task list is completed, it’d be great if it would show as completed but not show the engagements on the main bot screen (to avoid taking up space) and the user could click View All to slide over to see the completed engagements, so they could revisit them if they’d like. It’d also be great if we could show task lists based on prior completion of other task lists - so if they completed task list 1, then show task list 2. We can’t use the Audience Rules for Recommendations to achieve something like that.


@rithvikvarma Love that you all are looking more into the task lists

Question - Would these controls only be available in task lists and content group lists or would it apply to other content group layouts?

  • Should this control exist at the bot levelwidget level, or group/list level?

    • For our team, group/list level would be ideal as this would give us more control over how task lists might function as opposed to content group lists.

  • Would it be helpful to allow granular control, where only certain widgets are collapsed or expanded?

    • Yes, the more control the better!

  • Should this setting specify a custom number of items, or should it simply be a toggle between 'Show All' and a fixed default (3/5)?

    • I like the idea of a customer number of items as again we can customize per list. This also give us the option to show all. 

  • For the Task List widget, would it be good to show all eligible lists to the end user at once, even if they are completed or not?

    • I wouldn’t say all eligible lists. For our purposes (onboarding) we would want them to see them in chronological order. So if they complete a list, then the next list becomes available. I do love the idea of them being able to access previous lists in case there are articles or engagements they would like to revisit. I would not want them to see future work until they complete the task list at hand. 

 

I love the document you included! Looking at pages 11-13 is exactly what we are looking for as far as progress/past lists. Then if they can click through each of the options on 13 to see the past task list items as well as current items. Would we still be able to show the current task list on the homepage of the bot? This would keep things front and center so the user knows what they need to complete. 


Thanks, ​@aharkut . The Task Lists are definitely the feature that looks most like what we need. The ability to make the content conditional based on user/account attributes is perfect. There’s just the above notes about top-level visibility and persistence after completion.

 

For us, the perfect implementation would be the current functionality to apply audience logic to Task Lists, but applied to the Content Group.


Hi ​@rschlette , The “Recommendations” widget in the Bot is for the same purpose - to be able to configure Content Groups + Audience Rules

 

 

 


Thanks, ​@aharkut. Recommendations will highlight certain content for a sub-segment of bot users, but it doesn’t filter the bot content. Even more importantly, Recommendations just surface a card that needs to be clicked through to get to the recommended content, and our design teams want content on the top level of the bot.


Hi ​@rschlette , in the new bot editor, an user dont have to click a card to get through the content. The recommendations content is surfaced on the Bot itself based on the layouts used.

 

Thanks,

Abhilash


​ ​Hello ​@Sruthimalla ​@aharkut ,

We have been trying to implement new kc bot, but we require users to be taught how to use it effectively. For that purpose, we created a guide for a sort of walkthrough for new kc bot and to our surprise we cannot choose kc bot as elements for new guide to be active. How can we train users if we cannot even choose elements from px. 


It’s true that you can’t map guide elements with in the KC bot iframe widget, but you could make a short screen capture video to demonstrate KC Bot navigation in a guide engagement. Even a series of GIFs presented in dialog steps will accomplish the same thing