> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/guides-and-best-practices/batch-ai/how-to-send-every-message-at-the-moment-each-customer-is-most-likely-to-engage.md).

# How to Send Every Message at the Moment Each Customer Is Most Likely to Engage?

## What Is the Best Send Time Score?

Batch AI Predict's **Best Send Time** score predicts, for each customer, the optimal time of day to send a campaign message in order to maximize engagement. The output is a time attribute on the customer profile, derived from each customer's observed engagement patterns across past communications.

## Why Use It?

Sending everyone the same campaign at the same time ignores the reality that your customers' attention is not evenly distributed across the day. A message sent at the wrong time competes with noise; the same message sent at the right moment lands when the customer is receptive.

With the Best Send Time score, you can:

* **Increase open and click rates** by reaching each customer when they are most likely to engage.
* **Reduce the noise effect** of mass simultaneous sends, which tend to trigger higher opt-out rates.
* **Improve inbox placement** by spreading send volume across the day rather than creating spikes.

## How to Use This Score in Batch

### Orchestration: Delay Send to Each Customer's Optimal Time (Primary Use)

The recommended setup: use the Best Send Time attribute as a send-time delay in your orchestration, so each customer receives the message at their personally predicted optimal moment.

**How to set it up:**

1. Go to **Automations** in your Batch dashboard.
2. In your automation or journey, add a **wait step** before the send action:
   * Wait until: `Best send time` attribute value for each customer
3. Define a fallback time for customers without a predicted send time (for example, new profiles with insufficient history).
4. Activate. Each customer receives the campaign at their individually predicted optimal time, within your defined send window.

{% hint style="warning" %}
Define a maximum delay window (for example, send within 24 hours) to avoid messages being held too long for customers whose optimal time is outside your intended campaign window.
{% endhint %}

**Recommended test**: Run a **Targeting Comparison Test** between the send-time-optimized version and a fixed send-time version of the same campaign. Compare open rates and click rates by time slot. See the Performance Measurement Guide for details.

## Real-World Use Cases

| **Industry**              | **Example use case**                                                                                                                                                 |
| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Retail**                | Weekly newsletter: instead of sending to all subscribers at 10am on Tuesday, dispatch each customer's message at their personal optimal time within a 24-hour window |
| **Travel**                | Inspiration or deal alert: reach each traveler at the moment they are most likely to browse and book, rather than at a fixed batch send time                         |
| **Media & Entertainment** | Content digest: send each subscriber their weekly digest at the time they most often engage with the app or inbox, maximizing open and content consumption rates     |
| **Retail (subscription)** | Renewal or upsell campaign: time the message for each subscriber individually to maximize the likelihood of a click-through at a moment of genuine attention         |

## Related Documentation

* How to Measure the Performance of Batch AI Predict Scores
* [Omnichannel Trigger Automations](https://doc.batch.com/getting-started/features/customer-engagement-platform/orchestration/trigger-automations#analysing-automation-with-analytics)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://doc.batch.com/guides-and-best-practices/batch-ai/how-to-send-every-message-at-the-moment-each-customer-is-most-likely-to-engage.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.