Set up what you send, and why

The final onboarding step — Create Your First Use Case — does two things on one screen: it gives your email program its first use case, and it proves your sending setup works by delivering one safe email to you.

What's a use case?

A use case is the "why" behind an email: order confirmations, password resets, a newsletter. Every email you send through NevarMail belongs to a use case, so recipients (and your team) always know why a message went out. Use cases live inside a project and can carry a category — transactional or marketing — that steers defaults toward responsible sending.

Adopt the default, or create your own

Every project starts with a default use case named General, so you're never starting from zero. Its emails carry the unsubscribe footer, which is why this step also asks for your postal address — the footer has to say who sent the email. The step offers a simple choice:

• Use existing (preselected) — adopt the project's default use case (or any other use case your team has already created). For most teams this is the right first move; you can add more use cases anytime from Settings → Use Cases.
• Create your own — name it (required), optionally describe it, pick a category, and — if your organization has more than one project — choose which project it belongs to. A use case name must be unique within its project; if you pick a name that already exists there, we tell you inline and you can adjust.

Why the recipient is locked

The first email goes to the email address you signed in with — shown read-only, not editable, and re-checked on our server no matter what the browser sends.

That's deliberate, and it reflects two NevarMail principles:

1. You send mail; we don't. This first send runs on your own provider account and infrastructure — NevarMail is never the sender of record.
2. Recipients stay yours. Onboarding never asks for, stores, or sends to anyone else's address. The only recipient in this flow is you, so no recipient data enters our systems while you're proving the pipeline.

Safety checks still apply: if your sending domain isn't verified yet, NevarMail blocks the send and the step shows exactly why — verify the domain and send again. Suppressed addresses are never mailed.

Subject and body

The subject and body come pre-filled with a sensible default referencing your use case — edit both freely. You write plain text; NevarMail converts it to simple HTML for delivery and, because the default use case is suppressable, appends the unsubscribe footer with your postal address.

Optional: Suggest with AI

If AI assist is enabled in your NevarMail environment, a Suggest with AI button appears in the create-your-own form. One click drafts a name, description, subject, and body for you — using only your organization-level context (the category you picked and the name you started typing), never any recipient or list data. Everything it writes stays fully editable, it never runs unless you click it, and the step works completely without it. If AI assist isn't enabled, the button simply doesn't exist — there's nothing to configure or dismiss.

What happens after you send

• Your first email lands in your inbox — proof the pipeline works end-to-end.
• The "Create your first use case" task on your dashboard is tagged with the project and use case you used, so your team can see exactly where the first send happened.
• Onboarding is complete. From here, head to your dashboard to connect more domains, import templates, or create your next use case.

You can also choose Skip for now — onboarding completes without a send, and you can prove the pipeline later from Compose.