More than email. A platform for your whole audience

No. AMP only works in a couple of clients, requires per-sender registration with Google, and needs an ESP that can send a separate MIME part — most can't. MailInApp uses kinetic HTML and CSS techniques that work in far more inboxes, with automatic fallbacks everywhere else.

Nothing. Interactive emails render natively in the recipient's inbox. Where the inbox can't render interactivity, recipients get a clean static email with a link to a hosted live view — no accounts, no installs.

Classic Outlook (the Word rendering engine) gets dedicated table-based markup generated through conditional comments, plus a link to the fully interactive live view. New Outlook and Outlook.com render the static tier with selected kinetic enhancements.

No — MailInApp can send directly from your own verified domain, no ESP required. Or keep using Mailchimp, Brevo, SendGrid, Klaviyo, or anything that accepts custom HTML — export production-ready HTML and send it yourself. MailInApp hosts the interaction endpoints and analytics either way.

Yes. The transactional Send API lets your own backend trigger an email the same way you'd call Brevo, SendGrid or Postmark's send endpoint — freeform for OTPs, receipts and alerts, or trigger a project you designed in the studio with your own data standing in for a contact row.

Yes. The Embed API lets your own backend enroll or register your own end users into a MailInApp course or webinar and embed the viewing/joining experience — no MailInApp account needed on their end — and every registration, reminder or completion email can render as a real interactive email you designed, not a hardcoded confirmation.

Never in the email — every email client strips JavaScript. All in-email interactivity is pure HTML and CSS. That's also why it passes spam filters like any normal email.

Two ways. The dashboard's Responses view shows everything an email collected, grouped per recipient and joined with your data source — so you see who answered, not just how many. And each project can push every interaction to your own endpoint in real time via HMAC-signed webhooks, ready for your CRM or automation stack.

Gmail clips messages over ~102KB, which silently kills CSS interactivity. The studio tracks your email's size against that budget as you build and warns you before it becomes a problem.

Yes — connect your own SMTP relay once, then send a test copy to yourself or a full campaign to your contacts straight from the dashboard, with send history so you always know what's already gone out. Every email includes a one-click unsubscribe link, and opting out is account-wide: once a recipient unsubscribes, they're suppressed from every campaign you send, not just the one they clicked from.

Yes. The rating block supports star, Likert-scale and NPS styles with a configurable low-score alert threshold and an optional follow-up question on the hosted live view. Segment your audience, soft-launch to a sample, and schedule a recurring send for a rolling window like "resolved 3–7 days ago" — then read CSAT/CES/NPS averages, breakdowns and trend straight from the dashboard, export a CSV, or route low scores to your own webhook or an in-app alert email.

Yes. The Form block supports multiple choice, checkboxes, linear scale and star rating questions alongside the usual text/email/date/dropdown fields, and any question can be assigned to a page — recipients get a paginated survey with Back navigation on the hosted live view, with answers carried between pages until they submit. Results roll up per question on the Responses dashboard, same as poll and rating blocks.

You can tell it. Pick a purpose — survey, promotion, newsletter or event — when you create a project, and browse a carousel of real starter templates for it before the studio opens with one already on the canvas. It also decides which number leads your Responses dashboard: response rate for surveys, recipients engaged for promotions, opens tracked for newsletters and events. It's just a starting point — every block stays fully editable, and you can change the purpose anytime.

Yes. Save any project as a template from the studio toolbar — privately, so it's reusable by just you and your team, or publicly, so it's submitted to a community gallery every MailInApp user can start from. A public one is reviewed before it goes live, so the gallery stays worth browsing rather than a dumping ground. Either way, anything that shouldn't be reused — a product's real delivery code, a meeting's real join link, a countdown's actual deadline — is cleared automatically.

Yes — the Product block drops a Buy now button into any email that charges through your own connected Stripe account, digital or physical, with an optional inventory cap. MailInApp never holds the funds or sees card details.

