¶ Enable integration with your Front
¶ Create gateway in aissist.io
Creating an Aissistant working with Front can not be simpler!
Gateway can also be created with project with the similar steps as below, please refer to start for more details.
- In console.aissist.io, click "Gateway" tab in the left menu bar, then click on "Create Gateway" in the middle panel;
- Choose type "FrontApp", and give a name, make sure there is deployed workspace, then click "Next";
- Click on "Login", provide your credential of FrontApp. After successfully log in, then click "Next";
- (Required) Choose the "Inbox" that Aissistant will manage;
- (Required) Choose the "Self" which is a teammate in Front that Aissistant will behave as;
- Review and click "Create" to create the gateway;
After the gateway is created, you should turn on the created gateway. By default, it is "off". After that, you should be able to have Aissistant responding or creating draft for the incoming messages.
¶ Select the appropriate mode
Aissistant supports two modes for FrontApp integrations:
- Augmented: the Aissistant creates draft in Front for human team to confirm and modify before sending out.
- Automated: the Aissistant respond directly to the user inquiries via Front.
We recommend to start with "create draft" and get familiar with what Aissistant can do and can not do.
¶ Use the Front comment to provide extra context to Aissistant
You can provide extra context to the Aissistant by adding comment manually, by rules or by other integrations. The more the better. The comments is in pure language description. Usable comments include the order information, characteristics of customer, products used, bills, etc.
¶ Having trouble receiving response from Aissistant?
Please check the following, probability from highest to lowest
¶ 1. Check whether Gateway is turned on
Make sure the created gateway is enabled. By default, the newly created gateway is NOT turned on.
¶ 2. Make sure Aissistant manages the right inboxes
Aissistant ONLY works on selected inboxes. To set the inboxes, click on the "gateway" to config, and in the following tab, select the Inboxes (you can choose multiple). This config is per gateway, meaning you can create different gateway (associate with different workspac) for different set of inboxes. However, Don't overlap.
¶ 3. Make sure "self" is selected
For Aissistant to work, you need to select a "SELF" which is a teammate in FrontApp for Aissistant to behave as. Only single choice is allowed. This "SELF" can be any teammate but normally is some account specially created for Aissistant.
¶ 4. Make sure that gateway has deployed workspace
The gateway needs to have associated workspace. Normally, the workspace is set while creating gateway. However, there is a chance that workspace might be missed during other steps.
¶ Make Aissistant work better with FrontApp
¶ Hint 1: Add customized tags
When you configure the gateway, you can add other tags. When you define the model (in knowledge base and graph model), you can instructe Aisstant to mark tag in certain scenarion. As above, you can create rule to react to those tags when they happen.
¶ Hint 2: Add rules
Aissistant uses tags to mark status and notify other teams. There are two system tags "A(not_understand)", "A(status:suspended)" that specifically need human attention on. You can create rules on those tags - when they happen, move them to other inbox or assign to other team.
¶ Hint 3: Update and refresh the content
Aissistant leverage the provided contents. Two source of content are commonly used: web sites and Google Doc. To get the best outcome, those source of content needs to be periodically updated and refreshed. Please be noted that the update on websites normally takes days to take into effect, while the update in Google Doc is instant.
¶ Hint 4: Fine-tune the prompt
Please refe to https://doc.aissist.io/en/adjust_behavior on how to modify and fine-tune the behavior of Aissistant.
¶ Hint 5: Periodically check the Aissistant inbox to pick up unprocessed conversations
There are several scenarios that Aissistant will leave the work unprocessed:
- Aissistant could not find proper response for user's inquiry. In some scenario, it make respond to ask user to clarify the question.
- The conversation has been marked "suspended", in that case, the engine no longer processes the thread.
- Someone else other than Aissistant has been assigned to the conversation, in that case, the Aissistant considers it "bulge-in" and won't respond to it. Assigning it back to Aissistant won't trigger Aissistant to process the previous message, but it will react on the next as long as the conversation is not "suspended".