Hi.

SLA can be defined since 15 mins:

But yes, Escalation emails can be sent since 30 minutes before or immediately:

That sounds like a great feature, to have Before 15 minutes or 10 or 20 minutes.

I’d suggest to submit (in case it does not already exist) the Feature Request here, and ensure to share de Link to the idea in order we could vote on it:

Freshworks Ideas | Freshworks Community

You could also touch base here, with the Developers community, which is the Community for the ones who actually program in Freshworks:

Freshworks Developer Community

Regards,

To achieve more granular time-based automations, several strategies and tools can be employed, depending on the specific requirements and the context in which the automations are needed. Here are some approaches:

1. **Using Advanced Scheduling Tools**

Many automation platforms offer advanced scheduling capabilities. Tools like **Cron (Unix-based systems)**, **Task Scheduler (Windows)**, and cloud-based solutions like **AWS CloudWatch Events** or **Google Cloud Scheduler** allow for precise scheduling down to the minute or even second.

- **Cron**: Allows for very detailed scheduling, such as running a task every minute or at specific times of the day, week, or month.
- **Task Scheduler**: Similar to Cron, it provides detailed scheduling options on Windows systems.

2. **Utilizing Workflow Automation Tools**

Platforms like **Zapier**, **Integromat (now Make)**, and **Microsoft Power Automate** enable users to create complex workflows with detailed time-based triggers.

- **Zapier**: Allows workflows to be triggered at specific times, with options for intervals as granular as 1 minute.
- **Make (Integromat)**: Offers similar capabilities with even more detailed customization for triggers and actions.

3. **Custom Scripts and Code**

Writing custom scripts using languages like **Python**, **JavaScript**, or **Bash** can provide the most flexibility. These scripts can be run via cron jobs or similar schedulers to execute tasks at precise intervals.

- **Python**: Libraries like `schedule` or `APScheduler` can be used to create and manage complex scheduling.
- **JavaScript (Node.js)**: The `node-cron` library can be used to create cron-like schedules within a Node.js application.

4. **Real-Time Automation Platforms**

For tasks that require sub-minute precision, real-time automation platforms or event-driven architectures might be necessary. Tools like **Apache Kafka**, **AWS Lambda**, or **Azure Functions** can be used to trigger actions based on real-time data streams or events.

- **Apache Kafka**: Allows for real-time data processing and can trigger actions based on events in the data stream.
- **AWS Lambda / Azure Functions**: Serverless computing options that can execute code in response to events with very low latency.

5. **IoT and Edge Computing**

For applications involving IoT (Internet of Things), edge computing platforms can provide very granular control over time-based actions. Devices can be programmed to execute actions based on precise timing or sensor data.

### Implementation Examples

#### Cron Example (Linux-based system):

To run a script every 5 minutes:
```bash
*/5 * * * * /path/to/script.sh
```

#### Python with APScheduler:

```python
from apscheduler.schedulers.blocking import BlockingScheduler

def job():
    print("Job executed")

scheduler = BlockingScheduler()
scheduler.add_job(job, 'interval', minutes=1)
scheduler.start()
```

#### Zapier Scheduled Task:

1. Create a new Zap.
2. Set the trigger to "Schedule by Zapier".
3. Choose the desired interval (e.g., every 15 minutes).
4. Define the actions to be performed.

### Conclusion

More granular time-based automations can be achieved using a combination of advanced scheduling tools, workflow automation platforms, custom scripts, real-time automation platforms, and IoT solutions. The choice of tool or approach will depend on the specific requirements, such as the granularity of time intervals, the complexity of the tasks, and the environment in which the automation is being implemented.

Can we please get a “minutes” option for time-based automations or SLA escalations? The current restriction to “hours” disrupts our ability to manage SLA coverage effectively and impacts our egg rate today.

Yes it is essential