Thank you for joining us for ASAE’s AI In Action Demo Day.

You Asked Great Questions;
Here’s Where We Answer Them.

On June 24, FUSE Next had the privilege of kicking off ASAE's AI in Action Demo Day. Thank You, ASAE AI in Action Demo Day attendees for spending part of your day with us.

As first-time participants, we weren't sure what to expect. What we found was a thoughtful, engaged audience asking exactly the right questions about AI, content, governance, search, and the future of association knowledge. The problem was we didn’t get to address all of the questions you posed in the chat. It’s not because we were dodging them but because we ran out of time!

Let’s fix that now below.

The questions raised during our session reinforced something we strongly believe: that your association's greatest AI advantage isn't the technology - it's the knowledge you've already created. FUSE Next exists to help associations put that knowledge to work.

Does Fuse Next provide consultative services to identify some of those ‘hidden’ troves of content?

FUSE ‘puts on our consultant hats’ with customers before and during the onboarding process to advise them on best practices based on our experience and what other customers have done/do. We encourage customers who have done work with consultants to share that work or to connect Team FUSE with them so we can collaborate.

Re. the line between nonmember and registered member data: is a non-logged-in user informed via AI Insights or the chatbot when a response is limited due to hitting a “paywall”?

Yes! Since FUSE isn’t a black box the flexibility here is impressive. Some customers show the first ‘X’ words (e.g. 100), blur out the remainder of the response, and ask a user to Sign-In or Join to see more. Others show an alert that ‘X’ content items are being suppressed and to Sign-In or Join to display them. Some customers show padlock iconography next to items… You can really get in the weeds and show/hide items based on what you know about a user based-on, for example, your AMS record of them. In other words, countless options are available - let’s make it happen together!

The taxonomy in the left rail - is it extracted from the content by AI or defined by the customer? or both?

There’s no substitute for a subject matter expert (i.e. human affiliated with your organization). That’s always the first choice. FUSE receives that taxonomy from the systems it connects to (e.g. community, AMS, LMS, CMS, publisher, video repository). Need to update a taxonomy item? Update it in the respective system you already use and the next time FUSE syncs with that system, the taxonomy will be automatically reflected in the FUSE user interface. If you need some help classifying your content, FUSE can help there too with some AI magic. :) A typical use case here could be classifying legacy content after which, moving forward, staff classifies new content being entered into your systems of record.

Does FUSE retain my search queries and chat questions so they can be reviewed for analytics?

Even better, sticking with the FUSE mantra of ‘you don’t have to change a thing about your current workflow’ - FUSE pushes all of the metrics to your existing Google Analytics (GA4) account. What you’re asking for here are table stakes - yes, you’ll get that in spades. But you’ll also get all sorts of other metrics - what filters users are selecting, what source(s) they ultimately go to based on their query, numeric counts of the amount of content FUSE had to address a query (low numbers indicate areas where your organization perhaps needs to beef-up its content), and more. The best is that you can view these metrics alongside all of your other Google Analytic metrics and create sophisticated reports. Every customer that connects to 4 or more sources gets our Analytics Assist™ service where FUSE helps you configure reports, setup custom conversion tracking, and more.

When you say member directory - can you connect FUSE to your AMS?

Yep! 100%. Using the AMS’ API. Typical data FUSE would get from an AMS are products, events, and - yes - member data. FUSE only needs the member data, however, if you wanted something like a member/provider directory like GCCA or CBA has. If you’re running iMIS, FUSE can connect to RiSE as well.

To what extent does FUSE Next help identify potential content repositories?

Please see the very first answer above under “Does Fuse Next provide consultative services to identify some of those ‘hidden’ troves of content?” It’s the same answer here - in short, we’re a nice bunch of people to work with and we’ll always advise customers on best practices. FUSE is incentivized to help you find all of the potential content repositories because it’s a big part of how we’re paid.

At a high level - How you address data readiness in FUSE next (e.g. quality, governance, and usability)

FUSE typically needs these four elements for each content object ingested. That’s the whole of it. However, the quality, governance, usability part of this question: the tried and true garbage in, garbage out rule applies. At the end of the day if you don’t have good content (that adheres to these three rules and some others) you won’t get good results from any tool - FUSE or otherwise.

Did anyone see the pricing slide? I missed it.

FUSE has a sliding scale of pricing based on the size of your organization. This is so small groups can benefit from FUSE just as much as the big guys. At FUSE, a third of our customers are ‘small’ (<$5mm in annual revenue), a third are large (>$30mm), and a third are in-between. FUSE’s pricing is based first and foremost on the number of content sources FUSE is connecting to. One option is to scale FUSE over time - connect to 2 or 3 sources to start then add more as budget becomes available?

We all know that information across our online properties gets stale or old, how does the AI model know which is older and which is newer and to not present user with the obsolete answers?

FUSE isn’t a black box - we can tweak the algorithm to suit and, by default, FUSE favors more recent items. The “catch” is making sure to specify which date FUSE should use for this purpose. Most content items have several dates associated with them - e.g. publish date, last edited date, start date, end date, issue date… During FUSE’s on-boarding process Team FUSE will work with you to ensure we’re using the best date for each content type (e.g. if it’s an event, use the event start date, if it’s a journal article use the issue date, if it’s a general 'web page,’ use the last edited date).

Curious how FUSE Next could work in your environment or support your specific use case?

A personalized consultation lets you see FUSE Next in action in your context - we can walk through real-world scenarios, you can freely ask questions, and further explore how others are using it across their content, systems, and user experiences.