Return to blog

New Release
Content management, reusable components, and conversation scoping tools in VoiceXD

We are excited to launch our new content manager enabling you to manage all of the utterances, assistant responses, and intents in your designs and allowing you to convert assistant responses into reusable components to help you manage and scale your assistant's content faster.  

We have also added more advanced functionalities to scripts which allows you to group them into different categories based on their specific topics and create scopes for an individual scripts which can allow users to seamlessly switch contexts while chatting with your assistant while keeping track of the conversation history up to that point.

What we'll cover

  • Using the content manager to track and modify content
  • Creating components to scale your content design
  • Building more advanced conversation designs with script groups and global/local scripts

Content management in VoiceXD

Try it out with our interactive demo!

No need for Excel: Manage, edit, and search for any content

The content manager is your one source of truth for all of your assistant's content. You can quickly find and make changes to any assistant response, user utterance, or variable within your conversation designs. You can also quickly navigate to a particular piece of dialogue by clicking on the script in which it is located making it easy to navigated between the content manager and designer.

Designing with or without intents

In VoiceXD, you can create and test entire conversational assistants without having to use intents and we give you the flexibility to define them where and when you want them. We treat intents like re-usable components. You can attach them to any user input in your designs with the click of a button and as easily detach them if you no-longer want to have the input connected to an intent. In the content manager, you can manage all of your user input content including intents and utterances and create new intents.

When you convert a user input into an intent you have the option to merge all or some of the content from that input into the intent. This enables you to preserve any pre-existing content you may have written, without the need to re-add it to your intent manually.

Assistant response design with components

We also allow you to create components for your assistant responses so that you can re-use commonly used responses throughout your design. These response components include variations of responses, no-match responses, and no-input responses, which saves you time and effort by eliminating the need to rewrite content and enabling you to modify content at scale.

In the content manager, you can view all unattached assistance responses and response components, while in the designer, response components are identified by a purple component label. Unattached responses and response components have similar functionality to managing intents and utterances.

Updates reflect across components in real-time

All changes made within dialog designer or content manager for an utterance, assistant response, intent, or response component are immediately reflected in real-time. This ensures that your designs and all instances of your intents and components are always up-to-date with the latest content updates.

How components and the content manager can help each member of your team

For conversation designers, the content manager provides a comprehensive overview of all user and response dialogues within a project as well as the ability to jump to the specific location where a particular utterance or response is being used. This makes it easier to track and manage conversational flows and identify gaps. You can also make changes to any utterance, response, intent, or response components in the content manager and those changes will be reflected in your designs. By converting user utterances into intents and assistant responses into reusable components, designers can create a consistent conversational style and ensure that the assistant responds accurately to user queries.

For developers, the content manager enables easy navigation and verification of conversational components. It allows them to quickly locate, evaluate, and leave comments on specific dialogues, reducing development time and effort.

For AI trainers, the content manager assists them in annotating user utterances and generating training data by providing a centralized location to view all user utterances and corresponding intents. AI trainers can quickly access the conversation flows containing these utterances to gain context on how to accurately map them to the appropriate intent.

There's much more coming!

This is our first version of the content manager and we have many more updates to come that will supercharge your workflow including: AI generated intents and components, importing and exporting content to and from our platform, and creating real-time LLM generated assistant responses.

Using script groups to design for context-switching and advanced dialog management

What are scripts in VoiceXD?

Scripts give you the ability to choose how you structure various conversation flows. Each script commences with a user input (which does not have to be marked as an intent), and within it, you can design a conversational flow that incorporates a variety of scenarios and error management.

You can create general and comprehensive scripts that cater to a variety of use cases, such as handling all customer support queries in a healthcare conversational assistant or, you can also create more specific scripts that target particular cases, such as customer support for a specific medical device or medication.

What are script groups?

Script groups allow you to group conversation flows according to their related topic. For instance, within a banking assistant, you may create separate groups for "Customer Support," "Payments and Transfers," "Bill Payments," etc.

You have the convenience of easily moving scripts between groups simply by dragging them, allowing you to modify or alter your groups as your assistant expands.

Defining the "scope" of a script

Scripts can also be accessed from each other. You can define a script's scope by choosing whether it can be accessed from any other script in the project (global) or only scripts within the same group (local). This gives you the flexibility to allow a user to jump between different conversation topics while maintaining a memory of the conversation thus far. It also allows you to control when a user can access certain conversations.

Selecting which scripts can be reached from a specific turn

At a particular assistant response step within your script you can choose which global and local scripts can be accessed (if any) to control context-switching at an even more granular level. By default, all global and local scripts are accessible. If you are designing a chat assistant, you have the option to specify which scripts users can navigate to through a button, if the first input in that script includes a button.

We're really excited to get these new tools into the hands of conversation designers and see all of the powerful assistants that can be built. We'd love to hear your thoughts and feedback so, give it a try and let us know what you think at!

Take your conversation designs to the next level with VoiceXD

Start designing