# SAC 360º - Automations – Chatbot does not activate with WhatsApp call logs

In SAC 360º, we can configure automations so that the chatbot is triggered only in specific situations, preventing it from starting interactions on records that do not correspond to real customer interactions.

A practical example is when the system receives records of phone calls (call started, rejected, canceled, etc.) that end up entering the SAC as technical messages. In that case, we can create an automation that blocks the chatbot from being triggered whenever this type of record is identified.<br>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfYR-lEKcQKshf5odRfMJoQt06SJQ0LRdBbS1gsw-Bqxd8K1qFFg_OQxD9mCYO4t8ColS4D4SjjhlwSpJ9VqLP42DSCRFpV5boRgH43mQxFDfm2U78AEUo5aBa5VGjiEDQc53ed?key=l2ZwNEe_9CxUi_jIR3RHQQ" alt=""><figcaption></figcaption></figure>

Below, you can see how to configure this automation:

### 1. Access automations in SAC 360º

In SAC 360º, go to the Automations section to create a new automation.

### 2. Define a title for the automation

Example: Chatbot – Do not activate on call record

### 3. Triggers

In this automation we will not use a trigger.

This means that the conditions and actions will be evaluated as soon as the interaction enters one of the statuses configured in the Limit to statuses section.

### 4. Conditions

Add the following condition:

<figure><img src="/files/002b07fb7ddcb6e7385ccf5114e9a95df0c9743f" alt=""><figcaption></figcaption></figure>

* Content of the last message
* Lead → is different from → (keywords below)

List the keywords:

* offer
* ringing
* accept
* reject
* cancel
* end

That way, if the last received message contains any of these words, the chatbot will not be started.

### 5. Actions

Select the action:

* Start Chatbot

<figure><img src="/files/e0fb5274764992d887d541aa1e14e31fe8f97b32" alt=""><figcaption></figcaption></figure>

Thus, the chatbot will only be triggered when the defined condition is true (that is, when it is not a technical call record).

### 6. Action Repetition

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdc723M_Do439CnBDCtXtoeU_4We5GbTTDk3pIxCOhO-ol-TccF5iZz9Kn8xhl4DJOyfEBGpQpeaHo7yatHaPZAm6FvXZqHs1vw_l4e4Nc82ANLqdLAjw10zOn1iZwjehe7Fm9bCg?key=l2ZwNEe_9CxUi_jIR3RHQQ" alt=""><figcaption></figcaption></figure>

Leave the option as no repetitions.

### 7. Additional settings

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcMYcI_WjY9OLChdbsXQaE2_-92-B6c8n7tvmJz0A4UE_RObmQt5op2DNCosTS3qkRyxIcZJ0P9mVWbvC2_mHo1cJxhJkOdNBj2ABz4vA4LNG88niPSBjqoanw0vkvAGnyNl_Bj?key=l2ZwNEe_9CxUi_jIR3RHQQ" alt=""><figcaption></figcaption></figure>

* Limit to channels → select WhatsApp
* Limit to accounts → leave empty for (any account)
* Limit to statuses → select (Waiting, In attendance and Finished)

{% hint style="warning" %}
The option Only a single trigger per lead should be "No."
{% endhint %}

The options Limit automation based on time and Delay automation start should be left disabled, as recommended.

### Conclusion

With this automation, we ensure that the chatbot is only triggered in real interactions with the customer, avoiding unnecessary activations on technical records of phone calls. This optimizes service, improves the user experience, and keeps the communication flow cleaner and more efficient in SAC 360º.

\ <br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sprinthub.com/en/topics/general/sac-360/sac-360o-automations/sac-360o-automations-chatbot-does-not-activate-with-whatsapp-call-log.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.