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

Workspace config

Configuring instruction and context is the simplest way to tune the Aissistant’s behavior.

Screenshot 2024-01-25 at 2.16.06 PM.png

Instructions

Instructions can be used to tailor Aissistant to better meet your needs. Usually instructions have two categories:

Generic: generic instructions work for any scenario. An example of generic instruction is “be precise on your response”, “keep your response to the limit of 75 words”, “include url in the response”, etc.

Scenario: scenario-based instructions usually has a condition. An example is “if user asks for meeting, send them the link …”, “if user ask for human, tell them …”.

<aside> 💡 Tip: Contrary to the asset-based content, instructions are global and affect every interaction with the AI. As such, instructions should be concise and succinct, typically not exceeding 1000 English words, to optimize Aissistant's efficiency.

</aside>

<aside> 💡 Tip: when giving instructions, it is useful to include reasons which helps Aissistant better understand and follow the instructions. For example, instead of say “limit the response to 75 words”, say “limit the response to 75 words because people don’t like long response in SMS.”.

</aside>

Contexts

You can provide additional information that you’d like Aissistant to know in the Contexts. Some useful information like “the support email is support@…”, “the sales email is sales@…”, “the office address is …”, etc.

Name, Identity and Purpose

Business name: the name and brief description of your business. This information will be used to answer relevant question and provide context to fine-tune the behavior.

Identity: the identity for Aissistant. It can be something like consultant, realtor agent, customer service agent, sales agent, etc.

Purpose: the overall goal for Aissistant. Some common ones are “answer user’s questions”, “measure user’s interest”, etc.

Style

The language description on the tone. Multiple styles can be separated by “,”. Some commonly used styles are: professional, casual, persuasive, humorous, and charming etc.

Task (Optional)

The task to finish during the conversation. For example “ask user for their email”, “ask user for their availability”, etc.

It is usually used in a task-driven conversations like sales or targeted outbound reach-out.

Fallback

Should Aissistant be unable to address a user's question, it can generate tags such as sys_human_help or sys_human_follow_up. The Handover option allows you the flexibility to pause Aissistant's involvement in subsequent interactions and transfer the conversation to a human agent.

Additionally, you have the capability to activate a fallback mechanism after a specified number of interactions. This lets you design and implement a custom fallback strategy that aligns more closely with your specific requirements.

Screenshot 2024-01-25 at 4.49.41 PM.png