Skip to main content
University Header

Conversations experience actions

  • June 30, 2025
  • 0 replies
  • 411 views

Kevin Lewis
Forum|alt.badge.img+5

 

When building an experience for Qualified Conversations, experience actions form the steps of your experience that a visitor will go through. Think of them as the building blocks of Qualified experiences.

This article covers the experience actions that are relevant for Conversations in the Qualified Messenger. For general experience actions, see here. For actions related to Qualified meetings, see here.

Show a custom greeting

A custom greeting is often the first step of a conversations experience, especially for a rules-based chatbot.

Show a custom greeting can only be used as the first message sent to the visitor, before the messenger has been opened by another step.

Configuring the custom greeting includes the messaging, style, and buttons that make up the greeting. Note that the color palette, logo images, and button shapes are controlled by your messenger theme settings.

There are a few elements to customizing custom greetings:

Greeting style

There are four greeting styles to choose from, which will control the look and feel of your greeting:

AD_4nXcqNo_5G7NKC4Y0m1S6Sm_SPpaeUPw-jugtA-lNJkkOkG9P8bReR1xRNcDzvcUC-nmvUpwq8bASXNNDnTSeoTWGWM78o5pSc4uxF6MpvVkAZgSNhK070-oZXwX5Pj_9wC3is7wf?key=Z03PvGU0Z5A3kFWNFgQJog

The Minimal style is best suited for visitors on mobile devices, where screen real estate is at a premium. Note that if you have selected the DuotoneFull Color, or White styles, there is an optional checkbox to show minimal style to mobile visitors.  This setting is recommended, and will replace the configured setting with the minimal style when a visitor is on a mobile device.

Graphic

In all styles (except minimal), you will be able to select the graphic that appears above the text of your greeting. There are four options:

AD_4nXcEyXUXgqiYegKbrQ2asFo_0_T_ZSs1_cBVirZ0sBiV5C5in8RqL-c1pf8_G0pFH68aHJ5Ts4nvSHGsj6WP98OFI_wIK_gajY2zYpZEQOyl681zYh0NpwA8Ai-m5dYqLHHuSTq-jQ?key=Z03PvGU0Z5A3kFWNFgQJog

  • Faces: Shows three profile pictures of Qualified users. Will prioritize reps who are online. A green dot will appear next to the faces if at least one rep is available for live chat.
  • Logo: Shows a company logo. By default, this will show the logo set in messenger themes, but a different logo may be uploaded.
  • Image: Upload an image that will display at the top of the greeting. Choose whether the image is bounded by the background color of the greeting, or spans the full width of the greeting. Note that this option is not available with the Duotone greeting style.
  • None: No image is shown; the greeting is text-only.

GIFs are not supported in custom greetings at this time.

Title (optional)

A bolded message that greets your visitors.

Body

The main message that greets your visitors. Use this to provide a value proposition, welcome visitors, or promote content.

Buttons

Configure the text of the buttons that visitors can select in your greeting. At least one button must be included. These buttons will be used in branching logic further into your experience if more than one is set.

Qualified Markdown is not supported within custom greetings.

 

Messenger actions

These actions allow you to communicate with your visitors via the Qualified Messenger, either as a first message or after the conversation has started.

Send a message

Send a message in the chat window to your visitor, without requiring any input or response from them. This can be used to break up conversation flow, prepare the visitor for a question, or communicate an important piece of information.

Ask a question

Ask your visitors a question to determine how they should proceed through the experience.

Questions to visitors fall into two categories:

Custom question (picklist)

Define a question for your visitors and populate picklist options that will allow them to respond.

Visitor fields

Ask your visitor to fill in one of your predefined Qualified visitor fields. The format of the visitor’s response will be determined by the visitor field type.

When asking the visitor to fill in a visitor field, you can indicate if you’d like the question to be skipped if previously populated. This will ensure that you do not ask visitors unnecessary questions, either because they’ve answered them during a previous interaction or because they’ve been populated via integrations like Salesforce, Marketing Automation, or Clearbit.

Custom Question answers are not stored and can only be used to branch within the current experience. To record a visitor’s response/and or push it to an external system, it must be captured via a Visitor Field.

 

Offer a meeting

AD_4nXcoKDxgPzyflaPIRS9fJoQe2m9SqxY2Rg3bKRv52PW5eCmdaCW9YYF_2arlL-3wnZnFW2OJWUu9LB12rse0tWSTp1tOjHl8uG3Uw3MkWxr8wGBghbMsYnWnCygNCn-VjWAzQ88ijA?key=Z03PvGU0Z5A3kFWNFgQJog

Allow your visitor to book a meeting within the messenger window.  When this action is selected, three steps are created by default:

Route for a meeting

This node will determine the meeting type that is offered, and thus the routing rules that will be used to determine which calendar(s) are shown.

If you need to route to a different set of users or a specific user within your experience, select I know who I want to route to and configure custom routing for this particular meeting offer.

Offer a meeting

This node shows a preview of the meeting booker. Use this to edit your meeting title, and determine whether you’d like to block or allow personal email addresses.

Confirmation message

After a visitor books a meeting, a message is created to thank the visitor for booking the meeting. This text can be edited or the confirmation message can be removed if desired.

Confirmation message default text

Your meeting is confirmed and an invite has been sent to your inbox.

We look forward to speaking with you!

Start AI SDR 

Hand off the conversation to an AI SDR agent.  There are a few settings that will determine how the AI SDR agent takes over the conversation.

Because the Start AI SDR action hands the conversation to an AI SDR agent, it will always end the experience. No actions can be added after the Start AI SDR action.

Profile

Determines which AI SDR agent profile is used for the conversation. For more information on AI SDR agent profiles, see here.

Appearance

Select whether to use the new messenger styling configured in themes.

Greeting

If the messenger has not been previously opened by any other experience step, you can choose to have the AI SDR agent proactively greet the visitor. 

If the AI SDR agent is not set to proactively greet the visitor, either by option or because other messages had been sent in the messenger previously, the AI SDR agent will wait for the visitor to type a message to respond to. You may want to use the send a message action to prompt your visitors to start the conversation in this case.

If you have configured promoted content, select the “Personalize with relevant offers” checkbox to allow the AI SDR agent to offer this content to visitors as part of an initial greeting.

Conversation

If you have configured promoted content, select the “Personalize conversation with offers” checkbox to allow the AI SDR agent to offer this content to visitors as part of an ongoing conversation.

Goals

Configure which goals are active for this AI SDR agent conversation.  By default, all goals are active.

In addition to setting whether a goal is active, this setting allows you to create buttons with custom text that will trigger the AI SDR agent’s goals automatically.

As a best practice, set buttons for a maximum of two of your goals.

Start Multi-modal AI SDR

If you do not see the option to configure Multi-modal AI SDR agents, contact your Qualified Success Architect. Not all modalities are supported on all Qualified plans.

As above, but opens a conversation with a multi-modal AI SDR agent, including text, voice and video conversations.