Skip to main content

Implementing your Assistant: a step-by-step guide

The simple steps involved in onboarding with Unibuddy Assistant

Amy Gray avatar
Written by Amy Gray
Updated over a week ago

Unibuddy Assistant is remarkably easy for you to implement - there is nothing to train or "turn on" - it works right out of the box. Once the snippet is embedded on your website, your Assistant will be turned on and live!

You will choose the source of the Assistant's knowledge base - your website starting point. This will be where your Assistant will start its search as it finds the right information to answer questions.

Unlike many other chatbots, there is no need to manually 'train' the Assistant, or feed it information. It uses the information from your website, and as the information on your website updates, the Assistant's knowledge base will be updated, too.

🏁 What should I use as my website starting point?

This depends what you would like to use the Assistant for! Most partner universities choose their home page URL, so the Assistant can read and refer to all of their web pages (you do have the option to exclude specific URLs - more on that later!)

If you are utilising the Assistant for a specific use case - international students only, as an example, then you might use your main international page as your search starting point.

⏭️ What happens next?

Your Customer Success Manager will send you a code snippet, which you can pass to your web team, to have them embed on any pages where you would like the Assistant to show. Alternatively, they can embed the code snippet in the β€˜HEAD’ of your website, so it will be displayed on every page.

πŸ§‘πŸΌβ€πŸ« If you do not have active staff ambassadors, go to your dashboard to add a Staff Point of Contact. This means that students who request to be referred to staff have a relevant email address, or person to reach out to.

Our recommendations for successful implementation are:

  • We would recommend removing any existing CTAs - whether Unibuddy popcards, or other CTAs - on pages where you will embed the Assistant. Too many calls to action can be confusing for your audience.

  • Consider customising your Assistant - perhaps adding custom responses, a preference for tone of voice, or any URLs you would like to exclude from the Assistant's knowledge base. More on that here.

  • Finally, reach out to your Customer Success Manager with the URLs of the pages where you have embedded the Assistant.

Did this answer your question?