AI Agents - Execute Automations

Using the AI agent to execute automations intelligently.

Enabling the skill and creating an automation

To use AI automations, you must enable it and create a new one on the automations overview screen. Once enabled, the 'Agent Conditions' will be checked on every message from the lead.

Skill Execute Automations.

Automations screen.

Configuring - Initial Data

The initial data entered will be visible on the automations screen and are essential for the process to function. Both the 'Name' field and the 'Automation Description' — especially the latter — should clearly indicate the automation's purpose so the agent understands exactly what will be executed.

Initial Data.

Configuring - Conditions and Actions

1. Agent Condition: Checks when the lead sends a message that matches the defined condition, considering both the context of the current conversation and the lead fields accessible by the A.I. If the check is considered true, it will proceed to 'Automation Conditions', if any exist.

2. Automation Conditions: These are additional checks. If the combination of conditions is true, the actions will be executed.

3. Automation Actions: The actions within Sprinthub that will be executed.

In this example, it will be checked whether the lead showed interest in joining the Offers Club of a bookstore. If they express interest and have a registered email, an opportunity will be created for them in the 'Offers Club' funnel.

Conditions and Actions.

Configuring - Action Repetition

For this automation, the option 'Only a single trigger per conversation?' was enabled, ensuring the action is not repeated during the same service. The option 'Check conditions until they are met?' ensures that, even if the lead does not meet the 'Automation Conditions' on the first attempt, the A.I. can perform new checks as soon as they again pass the 'Agent Conditions'.

Action Repetitions.

Adapting the training and rules for the automation

It is important that the A.I. agent is aware that the company operates an Offers Club system, so it correctly understands the automation and can inform the lead whether this club exists or not.

It is also recommended, in the additional rules, to configure a notice to the lead informing them that they have been registered, if they request enrollment. This way, besides the automation creating the opportunity, we ensure the lead was properly notified about their registration.

Contextualization.

Testing the automation

Finally, during the conversation with the lead, the agent mentioned the possibility of enrollment. When the lead showed interest, they received a confirmation message. The execution of the 'Create Opportunity' action can be verified in the history.

Service with the lead.

Lead history.