Skip to main content

Creating a great first impression: Onboarding messages (working with the onboarding.gdoc file)

When a new user first starts a conversation with your AI Expert, it's crucial to welcome them , orient them, and set the right expectations. To do this, you can find the onboarding.gdoc configuration file in the root of your linked Google Drive folder.

This file typically contains two main sections where you define your message texts. It's very important to maintain the exact syntax and formatting (JSON structure) as specified in the pre-populated sample filewhen editing it . Any syntax error (e.g. missing quote, comma, bracket) may cause onboarding messages to not display correctly or at all.

13.1 First_messages section (Welcome messages for the very first contact)​

Here you define one or more variations of welcome messages. If you specify more than one, BuddyPro will use them as inspiration for each new first contact, and create a message in that style personalized for that user. This can make the first impression more interesting and less robotic.

What should a good welcome message include?

  • A warm and personal welcome: address the user by name if technically possible and appropriate (the platform can access the Telegram name if the user explicitly discloses it, but this is not standard behavior for a bot's first message). Rather, opt for a generic but warm greeting.
  • Briefly introduce your AI Expert: Briefly say who they are (what their name is) and what they can primarily help with. Emphasize his or her uniqueness (e.g., "I am your personal AI Coach for achieving financial independence, trained in the methods of expert Jan Novak.").
  • Set basic expectations (very important!): Briefly outline what the AI can do, but also what it can't do. You can mention that it is AI and can learn. This is a great place for a short, friendly disclaimer (e.g., "Remember, I am AI, and while I try to be as helpful as possible, I am not infallible. For major life decisions, always consult human experts as well.").
  • Clear Call to Action: suggest to the user how they can start the conversation. For example:
    • "Tell me, what is your biggest concern today in the area of [your topic]?"
    • "What is the first thing you want to ask me about [your topic]?"
    • "How can I help you today on your journey to [goal state you are helping with]?"
    • "To best help you, please tell me briefly about yourself and what you would like to accomplish."
  • 💡 Advanced Onboarding Tip - Link to introductory video:
    • It is very effective to create a short (e.g. 2-5 minute) introduction video where you personally (or a friendly announcer) introduce your AI Expert, show how to interact with them, what to ask, and what their main benefits are. You can also reiterate key disclaimers and emphasize that AI is a partner, but the final decision is up to the user.
    • Upload this video to YouTube (it can also be "unlisted" - non-public, only available through a link) and embed the link directly into the text of your first_messages. Telegram will automatically display this link as an interactive preview of the video directly in the chat, which can greatly improve the user's first impression and engagement. - Telegram will automatically display this link as a video preview directly in the chat, which can significantly improve the first impression and capture the user’s attention. After clicking, the user will be redirected to the link. The video cannot be played directly inside Telegram.

13.2 Onboarding_messages section (Automatic messages during the conversation)​

This section allows you to set up automatic messages that your AI Expert sends to the user after they reach a certain number of messages exchanged in their conversation together (both messages from the user and replies from the AI count).

What is it for?

  • To gradually introduce other features of your AI (e.g. "Did you know you can send me voice messages too? It's often faster and more convenient.").
  • To keep the user engaged and motivated (e.g. "We've already exchanged 20 messages, great job on your topic! I'm still here for you, keep asking.").
  • To offer additional help or relevant resources (e.g., "If you'd like to discuss [specific topic related to the current conversation] in more depth, my creator has a great article for that here: [URL]").

How to set this up?

  • In the configuration you define:

    • uniqueId – an identifier that must be unique
    • atMessageNumber – the “milestone” at which the message should be sent (e.g., "atMessageNumber": 10)
    • orderForBuddy – instructions for Buddy so Buddy knows what to say to the user (e.g., "orderForBuddy": "Tell the user...")
    • type – determines whether the message format should be text, audio, or both text and audio (e.g., "type": "text", "type": "audio", "type": "text-audio"). This parameter is optional; the default value is "text".

  • Example:

    {
      "uniqueId": "VOICE",
      "atMessageNumber": 10,
      "orderForBuddy": "Tell user that he can also send you voice messages...",
      "type": "text-audio"
    }

  • Example from the default Buddy.fm settings (customize or remove if not relevant for your AI Expert!):

    • After the 10th message: AI can inform the user that it can handle voice messages.
    • After the 30th message: The AI may mention the reminder feature (e.g. "I can remind you of our next session or task, just say so.").
    • After the 60th message: AI can report on the ability to search the Internet.

  • Recommendation:

    • Don't overdo it with the number of these automated messages. Too many can be distracting or annoying. Usually 2-3 well-timed and genuinely relevant and useful messages within the first few dozen interactions are enough. Less is sometimes more.
    • Make sure these messages are useful to the user and actually help them better use your AI Expert or motivate them, not just generic or salesy platitudes.

  • Again, make sure to use precise syntax (JSON) when editing! Any mistake can cause messages to not send or display incorrectly.

13.3 Activating changes in the onboarding.gdocfile​

After any editing of the contents of the onboarding.gdoc file on your Google Drive (and saving it), it is essential that you enter and send a command in the chat with your BuddyPro instance (in Telegram):

/update

This will instruct the AI to retrieve the new version of the onboarding settings. Without this step, your changes will not take effect for new users. The /update command is generally used to sync changes from Google Drive to your BuddyPro instance.

13.4 Voice Responses and Custom Voice Clone as Part of the First Impression​

A great first impression doesn’t have to rely on text alone. Buddy can also respond using voice messages – including a custom voice clone. This allows your AI Expert to speak in a voice that is fully aligned with your personal brand, communication style, or even your own real voice.

Voice responses feel significantly more human, personal, and trustworthy than text alone. For new users, this often creates a strong “wow effect” that immediately reinforces the feeling that they are interacting with a real expert, not an anonymous AI.

Why use a voice clone already during onboarding:

  • creates a strong emotional first impression
  • increases trust and authenticity of the AI Expert
  • helps you stand out from standard chatbots
  • supports a sense of personal connection from the very first message

A typical and highly effective use case is an introductory voice onboarding message, where Buddy introduces itself, explains how it can help, and naturally guides the user toward their first interaction.

Use the command /createVoiceClone.

Frequently Asked Questions (FAQ) about this step:​

Can I use Czech or Slovak characters in onboarding messages? The only important thing is to follow the correct syntax of the file structure (JSON).

What happens if I make a mistake in the JSON syntax in onboarding.gdoc? If the file does not have a valid syntax, BuddyPro will probably not be able to read and process it correctly. This can lead to the onboarding messages (or part of them) not being displayed, or an error message when trying to /update. In this case, you must repair the file and re-run /update. If you are unsure, use ChatGPT or another AI to check the JSON syntax.

How many variants of first_messages are optimal? There is no strict limit, but 2-3 well-written variants for different user groups or for variety are usually sufficient. Too many variants can be maintenance intensive.

Can an onboarding video be on a platform other than YouTube? YouTube is primarily supported because Telegram displays its thumbnails well. For other platforms, check how Telegram displays links. The most important thing is that the link is publicly accessible.

How often should I run /update after editing onboarding.gdoc? Always immediately after completing and saving changes to Google Drive. Otherwise, the changes will not take effect.

Should onboarding.gdoc also include disclaimers, or do they belong only in system_prompt.gdoc? It's a good idea to mention key disclaimers (especially those related to AI limits, not replacing expert advice, etc.) both in system_prompt.gdoc (which affects AI behavior) and in a brief and friendly way in onboarding messages, so that users are aware of them right from the start. Repeating important information doesn't hurt, as long as it's presented in an appropriate way.

Is the way onboarding messages are set up different from system_prompt.gdoc? Yes. System_prompt.gdoc defines the personality and behavior of the AI in general. Onboarding.gdoc defines the specific message texts that will be displayed to the user at certain stages of their first interaction. Both files are important, but serve different purposes. After editing both, the /update command is called.

Last updated on