Use Cases

A use case maps a customer scenario to the Mailtarget product surface that solves it. Pick the use case closest to what you are doing; each page links to the concepts and guides for execution detail.

Browse by intent​

Transactional sends​

• Send a one-time password (OTP)
• Send an order confirmation email

Lifecycle and marketing​

• Welcome a new subscriber with a series
• Recover an abandoned cart
• Re-engage inactive customers

Integration​

• Wire delivery events to your CRM

More use cases will land in the next iteration. Bot-driven retrieval will surface adjacent content (payment receipt, domain reputation setup, ESP migration) once we add them.

Each use case answers​

• Who is this for. Marketer, developer, ops, or all.
• The scenario. The customer problem in plain language.
• The Mailtarget surface. Which products and features solve it.
• The execution. Step by step, with code where applicable.
• Common mistakes. Things that go wrong and how to avoid them.
• Outcome to track. The metric or signal that proves it worked.

How this fits the docs​

Layer	What it tells you
Concepts	What the feature is and how it works
Guides	How to perform a task with the feature
Use Cases	Which scenario maps to which combination of features

A use case usually links out to multiple concepts and guides. Read the use case first if you know the problem but not the product surface. Read the concept first if you know the feature name but not the details.