Get Started
Guides
Assets
Integrations
Gateways
Configuring an Aissistant for your work is a straightforward process that can be completed in as little as ten minutes.
To begin, create an account here. By clicking "sign up," you can easily provide your name, email address, and password to generate your account. Following email verification, you should be able to access your account by logging in.
Upon your initial login to your account, it is necessary to initiate a project for your business. Simply complete the required fields, including a project name, your business name, optional business description and contact email to establish your project.
A workspace is encapsulation of an Aissistant, including definition, assets, instructions, smart taggers, smart actions and associated gateways (agent platforms).
For instance, in the case of an e-commerce business with multiple e-stores, you can establish a distinct workspace for each store. Similarly, if your company comprises various departments, you have the option to create a dedicated workspace for each department.
To create a workspace, simply click on "CREATE NEW" in the workspace dropdown menu and proceed with the following steps.
After creating the workspace, you can link it to your agent platform via gateways. To do this, select "Gateways" from the left-hand panel and then choose "ADD GATEWAY". For more comprehensive information about gateways, please refer here.
Currently, the platforms supported are FrontApp, Gorgias, Intercom, Zendesk, and Hubspot, with plans to incorporate Chatwoot, Kustomer, Edesk, and Salesforce shortly.
Once the gateways are set up, you have the option to integrate smart actions with your information system, provided it has a publicly accessible API.
For those with a Shopify store, you can follow this Shopify integration guide to link your store and incorporate actions to retrieve customer data or details of an order.
Moreover, if your information system has an available API, such as an API gateway leading to your internal database, Aissistant can connect to this API to gather relevant information in response to user inquiries.
You can read this Smart Action document for detailed steps.
After completing the setup, you are encouraged to test Aissistant's functionality. Utilize our simulator to assess its response to both hypothetical and actual user queries. Additionally, we offer an assets debugger to facilitate the search for pertinent data within assets, along with a smart action debugger that allows you to evaluate the execution and results of the actions.
Now, it's time to launch our Aissistant in auto-draft mode (not the auto-pilot). You can monitor the responses generated by Aissistant either through the Sessions page in Aissist or directly on your agent platform.
Should you encounter any incorrect responses from Aissistant, there are a few possible explanations. If Aissistant is unable to provide an answer due to insufficient information, you'll need to incorporate the missing details into the assets, enabling Aissistant to access the necessary information for the query. In cases where Aissistant delivers inaccurate or inconsistent answers, this might stem from conflicting data within the assets. In such instances, you should employ the asset debugger to pinpoint and resolve these discrepancies. If Aissistant's performance doesn't meet your expectations, you have the option to refine its behavior using instructions and smart tags.
For more detailed information, please refer to Achieve Full Automation.
While we strive for full automation, there are instances where Aissistant may not be able to address every customer query. This could be due to the complexity of the queries, limited access to your internal systems, or the preference to have certain sensitive tasks, like refunds, handled by human agents. In these situations, smart tags can be used to seamlessly transition tasks from Aissistant to your human team.
Our system includes predefined tags such as sys_human_help and sys_human_follow_up for immediate notifications, but you also have the flexibility to create custom tags tailored to your specific requirements. The sys_human_help tag is used when Aissistant lacks the information needed to respond to a query, while sys_human_follow_up is employed when Aissistant recognizes a user's request but cannot execute the related task, necessitating human intervention.
Please refer to Human Team Followup for more details.