Email Studio

Email Studio is the premium Capell extension for transactional email. It gives a site one place to manage email templates, delivery profiles, sent-message history, recipient outcomes, suppressions, provider events, replies, and tracking diagnostics.

This is not a newsletter tool. It is the operational email layer behind forms, editorial notifications, account emails, workflow alerts, and package-owned transactional messages.

Who It Is For

Email Studio is for teams that need to answer support and delivery questions without digging through queue logs or provider dashboards.

Typical use cases:

• a FormBuilder confirmation email needs a branded template per site;
• an editor wants to preview the exact notification a workflow will send;
• support needs to know whether a customer received an email;
• a provider rejects a message and the reason needs to be visible in Capell;
• a hard bounce or complaint should suppress future sends;
• replies need to land in a shared admin inbox instead of a personal mailbox.

What You Get

• Site-scoped email templates with locale-aware variants.
• Delivery profiles for sender identity, reply-to addresses, provider type, and provider settings.
• A package API so first-party and project packages can register and send approved templates.
• Send records with rendered subject/body snapshots and trigger context.
• Recipient rows with queue, sent, failed, partially failed, and suppressed states.
• Suppression checks before queueing and again before provider delivery.
• Provider adapter support for fake, SMTP, and Postmark in the first implementation slice.
• A schema ready for provider events, inbound replies, open/click tracking, and retention redaction.

Why It Sells

Most Laravel apps can send email. That is not the product.

The product is knowing what happened after the send button was pressed. Email Studio gives agencies and client teams a paid control plane around transactional email:

• fewer support tickets that need developer access;
• fewer one-off mailer implementations across packages;
• clearer delivery diagnostics;
• safer handling of bounces, complaints, and suppressions;
• a foundation for client-branded templates and approval workflows.

For Capell, it creates a clean upsell path from FormBuilder, PublishingStudio, CampaignStudio, and any package that needs reliable notifications.

How It Fits With Other Packages

Package	Relationship
FormBuilder	Can send confirmation and admin notification emails through Email Studio templates.
PublishingStudio	Can send workflow, approval, rejection, and scheduled-publish notifications.
CampaignStudio	Can use tracked links and attribution when email clicks matter to campaign reporting.
Insights	Can consume click/open events once tracking is implemented.
Newsletter or subscriber tooling	Remains responsible for audiences, opt-in, imports, segments, and bulk sends.

Extension Boundary

Email Studio should not leak authoring state into public frontend output. Public tracking and webhook routes must use opaque tokens or provider secrets and must return generic responses for invalid tokens.

The package stores rendered snapshots because auditability matters. Retention tooling will redact rendered bodies and context snapshots after the configured retention window while keeping delivery metadata useful.

Current Status

The current package implementation includes:

• package registration and manifest metadata;
• database tables, models, factories, and protected table registration;
• template registration, variable rendering, and variant resolution;
• send recording, queue dispatch, provider delivery, suppressions, and provider failure handling;
• focused tests around rendering, scope safety, suppressions, delivery, failure paths, and locale resolution.

Planned next slices:

• provider webhook event recording;
• inbound reply recording;
• open and click tracking routes;
• retention redaction job;
• Filament resources and diagnostics screens;
• FormBuilder integration.

Marketplace Positioning

Use this short listing copy in marketplace or pricing surfaces:

Email Studio gives Capell a transactional email command centre: reusable templates, delivery profiles, sent-message audit trails, suppressions, replies, provider events, and tracking diagnostics.

Use this longer description on the detail page:

Email Studio turns transactional email into a managed Capell feature. Packages send through a shared Action, templates stay site-aware and approval-ready, provider results are recorded, suppressed recipients are blocked before delivery, and support teams can see what was rendered and what happened next. It is built for confirmations, workflow alerts, account messages, and package notifications rather than newsletter audiences or bulk campaign sends.

Installation

composer require capell-app/email-studio
php artisan migrate

Exact installer commands may change as the package gains admin resources and demo data. Confirm available commands with:

php artisan list capell

Developer Documentation

Detailed package docs live in the package repository:

• packages/email-studio/README.md
• packages/email-studio/docs/overview.md
• packages/email-studio/docs/email-studio-api.md
• packages/email-studio/docs/email-studio-database.md