Get Started

Introduction

Quickstart

Guides

Workspace Config

Smart Tagger

Smart Action

Gateway

Achieve Full Automation

Human Team Followup

Assets

Website

Google Doc

Google Sheet

Integrations

Shopify

WooCommerce

Gateways

FrontApp

Gorgias

Intercom

Google Doc

Aissistant supports Google Doc and Google Sheet as assets

<aside> 💡 A lot of Aissistant users use Google Doc as Knowledge Base

</aside>

Click “Assets” from the left sight panel of your Aissist dashboard, you can then build your knowledge base with Google Doc.

Additionally, we offer an assets debugger on the same page. Here, you can enter keywords or questions, and the debugger will generate a list of relevant information along with its sources. This allows you to confirm the accuracy of the information retrieved. It also enables you to identify and resolve any discrepancies or conflicts within the returned data.

Set the permission

The doc provided to Aissistant needs to meet one of following requirements:

a) It is shared with [email protected]

b) It is set to be “accessible to anyone with the link”

Why Google Doc?

There are multiple reasons that we recommend using Google Doc as a primary asset:

1. It’s free and widely used;
2. It is function complete as a knowledge base;
3. It is easier to manage (search, edit, index, etc);
4. It is easy for team collaboration;

What is difference between Google Doc and Workspace Instruction?

Although the information in both places can play the same effect, they are significantly different.

• Workspace Instruction: the content in workspace instruction is global which applies to all the interactions. This is where you put something globally important, for example “be brief on the response”, “never confirm the schedule time”, etc. However, workspace instruction is supposed to be short and brief, usually within 4K English characters (~ 1K English words). Otherwise, it won’t be very efficient to carry a big chunk of instruction on every interaction.
• Google Doc: the content in Google Doc is not global therefore not guaranteed to be included in every interaction. This is where you put something that is contextually important, for example “the move-out procedure is …”, “our return policy is …”. It can be very long. However, it is very important to section the Google Doc by headings, because AI leverages the headings to intelligently select the relevant information to be included based on the context that conversation is in.

Another difference is that Workspace Instruction is meant to be more static, while Google Doc can be the place for dynamic content that has frequent updates.

<aside> 💡 You can included multiple Google Docs in one workspace.

</aside>

Format

We try to little restrictions on format, except the following two recommendations:

<aside> 💡 It is very important to use the HEADINGS to separate the topics in Google Doc. The heading can be a short description of topic or several example questions divided by ‘|’. Heading is an important manner to help AI segment your doc and intelligently select the relevant section to use.

</aside>

• Use the heading to separate the content, to help Aissistant better understand it. We usually recommend one section is no longer than 1 page.
• We don’t support image understanding in Google Doc yet.

Example Google Doc

Recommendations

<aside> 💡 It is very important to segment the Google Doc with HEADINGs.

</aside>

1. Use heading to separate the content. It is hierarchy to have nested heading. Simply have some heading to semantically separate the sections will help.
2. Use “normal text” as the format of content which can be “paragraph”, “list” or even “table”

Advanced Features (Optional)

1. Emphasize

Use [[ and ]] to enclose the text to instruct Aissistant to follow the provided content as much as possible in the response.

1. Contextual instruction

Use {{ and }} to enclose an instruction on how to handle this specific situation.

<aside> 🔔 Be specific on the instruction, for example, include when, what, how and why.

</aside>

Other supported assets?

The following assets are also supported, please contact [email protected] for assets that are not in the list.