> For the complete documentation index, see [llms.txt](https://doc.youverify.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.youverify.co/guides-and-solutions/onboard-a-customer-you-only-know-by-email.md).

# Onboard a customer you only know by email

{% stepper %}
{% step %}

### Add the entity

You hold only an email. That is enough. The platform creates the entity, scores it on the limited data, and returns a **Created** entity (not an approval) with a 360 canvas.

```
POST {{baseUrl}}/v2/api/entities
{ "entityType": "individual", "isSubjectConsent": true, "email": "jane@example.com" }
```

{% endstep %}

{% step %}

### Attach transactions right away

Register the entity as a KYT client and start posting transactions, so monitoring begins *before* full KYC.
{% endstep %}

{% step %}

### Enrich progressively

As the customer supplies a phone, date of birth or ID, run the relevant verification on the *same* entity ID. The record fills out; nothing is duplicated.
{% endstep %}

{% step %}

### React to signals, escalate to a case

When a signal fires or an alert needs review, open a case on the entity and work it with Vyra's AI summary. Every action is written to the activity log. The approve / reject / restrict decision is driven by an **automated AI-agent workflow** applying your rules, escalating edge cases to a human.
{% endstep %}
{% endstepper %}

> This flow is impossible in a check-centric system, where a customer with only an email has nowhere to live until enough data exists to run a check.


---

# 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.youverify.co/guides-and-solutions/onboard-a-customer-you-only-know-by-email.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.