> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/general/sac-360/sac-360o-automations/sac-360-automation-notify-an-employee/sac-360-automation-alerting-the-attendant-that-there-is-a-service-waiting-for-too-long.md).

# SAC 360° Automation - Alerting the Attendant that there is a Service waiting for too long

It is common, in operations with a high volume of requests in SAC360, for some tickets to end up being forgotten due to organization or follow-up failures by the agent. With that in mind, why not notify the user/agent whenever there is a ticket awaiting action?\
\
Below, we present a simple and visual approach, which can be easily customized according to the needs and dynamics of each business.

## Creating a new stage

To create a new stage, follow the flow below:

1. Access Settings, located in the lower-left corner of the screen.
2. Then, click on Funnel / Pipeline.
3. Select the funnel in which the new stage will be created.
4. Create the stage with the name “LEAD NO RESPONSE”.

You can check examples below.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FWYBpHzEBoXaWAHABwboQ%2Funknown.jpeg?alt=media&amp;token=e7456844-c47f-48d7-bc9e-df07b1f997e6" alt=""><figcaption><p><em>Accessing the settings</em></p></figcaption></figure>

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FQvYobbqTMvPBY2XePWq2%2Funknown.jpeg?alt=media&amp;token=a2fe6aa3-2193-4d86-ac1a-eea8e74c248a" alt=""><figcaption><p><em>Accessing Funnel / Pipeline</em></p></figcaption></figure>

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FZySWcmfGkFFyaa49jCou%2Funknown.jpeg?alt=media&amp;token=93f03e73-7ffa-49b7-a71c-5dbb37cb5ef1" alt=""><figcaption><p><em>Choosing the funnel and creating the stage</em></p></figcaption></figure>

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2Fo5Np7T7KKGnORofVWD0u%2Funknown.jpeg?alt=media&amp;token=4c2ec005-1ee7-4df4-9ffc-5b073d412aab" alt=""><figcaption><p>Creating the stage</p></figcaption></figure>

## Creating the automations

Now we will create the automation responsible for moving the lead to the stage when it remains unanswered.

Follow the flow below to configure the automation:

Automation creation\
\- Define a title for the automation.\
\- In Triggers, it is not necessary to configure any option.

Conditions\
\- Add the condition “The date of the last message”.\
\- Configure as follows:\
&#x20;    Source: from the lead\
&#x20;    Rule: was more than\
&#x20;    Time: set the desired period without response.\
&#x20;    Enable the option “Check conditions until they are met”.

With this, when the lead remains for the defined time without response, the automation will be executed and the employee will be notified.\
\
Actions\
\- Add the action “Change service stage”.\
\- Select the stage created earlier: “LEAD NO RESPONSE”.

You can check examples below.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FE18rRGdoZWjv2UmB4DWt%2Funknown.jpeg?alt=media&amp;token=7f5a93aa-dece-449c-90fb-9071ef818149" alt=""><figcaption><p><em>Conditions</em></p></figcaption></figure>

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2Fqrr375VaHstBrd89M6QT%2Funknown.jpeg?alt=media&amp;token=e286f017-7a03-4dc0-9b47-ebebe92f7751" alt=""><figcaption><p><em>Actions</em></p></figcaption></figure>

## Automation to notify the employee&#x20;

In this new automation, you should use as the trigger the stage change to **LATE**. With this approach, even if the manager manually changes the stage to **LATE** the agent will still receive the alert.

In **Conditions**, add your team's service hours, ensuring that the system does not send WhatsApp messages outside business hours.

Finally, in **Actions**, set the action to **send a WhatsApp message to the employee**.<br>

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FgRYN5vhuiAXpTDOIxRp4%2Fimage.png?alt=media&amp;token=4f6a5b71-18d9-4e03-9db2-f4438d0e26e2" alt=""><figcaption></figcaption></figure>

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FifChltQu061u1qX4C5tx%2FCaptura%20de%20Tela%202024-04-16%20a%CC%80s%2012.11.53.png?alt=media&amp;token=caf7758a-f912-4bb1-91d7-0c322413f22a" alt=""><figcaption></figcaption></figure>

After that, just save and wait for it to happen.
