Many people will find teaching their AI agent to answer questions using content from their institutional website enough. This approach has the benefit of your website being the single source of truth, and any updates made or new pages published will continue to improve your agent without any action required from you.

However, the occasion may arise where you want more granular control over what your bot can see and how it replies. This can be done in one of two ways:

Knowledge bases - "If a student asks x, always reply with y."
External knowledge sources - "Sharing internal guides/resources safely with the bot without putting them on our website."

Getting started with knowledge bases

Think of Knowledge bases as your AI agent's specialized memory. Your bot will draw upon what it finds on your website for most answers. However, you may want the bot to deviate from this or provide a pre-written, stock answer.

That's where knowledge bases come in. They allow you to group items / owned answers containing pre-written replies, as well as the questions or phrases students might use that should to trigger them.

Knowledge bases and their items can be used by any number of unique AI agents/bots. They can be assigned to (or unassigned from) a bot by heading to Conversations > Chatbots > {your bot} > Knowledge bases.

Creating Knowledge bases

Head to Conversations > Knowledge bases and click + Create a knowledge base in the top-right corner.

Give your knowledge base a name, choose whether you'd like to assign your knowledge base to individual agents or teams, and what, if any, labels you'd like to use to describe this knowledge base. Assignments and labels can be used to filter knowledge bases and are a great way of better delineating ownership swim lanes.

Creating items

To add a new item to your knowledge base, head to Conversations > Knowledge bases > {your knowledge base} and click + Create item in the top-right corner.

Items are divided into four main sections:

Basic information

This section is all about good housekeeping. How will you internally name, assign, and tag your owned answer/item?

Name - The internal name of your item. This is never visible to students.
Assignments - Optional. Assign this answer to agents or teams for easy auditing.
Labels - Optional. Assign labels to describe the types of information your item provides.

Responses

This section is all about the type of response you'd like your bot to give. You can use multiple response types per item. Responses will be displayed in order, from top-to-bottom:

Message - A rich-text enabled text block. Type out the message you'd like your bot to use. Highlight any words/sections to apply rich text editing.
Display message buttons - Begin by picking a button style (list or pill) and click + Add item to add a new button to your list. Click your button to edit its label and choose what action should trigger if the button is clicked:
- Send to a webpage - The URL users should be redirected to when clicked.
- Invoke another item - Trigger another knowledge base item from any knowledge base.
- Prompt chatbot response - Provide a detailed, specific prompt/question for your generative AI bot to reply to. This prompt will not be printed in the conversation.
  Example: Imagine our item is to help triage users to find Scholarships. We use a 'Message' and 'Display Message Buttons' to invite students to tell us their level of study. We then discreetly prompt our AI bot to generate a cogent reply:
Embedded form - Select a pre-made Gecko form and invite your AI bot to capture responses. Any conditional logic, workflows, or integrations will fire as usual. You'll only be able to select from the forms your user has permission to view.
Conversational form - Prime your AI bot to capture/update contact fields on your account. Once added, click the [>] chevron to expand the field and configure how you'd like your AI agent to ask the question:

Trigger questions

This section is all about defining which questions or phrases should trigger your item. Begin by adding an initial question and then click Generate trigger questions to use AI to quickly generate additional variants of your question, or Manually add a trigger question. We recommend a minimum of 10 trigger questions and a maximum of 15.

Actions

When your item is triggered, in addition to your Responses being invoked, you can also immediately run any number of the following actions:

Assign conversation - To any selected agents or teams.
Add a label - Apply any pre-made labels to the convo.
Add a note to the contact - Add a note to the conversation for agents to view.
End conversation with bot - The convo will remain open, but the bot will be unassigned and will stop responding to future student messages.

After your item sections are configured, click Save and publish item to make your item immediately available to any bot using your knowledge base, or click Save as draft to save an unpublished copy of the item in your knowledge base.

Once created, your knowledge base items can be published or unpublished at any time from the Conversations > Knowledge bases > {your knowledge base} table. Click the breadcrumb [...] button to alternate between the two states. Published items can be used by any bot with access to the knowledge base whereas unpublished items will never be used.

External knowledge sources

Sharing documents with your agent

Sharing your treasure trove of internal documents, FAQs and guides with your AI agent can help make it better at answering questions. Happily, this process is quick and easy.

This quick guide covers the process for sharing .pdf, .docx, .xlsx, and .csv files.

Organize Your Documents

Gather all .pdf, .txt, .docx, .xlsx, and .csv files you'd like your AI agent to learn.
Make sure the files are up-to-date and contain relevant information.

Upload to Google Drive / Microsoft OneDrive

Log into your Google Drive / Microsoft OneDrive account.
Create a new folder for your AI bot documents (optional but recommended).
Upload your files to Google Drive / MS OneDrive.

Publish to the web

Open each document
Click File > Share > Publish to web
Choose "Entire Document" in the first dropdown.
Click "Publish" and copy the provided link.
For more information, check out this Google Support guide.

Doing so will provide a unique static URL per document, meaning any changes you make to the bot will be pulled through into your AI Agent when it next scrapes the document.

Finally, share your link with your Gecko account, who can point your bot at the URL as requested!

AI agent x Sharepoint integration

Should you want us to include Sharepoint content within your chatbot, then you will need to provide us with a way to authenticate. Currently the preferred method for that is to register an app for the Sharepoint site, and then provide us with a Client ID & Secret for us to use to authenticate.

We use the in-built Sharepoint API to access the sites content rather than traditional scraping techniques.

Step 1: Register an app

This is done within your Sharepoint tenant by visiting the following URL:

https://[your tenant].sharepoint.com/sites/[your site name]/_layouts/15/appregnew.aspx

For example during our test, this URL was:

https://geckolabs.sharepoint.com/sites/gecko-test/_layouts/15/appregnew.aspx

Once you are on this page, you'll be presented with the following screen:

Client Id: [Click Generate]
Client Secret: [Click Generate]
Title: Gecko
App Domain: localhost
Redirect URI: https://geckoengage.com

Make a note of both the Client Id, and Client Secret as you will need to provide those to Gecko to authenticate with.

Step 2: Give the app Sharepoint permissions

Now that we have an app, we need to provide the permissions to access sharepoint, this is done on a slightly different URL in the admin interface:

https://[your tenant]-admin.sharepoint.com/_layouts/15/appinv.aspx

During our test setup the URL was:

https://geckolabs-admin.sharepoint.com/_layouts/15/appinv.aspx

You will then be presented with the following screen:

Paste the "Client Id" from the previous step into the "App Id" field and then [click Lookup], this will retrieve the app and if it works it should automatically fill out the other fields for you and you will see the following:

In the last box, "Permissions Request XML" enter the following:

<AppPermissionRequests AllowAppOnlyPolicy="true"> <AppPermissionRequest Scope="http://sharepoint/content/tenant" Right="FullControl" /> </AppPermissionRequests>

Next click on [Create]

Step 3: Send credentials to Gecko

Once the above is completed, you will need to provide us with:

Client ID

Client Secret

Sharepoint Site URL

We can then conduct a test to ensure things are working as expected.

Any questions? Feel free to start a live chat with a member of our support team or explore the rest of our academy at your leisure.

Users and permissions