> For the complete documentation index, see [llms.txt](https://learn.doubletick.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.doubletick.io/bot-studio/triggers/on-first-daily-message.md).

# On First Daily Message

Learn how to use the On First Daily Message trigger for controlled daily customer engagement.

**On First Daily Message** is a bot trigger that activates when a customer messages you for the first time on a given day. It runs **only once per customer per day**. If the same customer sends more messages later, the trigger will not repeat until the next day. This helps you start a **daily automation flow** without sending repeated welcome messages.

#### What's covered

* [Where to use this trigger](#where-to-use-this-trigger)
* [How to use it in Bot Studio](#how-to-use-it-in-bot-studio)
* [Key takeaways](#key-takeaways)
* [Frequently asked questions](#frequently-asked-questions)
* [Related articles](#related-articles)

<figure><img src="https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2FJY9xTzIG8atkM2A48ART%2Fimage.png?alt=media&#x26;token=008bce94-307c-45ac-9428-6a12bdb77ccc" alt=""><figcaption></figcaption></figure>

#### Where to use this trigger

Use this trigger when you want to automate **daily customer engagement** in a controlled and non-repetitive way. It is ideal for:

* **Send** daily greetings or updates when customers initiate contact
* **Guide** customers to the right product, service, or support team
* **Create** personalized daily journeys based on customer intent or attributes
* Make sure automation runs **only once per day per customer**

This trigger is best suited for businesses that want consistent engagement without overwhelming customers with repeated messages.

#### How to use it in Bot Studio

* **Open** **Bot Studio** in your DoubleTick dashboard
* **Click** **Create New Journey**
* **Select** the **On First Daily Message** trigger
* **Design** the automation flow, such as sending a greeting message, sharing a daily update or offer, assigning the chat, or using conditions based on tags or attributes
* **Save** and **publish** the journey

Once active, the bot triggers automatically when a customer sends their **first message of the day**. For example, a fashion brand can increase daily engagement and product discovery. The bot replies with a daily featured collection and quick options to explore products or connect with a stylist. This helps the brand re-engage customers, promote new arrivals, and improve conversions without additional broadcast campaigns.

#### Key takeaways

* **On First Daily Message** triggers **once every 24 hours per customer**
* It enables daily engagement without repeated automation or template spend
* It supports **multi-step conversational journeys**
* It allows **conditional logic** based on customer activity, tags, or attributes

#### Frequently asked questions

<details>

<summary>How often does On First Daily Message trigger for the same customer?</summary>

Only once every 24 hours. If the customer sends more messages later the same day, the trigger will not fire again until the next day.

</details>

<details>

<summary>Can I use conditions or attributes with this trigger?</summary>

Yes. You can add conditional logic based on customer tags, attributes, or activity to personalize the daily journey.

</details>

<details>

<summary>Does this trigger reduce the need for paid template messages?</summary>

Yes. Since it runs within the customer-initiated conversation window, it helps businesses engage customers daily without relying as heavily on paid templates.

</details>

<details>

<summary>What kind of businesses benefit most from On First Daily Message?</summary>

Businesses that want consistent daily engagement, like promoting daily offers or guiding repeat visitors, without sending the same welcome message multiple times a day.

</details>

#### Related articles

{% content-ref url="/spaces/53n17VnOICC1LtDqlENV/pages/QNf0Mg5iZN1In4U7IetZ" %}
[On Message](/bot-studio/triggers/on-message.md)
{% endcontent-ref %}

{% content-ref url="/spaces/53n17VnOICC1LtDqlENV/pages/WVrKUwutI3ceNAQsMhFr" %}
[On New Lead](/bot-studio/triggers/on-new-lead.md)
{% endcontent-ref %}

{% content-ref url="/spaces/53n17VnOICC1LtDqlENV/pages/Bv6OrDs6ObGrWBv6Ww4O" %}
[On Open Conversation](/bot-studio/triggers/on-open-conversation.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learn.doubletick.io/bot-studio/triggers/on-first-daily-message.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
