> ## Documentation Index
> Fetch the complete documentation index at: https://help.lobyco.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Welcome new customers
> Give every customer who signs up a welcome coupon and a push, from a flow that starts the moment they join.
This page shows you how to welcome each new customer as soon as they sign up. A flow starts when a customer joins. It gives them a welcome coupon, then a push tells them it's in the app.
## What you'll build
```mermaid theme={"system"}
flowchart LR
A["Customer event
Sign-up"] --> B["Offer
Gift"]
B --> C["Activity event
Assigned"]
C --> D[Push]
```
The flow doesn't run on a schedule. The **Customer event** starts it once for each customer who signs up, while it's listening. A **Gift** is an [offer type](/business-documentation/activities/offers/offer-types) that a flow gives out. The **Activity event** passes on each customer who got the coupon, so the push only reaches them.
**Customer Sign-Up** is the only customer event you can pick. So a journey that starts from another moment, such as a first purchase, can't start this way. Start it from a **Member segment** that runs every day instead, with rules that find the customers you want. [Give customers a birthday voucher](/business-documentation/use-cases/give-customers-a-birthday-voucher) builds a flow like that.
## Settings
| Block | What to set here |
| - | - |
| **Customer event** | **Customer Sign-Up**, with a **Start date** and **End date** for when it listens. |
| **Offer** | **Type** **Gift**, a **Validity period** in days, and the welcome discount. |
| **Activity event** | **Assigned**. The block sets it for you. |
| **Push** | Your welcome message. Its **Segmentation** is set to **Custom** for you once it's connected. |
All the dates have to fall inside the campaign's dates. Give the campaign dates that cover the whole time you want to welcome new customers. See [Create a campaign](/business-documentation/campaigns/create-a-campaign).
## Start the flow on sign-up
Open the campaign's **Orchestration** view, in **Design** mode. From **Trigger** in the **Block library**, drag a **Customer event** onto the canvas and double-click it.
1. On **Choose Event**, keep **Customer Sign-Up** under **Select customer event**. It's already selected.
2. On **Schedule real-time run**, set the **Start date**, when the flow starts listening, and the **End date**, when it stops.
3. Select **Save**. On the canvas, the block reads **Sign-up**.
Only customers who sign up between those dates get the welcome. Customers who joined before the start date don't.
## Add the welcome coupon
From **Activity**, add an **Offer**. Connect the **Customer event** to it first, then double-click the **Offer** and choose **From Scratch**. Connecting it first means the **Type** list shows only the types a flow can hand out, and the form leaves out **Segmentation**.
Fill in the offer as described in [Create an offer](/business-documentation/activities/offers/create-an-offer). These settings make it a welcome coupon.
* In **Details**, set **Type** to **Gift** before anything else. That switches on **Pre-activated**. Leave it on, so the coupon works without the customer activating it in the app.
* Set **Validity period** to how many days a new customer has to use it, such as 30. The days count from when the flow gives it out, straight after they sign up. A coupon never lasts past the offer's end date, so set the offer's dates to cover the whole campaign.
* In **Discount**, set up the welcome discount, such as 10% off the basket. See [Discount types](/business-documentation/activities/offers/discount-types).
* Under **Limits**, keep **Redemption limit** at 1, so each customer can use it once. See [Stacking and limits](/business-documentation/activities/offers/stacking-and-limits#redemption-limit).
Select **Publish** and confirm. Publishing the flow doesn't publish the coupon. If you don't publish it here, new customers go through the flow and get nothing.
## Add a push
From **Trigger**, add an **Activity event** and connect the **Offer** to it. It reads **Assigned**, the one event an offer has.
From **Activity**, add a **Push** and connect the **Activity event** to it. Double-click the **Push** and write your welcome message, as described in [Push notifications](/business-documentation/communication/push). Its **Segmentation** already reads **Custom**, so each customer who gets the coupon gets the push.
Publish the push from its form, too. A push that isn't published when a customer reaches it doesn't go out, and isn't sent later. See [When a triggered communication acts](/business-documentation/communication/triggering#when-a-triggered-communication-acts).
*The welcome flow on the canvas*
## Save and publish the flow
Select **Save** at the top right of the canvas. Then select **Publish** on the **Customer event**, the block with the **Start** tab, and confirm. That takes it out of **Draft**, so sign-ups start the flow from its start date.
## Check the result
Once customers have signed up, check these two things.
* Switch the canvas to **Live stats**. It shows the flow with a count on each block, refreshed every minute. The counts grow as new customers go through the flow.
* Find a new customer in **[Members](/business-documentation/self-service/find-a-customer)** and open their **Coupons** tab. The welcome coupon is there, with its **Valid from** and **Valid to** dates.
If the counts stop at the **Offer** or the **Push**, check that both are published.
## Variation: send the push a few days later
To remind new customers about their coupon instead of telling them straight away, put a **Delay** between the **Activity event** and the **Push**.
```mermaid theme={"system"}
flowchart TB
A["Customer event
Sign-up"] --> B["Offer
Gift"] --> C["Activity event
Assigned"] --> D["Delay
3 days"] --> E[Push]
```
In the **Delay**, set it to wait for 3 **day(s)**, then continue at a time of day, such as 10:00. Each customer's wait starts when they reach the **Delay**, so everyone gets the push three days after they joined, at 10:00. The [Block reference](/business-documentation/campaigns/orchestration-canvas/block-reference#delay) describes every Delay setting.
## Variation: tell your own system
To pass each new customer on to another system, such as your CRM, a second flow can start from a **Customer event** and end in an **[Outbound API](/business-documentation/campaigns/orchestration-canvas/block-reference#outbound-api)** block. Set it up together with whoever runs that system. [Outbound API connection](/integration/external-integrations/outboundapi-connection) tells them how the block calls their system.
## Related
* [Orchestration canvas](/business-documentation/campaigns/orchestration-canvas) explains what can start a flow, and how to publish it.
* [Offer types](/business-documentation/activities/offers/offer-types) explains **Gift** and the other reward types.
* [Give customers a birthday voucher](/business-documentation/use-cases/give-customers-a-birthday-voucher) builds the same offer-and-push flow from a daily segment, with a voucher.
* [Block reference](/business-documentation/campaigns/orchestration-canvas/block-reference) describes the **Customer event**, **Activity event**, **Delay** and **Outbound API** blocks in full.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.