Salesbot Explanation: “ByteGPT+ Template”

1. This is a Template: In other words, it is not a ready-made flow for your business. As it is a template, you can change and customize it according to your business and needs.

2. Duplicate your template (salesbot): Preserve the original template and leave it to be the replicator for new salesbots that you need. 

3. Functional test of the ByteGPT: If your salesbot is not operating correctly, run a test run using the original salesbot template. ByteGPT first. This will help check if the problem is in the ByteGPT or in some specific configuration of your salesbot.

4. There are two Webhooks: One for ChatGPT (internal actions) and one for GPT Assistant (responses to customers).

5. Intent Analysis: We left options in step 184, so that ChatGPT can identify the intent of the message. Add or change depending on your business. You can also use this step for actions other than intent. Intent was just one example. You can also remove this action (see below in the “About ChatGPT and Assistant in Salesbot” section).

6. Intent Check: Intentions are checked and redirected as necessary, in step 201. We have provided an example, but you must provide your options, depending on your business.

7. Flow Diversion: The flow can be adjusted based on the identified intent (step 201).

8. Update fields in reinstallations: New fields are added with each reinstallation. The most recent fields are always the current ones, so make sure you always use the latest template available. In the widget, there is a list of active fields.

9. Specific prompts: you can adapt your prompts, throughout the salesbot, according to your needs.

10. The solution depends on you: Remember, the ByteGPT is a connector that connects AI Assistants, ChatGPT etc to your Kommo. It's a tool. Therefore, success will depend on building your flow, structuring the solution for your business.

First of all, it is important to know that the salesbot “ByteGPT+ Template” comes with two webhooks, related to Artificial Intelligence, one for the Chat GPT (GPT-4o) and another for your Assistant (with your company data and model defined by you), connected to this salesbot or template. 

Let's understand the role of each one in the salesbot:

Chat GPT

• The ChatGPT Webhook is at Step 187.
• ChatGPT in salesbot is used for internal actions and functions, such as identifying intentions of messages received from users, analyzing, validating, extracting data and whatever else you want to do.
• Does not send messages to customers (unless you change this).
• You can use the ChatGPT result to infer conditions, change flow routes, define values ​​in CRM fields, etc.
• It is unrelated to your GPT Assistant, so it is not impacted by the Assistant's instructions or files.
• It reacts to the internal prompt, in the salesbot, from step 184, or from other steps that you define.
• The default model is GPT-4o. See how to change here.
• If you do not want to use or do not need this ChatGPT in your flow and want to keep just the assistant, connect step 219 (Pause step) directly to step 210 (with the “ByteGPT+ | Prompt”).
  • If you want to delete the ChatGPT steps, you can delete the steps: 184, 187, 189, 191, 204, 201, and 171.

Assistant

• The GPT Wizard Webhook is at Step 50.
• The Assistant in the salesbot is used for personalized service and sending responses to the customer.
• It is responsible for generating messages via GPT and sending them to the client.
• It is directly related to your GPT Assistant (such as Assistants from Open AI, Dify, Chatbase, etc.) and is impacted by the instructions or files in this Assistant. It has no relation to the native resource of Kommo AI (suggested answers), as they are different resources and independent of each other).
• It can also react to internal prompts, in the salesbot, if you define or edit it in step 210, being able to increase the message received or make other adaptations. However, it is worth noting that it is not directly related to the prompt in step 184 (related to ChatGPT).
• The GPT model used is defined directly in your Assistant, externally (like in OpenAI, the Assistants area, for example)
• If you do not want to use or do not need this Assistant in your flow and want to keep only ChatGPT (for internal actions or responses given by it), you could exclude the steps: 210, 50, 59, 209, 212, 213, 80, 51 (if you want ChatGPT to respond to something, you may need this), 228, 224, 215, 216, 226, 218, 217.

With these two webooks in use, 2 requests to the API are consumed ByteGPT. Each time a webhook is triggered, 1 request is counted.

To directly activate the ByteGPT When starting a conversation from the lead card, follow these steps:

1. Access your salesbot flow on Kommo.
2. Connect “Start Robot” directly to step 144, which sets the “Message received” field to “customer message”.
3. In your account Kommo, in the table with the Salesbots list (Settings > Communication tools), select the conversation trigger “When conversations are started by an incoming message on any channel”.

For visual guidance, watch the video at minute 28:00 via this link:

Here is an example of the process:

• Clone the template ByteGPT to preserve the original.
• Make your customizations in the copy.

See explanation of the Template ByteGPT in detail, with each step.

If you need further assistance or want to schedule a meeting, activate the chat at the bottom and to the right or schedule a call via link to schedule.

Overview

1. User Message Reception:
– When a message is received from the user, it is recorded in the “Customer Message” field (ByteGPT+ | Message received), in step 144.

2. Defining the Intent Prompt:
– The received message is inserted into a pre-defined prompt in the step 184. This prompt is used for intent analysis, seeking to identify whether the message is related to attendant, meeting, greeting or general.

3. Submission to ChatGPT Webhook:
- Na step 187, the intent prompt is sent to the ChatGPT webhook.
– The system enters a 5-second loop to wait for ChatGPT’s response, in which case step 189. It is important to maintain at least 5 seconds.

4. Intent Check:
– When the response is received, it is checked in the step 201 (Intent Conditions), to see if it matches any of the defined intents (attendant, meeting, greeting, general), referring to step 184 of the intent prompt.
– If an intent condition is satisfied, the flow continues as defined for that specific intent.

5. Flow Diversion:
– If one of the conditions is met (Yes), and if the intention is, for example, “#Attendant”, the flow will be diverted to other specific steps where various actions can be performed, including opening response options or even stopping the flow.

• It is possible and recommended to edit the intent prompt to include more options.

6. Assistant Response:
– If none of the intent conditions are met, the flow proceeds to the step 50, where the assistant webhook processes the response.
- Na step 51 (GPT Response), the assistant responds to the user using a generative response based on GPT artificial intelligence.

7. Interaction Cycle:
– After responding, the system returns to step 9, waiting for a new user interaction, creating a continuous cycle of “question, analyze, answer”.

Yes the ByteGPT can interpret images and pass a specific prompt to your salesbot.

You can create a condition after step 201 (which in our case is 233) and add a condition to the field ByteGPT+ | LOG.

If it contains #image, you can pass a specific prompt in the next step (235, in our flow), asking you to analyze the image, passing a specific prompt or requesting whatever is necessary.

In this example, the prompt (ByteGPT+ | Prompt) in step 235 has just one period (.), as an example.