> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/value-stream-modeller/value-stream-examples/new-customer-registration.md).

# New Registered Customer

The New Registered Customer value stream template streamlines the onboarding experience by automating welcome emails and delivering personalized coupon codes to first-time registrants. It's designed for a quick setup and empowers business users to implement effective customer engagement flows that increase loyalty and encourage early purchases.

## Key features

| Feature                           | Description                                                                                |
| --------------------------------- | ------------------------------------------------------------------------------------------ |
| **Customer registration trigger** | Automatically initiates the process when a new customer registers at the store.            |
| **Automated welcome email**       | Sends a personalized welcome email.                                                        |
| **Automated coupon creation**     | Sends a follow-up email containing a unique coupon code for the first purchase.            |
| **Process automation**            | Reduces manual effort through standardized workflows and orchestration engine integration. |

## Process template flow

When a user registers for the first time on the storefront, the system automatically initiates the onboarding process. This triggers an automated welcome email containing a personalized coupon code, encouraging the customer to make their first purchase.

<figure><img src="/files/97F6pDC2pRTKbhdjvm6B" alt=""><figcaption></figcaption></figure>

### Process trigger

The process starts when a new customer registers at the store. In this case, the `email_received` event initiates the flow. However, you can choose a different event from the drop-down list that would trigger the process. The events available in the list are the ones configured in the Value Stream Modeller [Event Registry](/value-stream-modeller/settings-and-configuration/events/event-registry.md).

<figure><img src="/files/dXvv0qdBQI1BvnCyPOOE" alt=""><figcaption></figcaption></figure>

### Welcome email

The customer receives a welcome email containing information about their newly created account. The content of the email itself is not editable. The template for it is fetched directly from a connected Mailjet account.

<figure><img src="/files/AFYxUWEieuUtk0aoOG1T" alt=""><figcaption></figcaption></figure>

### Welcome coupon

The customer receives a first-time coupon to encourage their initial purchase. The list of available coupons reflects the ones that are created in the Management Dashboard - [Coupons](/ce/management-dashboard/customer-management/coupons.md).

<figure><img src="/files/n4bsKgdiR1BrY6BRFKWH" alt=""><figcaption></figcaption></figure>


---

# 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://developer.emporix.io/value-stream-modeller/value-stream-examples/new-customer-registration.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.