Yes — every order and response links to a lightweight support inbox. Start a conversation with any past recipient, or use "Contact buyer" straight from an order, and they reply through a private link with no account needed on their end. You see the whole thread, and get notified the moment they write back.

Yes — once your sending domain is verified, you can claim any address on it (support@, hello@, billing@, and so on) and start receiving real mail there. It lands in a full mailbox dashboard inside MailInApp: reply, compose, search, and organize with folders and filters, not just read. Every plan, including Free, includes at least one address.

No. When you verify your domain with MailInApp, we configure the outbound DKIM/MAIL-FROM/DMARC records for sending and the inbound MX record for receiving — all in the same setup flow. There's no separate email hosting service to sign up for.

Incoming messages are delivered to your MailInApp mailbox dashboard, MIME-parsed into readable HTML and plain text with any attachments accessible. You can read, reply with your own attachments and CC/BCC, forward, archive or search from there, or configure a webhook to forward each message payload to your own endpoint — HMAC-signed — the moment it arrives.

Yes — replying uses a full rich-text editor (bold/italic/underline, headings, lists, blockquotes, links, a fixed color palette, and tables) and lets you attach files, whether the message is on your domain mailbox or a connected Gmail/Outlook account. For anything bigger than formatted text, "Reply with interactive email" opens the same studio editor you build campaigns in, with the message attached as context, and sends your project back as that specific reply — correctly threaded, no unsubscribe footer or tracking pixel since it's a one-to-one transactional send.

Yes — connect any Gmail, Outlook, Yahoo, or custom IMAP account from the same Mailbox, and it works as a full mail client: real folders, compose/reply/forward with your own signature and quoting, rich-text replies with attachments, live search, per-account filter rules, and Gmail-style keyboard shortcuts (j/k, e, #) — right alongside your domain mail in one unified view. Composing a brand-new message from a connected account is the one thing still plain text for now; everything else, including replying with a full interactive email, works the same as your domain mailbox.

Turn on an opt-in sender profile — name, avatar, bio and a link, behind a handle at your own mailinapp.com/p/<handle> page — and a verified card appears next to your email inside a recipient's connected inbox. It's built only from a cryptographically signed manifest embedded in the mail we send for you, never from anything a message merely claims about itself, so it can't be spoofed by a look-alike, and it's off by default.

Yes. The Quiz block scores multi-question answers server-side against a pass threshold you set and shows a results message; the Scratch-off block reveals a prize on a tap, built on the same reliable CSS technique as the accordion. Both work the same way as every other block — a real interactive version where supported, and a sensible fallback everywhere else.

Yes — invite teammates from Settings → Team as an Editor (full access, except billing and credential rotation) or a Viewer (read-only). No separate accounts to manage per project, and solo accounts work exactly as before if you never invite anyone. If two people have the same project open at once, the second save gets a clear "changed elsewhere" warning instead of silently overwriting the first person's work.

Yes — the studio's Theme panel sets project-wide tokens for your brand color, accent, text and background colors, font stack and button shape once. Any block referencing a theme token — buttons, social icons, form and quiz submit buttons — restyles everywhere it's used, in the canvas, live view and the mailed email, the moment you change the token.

Yes — select anything on the canvas, then "Save as component" from the Inspector. It's saved to your account, not just that project, and shows up under My components in every project's block panel from then on, ready to drag in as an independent copy you can restyle freely.

If you want it to. Click the ✨ Suggest button next to a subject line or any text field in the studio and get a few AI-drafted options grounded in your project's purpose and existing copy — nothing is ever written in for you automatically, you pick what to use.

Yes — Settings → Privacy & data lets you download a complete JSON export of everything your account owns, or permanently delete the account (projects, contacts, responses, credentials, all of it) through an emailed confirmation link, with no support ticket required. Recipients get a self-service path too: every unsubscribe page includes a form to request a correction or deletion of their own data, which opens a ticket straight to you.