Greetings are your AI Agentβs first impression. They introduce the Agent, set expectations for the conversation, and reflect your brandβs tone. Think of the greeting as the handshake that starts every interaction and guides end users toward what the Agent can do.
A good greeting is clear so end users immediately know who theyβre interacting with. It stays focused by outlining exactly what the Agent can do. The tone and style should be on-brand, matching your organizationβs personality. And finally, the message must be concise, keeping the conversation moving without overwhelming the end user.
Strong greetings are written in a natural, conversational tone. They avoid jargon and overly formal language, and instead use simple sentences that sound like real speech. A well-written greeting feels approachable and invites end users to engage right away.
Many end users are used to simple search or keyword-based chatbots. Itβs important to set expectations upfront: Ada works best when people write in full sentences or longer messages. A greeting that encourages this kind of input helps guide end users toward more effective interactions.
Outcome: The greeting feels human, brand-consistent, and easy for end users to act on while encouraging them to use full sentences for better results.
Many enterprise customers use greetings to include compliance-related information. This can help set clear expectations by letting end users know they are interacting with an AI Agent and by linking to relevant company policies (such as privacy, data use, or terms of service).
Guidelines:
To add compliance messaging to your Greeting:
Work with Legal/Compliance
Before publishing a greeting that includes compliance messaging or policy links, confirm with your Legal or Compliance team that the content is accurate and up to date. This helps reduce risk and ensures your end users receive the right information.
Ada offers multiple ways to add personalization data to your AI Agent. Personalization helps end users feel recognized, while variations prevent conversations from starting the same way every time. Together, these techniques create greetings that feel more engaging and less repetitive.
When setting this up, add a fallback value so the greeting still works if the end userβs name isnβt available. For example:
Outcome: End users feel recognized when data is available, and the fallback ensures the greeting remains smooth and natural when it isnβt.
Using fallback values
When you personalize greetings with end userβs data, always include a fallback value in case the information isnβt available. This prevents awkward gaps or broken messages and ensures every end user receives a polished, natural greeting.
Outcome: Repeat visitors experience fresh, dynamic greetings.
Greetings can also be updated to share time-sensitive information such as limited-time promotions, special announcements, or recurring events. Adjusting your greeting for these occasions ensures end users see relevant updates immediately, without needing to search elsewhere.
Here are the ways you can implement your Text block within a Greeting together with a Scheduled block:
To set up a scheduled Greeting:
Outcome: End users see a promotional greeting during the defined schedule (Tuesdays, 3β6 PM), and a clear alternate greeting at all other times.
Managing scheduled greetings
Use Scheduled blocks to control when different greetings display. You can configure days of the week, times of day, or make exceptions for specific dates. This ensures end users always see a message that matches your availability or promotions.
Not every end user is the same, and greetings should adapt accordingly. Use the Conditional block to implement contextual greetings. The Conditional block allows you to define one or more conditions (for example, user type, region, or language). If none of those conditions are met, the Agent will fall back to the default greeting youβve configured.
To set up a contextual Greeting for new vs. returning end users:
is_returning_user) or use another user attribute passed from your system.Outcome: New end users feel guided, while returning end users get a warm welcome.
To set up a region-based Greeting:
Outcome: End users see localized information that matches their context, while others see your default greeting.
Not all greetings behave the same way across channels.
Greetings are not set and forget! They need to be reviewed and refreshed regularly. Always preview greetings with and without personalization, test conditional logic to ensure the right greeting is shown, and confirm the tone matches your brand. Update greetings ahead of seasonal events or promotions, and remove outdated content so end users never see irrelevant information.
The following table summarizes the main scenarios and best practices for configuring greetings, along with the features that support them.