What it produces
You give it a channel and a brief (“a friendly welcome email for a new SaaS signup with a button to set up their workspace”), and it drafts channel-appropriate content:- Email — a subject line, an optional preheader, a structured body of headings, paragraphs, buttons, lists, and dividers, and optionally a color palette (accent for buttons/links, heading, and body text colors). Colors are applied only when the brief mentions a color, brand, or look/feel; otherwise the email keeps its neutral defaults.
- SMS — a single message body, kept within SMS length budgets.
- Push — a short title and body.
Where it fits in the workflow
AI authoring is available in two places:- Dashboard editor — the Write with AI button in the template editor drafts or rewrites a template inline. Nothing goes live until you review and publish.
- MCP server — the
senderkit_templates_createandsenderkit_templates_regeneratetools let an AI agent (Claude, Cursor, etc.) generate templates from a brief. Both tools save the result as a draft and return a link to the editor for review — publishing is always a deliberate human step.
What to expect
Treat the output as a strong first draft, not a finished template:- Review the copy — it’s a starting point; tighten it to your voice.
- Check the variables — confirm the names and types match the data you’ll actually pass at send time.
- Then publish — the draft only affects real sends once you publish it as the current version.
Templates
Where authored drafts live.
Versioning
The draft is a version — publish it to go live.