--- title: "Resource Center" slug: "resource-center" description: "Empower users with a personalized resource center in your app, featuring customizable help blocks, knowledge base search, and seamless user support." tags: ["Add my own chatbot", "Intercom", "Zendesk", "chatbot", "Resource Center", "Help Widget"] updated: 2026-11-13T16:29:34Z published: 2026-11-13T16:29:34Z canonical: "help.userflow.com/resource-center" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.userflow.com/llms.txt > Use this file to discover all available pages before exploring further. # Resource Center The Resource Center is a help menu inside your app. Users open it from a button (or any element you choose) and see a list of blocks you set up: checklists, flows to start, knowledge base search, the Adoption Agent, announcements, contact options and more. You can show different blocks to different users. ## How the Resource Center works We provide a default button in the lower-right corner of your app to launch the Resource Center; however, you can customize the user experience by using an element (e.g., a button, icon, or menu item) in your app to trigger the Resource Center instead of the default button or programmatically control so it appears without a visible trigger (e.g., it appears when specified conditions are met). When you build a Resource Center, add the content blocks that best meet your users’ needs. ![Resource Center launcher button, collapsed](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/collapsed.png) When users click the button or app element, it expands to a list of customizable blocks, including free-form messages, links to flows, checklists, support contacts, announcements, Adoption Agent, knowledge base search, and more. ![Resource Center opened, showing its list of blocks](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/expanded.png) ## Creating a Resource Center 1. Select **Resource centers** in the sidebar. 2. Click **Create resource center**. 3. Enter a name and click **Create resource center**. ![Create resource center dialog with a name field](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(447).png) ## Customize how your Resource Center is Launched By default, the Resource Center places a subtle help icon in the lower-right corner of your app. Alternatively, you can use an element in your app, such as a button, icon, or menu item, to trigger the Resource Center in a way that seamlessly integrates with your product experience. When you add or edit a Resource Center, choose one of the following Launcher types: ![Resource Center launcher type options](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(452).png) - **Default:** Places a default help button in the lower-right corner of your app. ![Default Resource Center launcher button in the lower-right corner](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(453).png) - **Custom:** Choose an element in your app that, when clicked, will open the Resource Center. See [Selecting a custom element to launch the Resource Center](/docs/resource-center#selecting-a-custom-element-to-launch-the-resource-center). - **None:** Userflow will not determine how your Resource Center is launched, and there will be no visible activation for the Resource Center. Use this option to control your Resource Center programmatically via [Userflow.js](/userflow/docs/userflowjs-installation). ### Choosing a Resource Center Launcher type Selecting the appropriate launcher type depends on how you want to integrate the Resource Center into your application. Use these recommendations to identify the most suitable option for your app and desired user experience. | **Default Launcher** | | --- | | **Behavior** | Places a standard Userflow help button in the lower-right corner of your app (configurable in Theme settings). | | **Best For** | Teams looking for a “plug-and-play” solution that requires zero coding or custom design. It ensures high visibility for your content with minimal setup. | | **Unread Count/Badge** | Visible (on the button) The red notification badge appears directly on the button. | | **Boosted Announcement Style (Pop-out)** | Tethered to the Resource Center (with notch) Will appear next to the button, with a visual notch (arrow) pointing toward it, indicating the announcement's source. | | **Example** | You want a standard floating help button in the bottom-right corner of your app that works immediately upon installation. | | **Custom Launcher** | | --- | | **Behavior** | You can select an existing element in your app that, when clicked, will open the Resource Center. | | **Best For** | Seamless integration where you want the help experience to feel like a native part of your app’s navigation rather than an overlay. | | **Unread Count/Badge** | Visible (On Element) The notification badge is attached to the corner of your custom element. | | **Boosted Announcement Style (Pop-out)** | Tethered to the Resource Center (with notch) They will appear next to the element with a visible notch (arrow) pointing toward it, indicating the announcement's source. | | **Example** | You want to anchor the Resource Center to an existing help link in your applications navigation bar or sidebar menu, rather than having a separate floating button. | | **No Launcher (None)** | | --- | | **Behavior** | Userflow will not render a launcher button. This is typically used if you want to open the Resource Center exclusively via a custom button using userflow.toggleResourceCenter(), or if you intend to control the launcher’s visibility programmatically. | | **Best For** | Advanced use cases that require full programmatic control over when and how the Resource Center appears. | | **Unread Count/Badge** | Hidden | | **Boosted Announcement Style (Pop-out)** | Floating (no notch) Because there is no visible anchor target, they will appear on the screen (based on the Resource Center settings) without a notch. | | **Example** | You want to trigger the Resource Center only for a set of paid users who navigate to a specific page and click a button. *Note: Boosted announcements will continue to function even if the launcher is hidden.* | ### Boosted Announcements & Custom Resource Center Launchers Boosted Announcements will behave consistently, whether or not you use a custom launcher, no launch trigger, or the Userflow default. If you choose a custom element in your app, Boosted Announcements will appear with that element. If you select **None** as the launcher type, Boosted Announcements will appear in the default position of the Resource Center. Ensure Boosted Announcements don’t interfere with other elements of your app when you customize the launcher experience. #### Selecting a custom element to launch the Resource Center 1. Select the **Custom** launcher type. ![Custom launcher type selected in the Resource Center settings](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(473).png) 2. Click **Select element.** 3. Enter your app URL and click **Select element**. ![Entering your app URL to select an element](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(474).png) > [!NOTE] > Using the ‘Go Manual’ selection option > > If an element requires entering its CSS, unique ID, or custom data attribute, use the **Go Manual** option to select it. [Learn more](/userflow/docs/tooltip-element-selection#go-manual). 4. Locate and select the element you want to use as the Resource Center launcher. **Navigating to the element:** If you need to navigate to another page in your app to locate the element, click **Navigate to another page** in the element selection bar to pause recording your selection until you locate the element. When you are ready to select it, click **Select element here** and then select the element. To move the bar up or down on the screen (if it blocks the element you’re trying to select), use the up or down arrow. ![Selecting a custom element to open the Resource Center](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(476).png) 5. Configure your Resource Center blocks as needed and publish it when you’re ready! ## Controlling the Resource Center via Userflow.js You can use Userflow.js to programmatically control how Resource Center operates. Refer to the [Userflow.js API Reference](https://help.userflow.com/docs/userflowjs-reference) for details. Expand each method's description on this page to see how it affects the Resource Center launcher, unread counts, and Boosted Announcements. #### setResourceCenterLauncherHidden() **Behavior by Launcher Type** Programmatically controls the visibility of the Resource Center launcher button, the unread count badge, and the visual anchoring of boosted announcements. **Parameters** - `hidden` (boolean): `true` to hide the launcher; `false` to show it. **Behaviour by Configuration** **1. Launcher Type: None** *Use this configuration when you do not want a launcher by default.* - `true` **(Default State - Hidden):** - **Launcher:** Remains hidden - **Unread Count:** Hidden - **Boosted Announcements (Pop-out):** Floats independently with no notch (no anchor point) - `false` **(Override - Show):** - **Launcher:** Forces the **Default Userflow Launcher** to appear by overriding the configuration - **Unread Count:** Displays on the default launcher - **Boosted Announcements (Pop-out):** **Tether** to the default launcher with notch **Note:** If you use `userflow.setResourceCenterLauncherHidden(false)` via Userflow.js while using the None type, it will force the Default launcher to appear. In this state, the badge will become visible, and boosted announcements will switch to the "Tethered" style. **2. Launcher Type: Custom** *Use this configuration when you are using a custom DOM element (CSS selector) as your launcher.* - `true` **(Disable):** - **Launcher:** The custom element specified in your settings stops functioning as a launcher - **Unread Count:** Hidden - **Boosted Announcements (Pop-out):** **Float** independently (no anchor point)with no notch - `false` **(Enable):** - **Launcher:** The **custom element** remains the active trigger - **Unread Count:** Displays on the custom element - **Boosted Announcements (Pop-out):** **Tether** to the custom launcher element with a notch. **3. Launcher Type: Default** *Use this configuration when using the standard Userflow launcher.* - `true` **(Hide):** - **Launcher:** Hidden. - **Unread Count:** Hidden. - **Boosted Announcements (Pop-out):** **Float** independently with no notch (no anchor point). - `false` **(Show):** - **Launcher:** **Default Launcher** is visible. - **Unread Count:** Displays on the launcher. - **Boosted Announcements (Pop-out):** **Tether** to the default launcher (appearing with a notch). #### userflow.openResourceCenter() **Behavior:** - **Boosted Announcements & Badges:** Opening the Resource Center temporarily hides active **Boosted Announcements** and the **Unread Count Badge** to prevent visual clutter and overlap during use. - **Unread Count:** The unread count persists until users view specific announcements. If unread announcements remain, the badge reappears with the same count when the Resource Center is closed. #### userflow.closeResourceCenter() **Behavior:** - **Boosted Announcements** and the **Unread Count Badge** will immediately reappear. - **Unread Count:** Closing the Resource Center restores the previous UI state. **Boosted Announcements** and the **Unread Count Badge** will immediately reappear unless the announcements were marked as read/dismissed during the session. #### userflow.toggleResourceCenter() **Interaction with Boosted Announcements:** The Resource Center view is prioritized when opened. - **On Open:** Active **Boosted Announcements** (e.g., Pop-outs, Modals, Banners) and the **Unread Count Badge** are temporarily hidden. - **On Close:** These elements automatically reappear to their previous state (unaffected). ## Customizing Resource Center Blocks The Resource Center is a collection of blocks you can modify as needed. It is initially populated with blocks that you can personalize or remove. 1. Click a block to edit its settings (e.g., name or icon) in the right-side panel that appears. You can also delete a block there. 2. Click **Add block** at the bottom to add more blocks. ![Resource Center builder with block settings in the right-side panel](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(460).png) 3. Click **Preview** to view a live preview of the Resource Center running inside your app. 4. Click **Publish.** You can optionally control when the Resource Center appears by using the **Only show Resource Center if** option. This is useful if it should not appear on certain pages, or if it should only be visible to specific users/segments. You can also build multiple Resource Centers if you have experiences you want to show different segments or on different pages, for example. ![Resource Center audience and multiple Resource Centers settings](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(263).png) ### If you have more than one Resource Center Each user sees one Resource Center at a time. If a user matches more than one, Userflow shows the one with the highest priority. If two have the same priority, the one created first wins. Userflow decides which Resource Centers a user matches using only each one's **Only show resource center if** conditions. If a newly published Resource Center isn't showing, an older one is usually winning. To fix it, either: - give the one you want to show a higher priority, or - split the targeting, for example by page, so each user only matches one. ## Block types We support many block types, each with its own unique functionality and purpose. Each block type not only serves a specific function but also enhances the overall user experience by providing features tailored to the requirements of diverse applications. > [!NOTE] > Availability of block types > > Note that some block types (e.g., Checklist) will disappear from the list of available blocks if they’ve already been added to the Resource Center. ### Checklist block We recommend adding a **Checklist** block in your Resource Center at all times. When the Checklist block is present, the user's active [checklist](/userflow/docs/checklists) is automatically integrated into the Resource Center. You can enhance the user experience using [segmentation](/userflow/docs/users-and-segments) to deliver appropriate content to specific users or company groups and implement [no-code event tracking](/userflow/docs/no-code-event-tracking) to accurately monitor progress. ![Resource Center showing the active checklist block](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/expanded-with-checklist.png) The checklist’s text and number of tasks not yet completed (if any) will also show in the Resource Center launcher. ![Resource Center launcher showing checklist text and tasks left](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/collapsed-with-checklist.png) If you don’t include a checklist block in your Resource Center, the checklist will work stand-alone and be displayed next to your Resource Center by default. You can also [embed checklists](/userflow/docs/embed-a-banner-or-checklist) in your app to provide a different on-brand experience for your users. ![Checklist shown on its own next to the Resource Center](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/standalone-checklist.png) ### List of flows/checklists block The **List of flows/checklists** block enables your users to find and start flows and checklists on demand. When users click it, it will show a searchable list of flows. ![Searchable list of flows inside the Resource Center](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/flows-route.png) If you click the block in the builder, you can edit its icon and name, and select which content items will be listed. ![List of flows/checklists block settings](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(454).png) > [!NOTE] > **Note:** Flows/Checklists are not included by default in this block. You must add each individual item you want to list. This avoids the possibility of exposing restricted content inadvertently. You can either sort the list alphabetically or switch from **Sort alphabetically** to **Sort manually** and drag and drop items to reorder. You can optionally override the public names of items in the Resource Center. Open an item’s builder, click **Show advanced settings,** and look for **Public name in Resource Center**. Enter the desired public-facing title. ![Public name in Resource Center setting in a flow's advanced settings](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/flow-settings-v2.png) ### Knowledge base block The **Knowledge base** block enables your users to search your existing knowledge base without leaving your app. ![Knowledge base search results inside the Resource Center](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/knowledge-base-route.png) Clicking a search result will open the article in a new tab. There’s also a link button at the top that takes the user to your knowledge base's home page. We currently support searching directly in the following knowledge base providers: **Public/Unauthenticated search** - Freshdesk - HubSpot - Zendesk **Authenticated search** - Intercom - Zendesk For all other knowledge base providers or home-built documentation sites, use one of the following options: - **Google Search:** Provides similar results to Google.com when searching for `site:yourdomain.com/path`. This requires that your site is indexed by Google. - **Adoption Agent:** If you’re using our Adoption Agent, you can utilize its sources for searching. This requires that your Adoption Agent is trained and published. You don't have to use the Adoption Agent for chat: if all you want is knowledge base search, you can use it for search only. Searching through the Adoption Agent costs nothing extra. Using the Adoption Agent as a source also lets you perform authenticated searches in Salesforce knowledge bases. See [Set up your Adoption Agent](/userflow/docs/ai-assistant). - **Notion:** if your help center is a public Notion site, add it as a website source on your Adoption Agent with **Render JavaScript** turned on, then choose **Adoption Agent** as the provider here. You can also use **Google Search** if the site is indexed. Private Notion workspaces aren't supported. Choose your **Knowledge base provider** and **Knowledge base URL** in the builder’s side panel. ![Knowledge base provider and URL settings for the block](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/knowledge-base-block-settings.png) #### Suggest articles for the current page You can make the Knowledge base block show the help articles that fit the page your user is on, without them typing a search. Use the block's **Default search query** field with a Liquid template. `{{ page_url }}` is built in, so you don't need to send it yourself. 1. Click the Knowledge base block in the Resource Center builder. 2. In **Default search query**, map your pages to search terms. For example: ```plaintext {% assign on_billing = page_url | url_matches: '/settings/billing*' %} {% assign on_reports = page_url | url_matches: '/reports*' %} {% if on_billing %} billing {% elsif on_reports %} reports {% else %} getting started {% endif %} ``` 3. Preview the Resource Center on each page to check the results. Assign the result of `url_matches` to a variable first. Liquid doesn't allow filters inside `if` statements. One Knowledge base block with a dynamic query covers every page, so you don't need a separate launcher for each one. See [Liquid templates](https://help.userflow.com/docs/liquid-templates). ### Contact block We recommend putting a **Contact** block at the bottom of your Resource Center. It’s a great way to connect users with your support team. ![Contact block with Email, Phone and Chat options](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/contact-block.png) When users click the Email or Phone icon, they’ll see a page with information, for example, your support email address: ![Support email page opened from the Contact block](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/email-route.png) When they click on the Chat icon, the Resource Center will close, and your live-chat provider will be activated: ![Live chat opened from the Contact block](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/intercom.png) Click the Contact block in the Resource Center builder to customize which of the Email, Phone, and Chat options are displayed, edit the text, and choose your live-chat provider. ![Contact block settings in the Resource Center builder](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/contact-block-settings.png) The Resource Center currently integrates with the following live-chat provider options (see [Help desk integrations](/userflow/docs/chat-and-knowledge-bases)): - Crisp - Freshchat - Help Scout - HubSpot - Intercom - Zendesk For all other chat providers, you can build a custom chat connection using JavaScript. ### Action block **Action** blocks are ideal for any custom action you want users to perform in the Resource Center. It works similarly to a button in a flow. The block’s actions will be executed when a user clicks it. You can use an Action block to navigate the user to a page, start a specific flow/checklist, or execute custom JavaScript that performs any necessary task. ![Action block settings](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(456).png) To open Beamer Feedback from an Action block, see [Beamer Feedback block](/userflow/docs/implementing-beamer-feedback-block-in-a-resource-center). ### Message block If you want to display a free-form message, such as an announcement or a greeting, in your Resource Center, then the **Message** block is for you. ![Message block in the Resource Center](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(457).png) ### Sub-page block If you want to display a larger free-form message, such as a list of resources or an embedded video, in your Resource Center, then use a **Sub-page** block. ![Sub-page block content](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(461).png) When the user clicks the block, the **Sub-page content** will be displayed in a nested route with a **Back** button. ![Sub-page opened inside the Resource Center with a Back button](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(463).png) #### Add a video to your Resource Center To show a video in the Userflow Resource Center, add a **Sub-page** block and [embed the video](/userflow/docs/embed-videos-forms-and-images) in its **Sub-page content**. When users click the block, the video opens on its own page inside the Resource Center, with a **Back** button. 1. Open your Resource Center in the builder and click **Add block**. 2. Choose **Sub-page** and give it a name, such as "Watch the intro video". 3. In **Sub-page content**, embed your video. 4. Click **Preview** to check it, then **Publish**. For how to embed a YouTube, Vimeo, Loom or other video, and which video settings let it play, see [Embedding videos, images, and forms](/userflow/docs/embed-videos-forms-and-images). ### Announcements block Announcements in Userflow let you update users about new features, fixes, events, and more, all within the Resource Center. Read more in the [Announcements guide](/userflow/docs/announcements). ### Adoption Agent block Adoption Agent delivers automated answers to your users’ questions within your app, leveraging your knowledge base and website, and powered by OpenAI models that Userflow keeps up to date. See [Set up your Adoption Agent](/userflow/docs/ai-assistant). ## Conditionally display a block You can make a block appear only when a condition is met by using the **Only show block** setting. A good example is if you have an **Action** block that (re)starts a checklist, then it’s a good idea to only make it show up if the checklist is not already active: ![Only show block condition for an Action block that restarts a checklist](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(464).png) Another example is to conditionally show help articles on specific pages: ![Only show block condition showing help articles on specific pages](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(465).png) ### Example: Show a CTA to trial users only You can use attribute targeting to show different content based on a user's subscription status. For example, to display a "Talk to an Expert" button only to users currently on a free trial: 1. Add an Action block to your Resource Center. Label it "Talk to an Expert" and configure its action (for example, open a booking link or start a live chat session). 2. In the block settings, enable **Only show block if**. 3. Add a condition on your trial attribute, for example, `plan_type = "trial"` or `is_trialing = true`. Use whatever attribute your team sends to Userflow to identify trial users. 4. Save and publish. Users on a paid plan see your standard Resource Center. Trial users also see the "Talk to an Expert" block. The same pattern works for upgrade prompts, role-specific help content, or any experience you want to personalize by user segment. ## Conditionally show the Resource Center To conditionally show or hide the Resource Center, toggle **Only show resource center if** conditions. For example, this can be used if you only want to display the Resource Center on specific pages, or when particular elements are present or absent. If an element blocks the Resource Center, it is often better to adjust the Resource Center's z-index (via theme settings).![Only show resource center if conditions](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/only-show-rc.png) ## Global search If your resource center has at least one searchable block (currently, only **Knowledge base** and **List of flows/checklists blocks** are searchable), a global search icon will appear in the header: ![Global search icon in the Resource Center header](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/search-icon.png) Clicking it and searching will search across both flows in your Userflow account and articles in your knowledge base: ![Global search results across flows and knowledge base articles](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/search-results.png) ## Theming Under **Settings** > **Theme,** you can customize the look of your resource center. Use the **Base colors** section to quickly adjust the colors. Read more in our [Themes guide](/userflow/docs/themes). Use the **Resource Center** section to control where the resource center appears, as well as its size and padding. You can also change the resource center launcher appearance, for example, if it should have the default icon or a plain text question mark, as well as if it should show the active checklist text, the resource center launcher text, or no text at all. ![Resource Center section of the theme settings](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/theming.png) ## Dividers and badge appearance **Dividers between blocks.** By default the Resource Center auto-inserts divider lines between your blocks. If you'd rather place dividers yourself (for example, to group related blocks or remove separators entirely), go to **Settings → Theme → Resource Center** and toggle **manually inserted divider lines** instead of the default auto-inserted ones. See [Customizing Themes](/userflow/docs/themes) for the full Resource Center theme options (position, size, padding, colors). **Unread count badge.** The red unread badge appears automatically wherever your launcher lives: - **Default launcher**: on the button. - **Custom launcher**: attached to the corner of your chosen element. - **None**: hidden (no anchor to attach to). The badge's colors are set in **Settings → Theme → Resource Center**, under **Unread announcements badge**. You can change both the background color and the text color there. To hide the badge entirely, hide the launcher with `userflow.setResourceCenterLauncherHidden(true)`. This also hides the launcher itself and floats any boosted announcements with no notch. The unread badge and the Resource Center launcher icon are two different things. The launcher icon's size is set under **Settings → Theme → Resource Center → Resource Center launcher button**, and changing it does not change the badge. The badge's size and position are fixed. Colors are the only part of its appearance you can change. ## Resource Center Best Practices Use these proven best practices and strategic use cases to help you maximize the impact of your Resource Center. Whether you’re implementing your first help widget or optimizing an existing one, you can create a seamless self-service experience that enhances user satisfaction and drives product adoption. ### Essential Elements - **Checklists:** Drive user progress with visual milestones that create a sense of achievement. - **Contact options:** Provide clear escalation paths when users need human help. - **Smart visibility:** Show the right resources to the right users at the right time using conditional display. - **Role-based centers:** Deliver personalized experiences by creating separate centers for different user segments. - **Brand consistency:** Match your app's look and feel effortlessly with configurable themes. ### Self-Service Support - **Knowledge base search:** Users find answers without leaving your app. - **Adoption Agent:** Instant, automated answers powered by your documentation and latest LLMs. - **Multi-channel escalation:** Hand users off to your live-chat provider. The Contact block supports Crisp, Freshchat, Help Scout, HubSpot, Intercom, and Zendesk. ### User Activation & Adoption - **Progressive onboarding:** Guide new users through setup with checklist-driven milestones. - **Feature discovery:** On-demand tutorials help users unlock product capabilities. - **Announcements:** Keep users informed about updates, fixes, and events. ### Advanced Customization - **Custom workflows:** Trigger actions, navigate to key pages, or execute JavaScript. - **Dynamic content:** Deliver messages, videos, and sub-pages based on user context. - **Segmented experiences:** Tailor content by plan, product area, or user behavior. ### Measure & Optimize - **Track engagement:** Identify your most valuable content through [interaction analytics](/userflow/docs/analytics#resource-center-analytics). - **Test configurations:** [A/B test](/userflow/docs/ab-testing) layouts and content to maximize user satisfaction. - **Refine targeting:** Use behavioral data to surface the most relevant resources. ## Troubleshooting If your Resource Center isn't working as expected, check these common issues: ### Resource Center not appearing **Check installation:** Make sure Userflow.js is installed and `userflow.identify()` has been called. **Check launcher settings:** Verify your launcher type (Default, Custom, or None) is configured correctly in Settings → Resource Center → Launcher. **Check targeting rules:** Go to your Resource Center settings and review "Only show resource center if" conditions. Make sure the current user matches those rules. **Check for another Resource Center:** only one Resource Center shows per user. If another published Resource Center also matches this user and has a higher priority, or the same priority and an earlier creation date, it shows instead. See [If you have more than one Resource Center](/userflow/docs/resource-center#if-you-have-more-than-one-resource-center). **Preview session closed, and the Resource Center disappeared:** the Resource Center (and its launcher) only shows during an active Preview session if it's actually published to the environment you're testing. If it isn't published yet, the widget appears while your Preview session is open but disappears when the session ends. It isn't a bug, and it won't reappear until you publish. Confirm via Settings → Environments that the Resource Center is published to the environment you're viewing, not just previewed. ### Custom launcher not working **Element not found:** Open the browser Console and run `document.querySelector('YOUR_SELECTOR')`. If it returns null, Userflow can't find it either. Update your selector in the Resource Center settings. **Element loads after Userflow:** If your launcher is rendered by React/Vue/Angular after page load, call `userflow.updateResourceCenter()` after the element appears. ### Works in staging but not production **Check environment token:** Make sure your production site uses your production Userflow token, not your staging token. **Check publish status:** Verify the Resource Center is published to your production environment in Settings → Environments. ### Resource Center is empty **No content published:** Publish at least one Resource Center item (Announcement, Checklist, or link) and confirm its audience settings match the current user. ### Adoption Agent missing from the Resource Center If the Resource Center opens but the Adoption Agent is gone, work through these in order. 1. **A usage limit was reached.** When an Adoption Agent reaches one of its agent-level limits, Userflow hides that agent from the Resource Center for 24 hours. When your account reaches its global limit, every Adoption Agent is hidden for 24 hours. Userflow sends an email when this happens, and hiding or restoring the agent can take up to 10 minutes. See [Adoption Agent: Agent-level limits vs. Global limits](/userflow/docs/usage-limits-vs-global-limits). 2. **The agent or the Resource Center isn't published to this environment.** Publishing the Adoption Agent doesn't make it visible on its own. It also needs an Adoption Agent block in a Resource Center, and both need to be published to the environment you're viewing. 3. **The block has conditions.** If the Adoption Agent block uses **Only show block if**, the current user has to match those conditions to see it. If a single user sees a message saying they've reached their daily limit, that's the per-user daily limit. The agent stays in the Resource Center for everyone else, and that user can ask again the next day. ### Resource Center still not working? Contact support If the Resource Center still isn't working, check it with the [Userflow Debugger](/userflow/docs/using-the-debugger-for-auto-start-conditions), or contact support at support@userflow.com. Include your browser type, the name of the environment you're testing in (for example, Production), and that environment's Userflow.js Token from **Settings → Environments**. ## Related - [Getting started with Userflow](/about-userflow-engagement-types-2.md)