What’s new in Mailoo: one dashboard instead of five browser tabs

Over the past few weeks we shipped a chunky batch of updates (from 1.6.0 through 1.10.1 and counting). In one line: chat, feedback forms, a blog that plays nicely with headless CMS, subscribers, and images — all in one place, without feeling like you’re administrating half the internet.

Chat that knows where people came from

There is a full chat integration: visitor sessions, real-time messages over WebSocket, replies from the dashboard. Small thing, big relief: the dialog keeps the page URL the visitor wrote from — fewer “which product did you mean?” moments.

For teams who like production to behave, we expanded WebSocket documentation and deployment notes — so you’re not reading tea leaves to wire it up.

Feedback / contact forms as their own integration

A dedicated contact / feedback form type: submissions from your site land in the same world as your other integrations. Wire it to footer bug reports, a “contact us” page, or anything similar — without yet another homemade spreadsheet.

In docs and examples we stress server-side webhook calls with the key in environment variables: no secrets in the browser, calmer nights.

API keys: clearer scopes and limits

API key management is clearer: which operations are allowed (forms, feedback, chat, blog, images, and so on) and how that shows up in the UI. Restricted keys now carry a rate limit tier label — so “restricted” means both permissions and pacing.

If you integrate: fewer guesses, more hints in the UI and docs.

Blog, images, and headless CMS

On the blog and media side:

Public embed URLs for images in API responses are easier to use for previews and content on your CMS or frontend.
Article Markdown and HTML keep playing nicely with safety and predictable links (including build work around dompurify).

For you: headless CMS + Mailoo — content and newsletters/forms in one flow, less manual duplication.

Subscribers and forms (newsletter and beyond)

Classic subscription forms stay at the core: capture contacts, templates, campaigns — they sit naturally next to feedback and chat. One project, several entry points (form, chat, contact), one place to respond.

Integration UI and languages

The dashboard goes deeper on integration cards: Form, Contact/Feedback, chat (JSBOX), blog — with localization (including DE/EN/ES/RU), proper loading and error states, and quick actions. Less “what is this integration?”, more “got it in a minute”.

Why it matters

The old pattern: newsletter in one tool, chat in another, forms in a third, blog somewhere else. You can now fold a big slice of that into Mailoo: comms, inbound from the site, content hooks for integrations — in one workable UI, with sensible keys, docs, and security defaults.

Versions for the curious

Recent updates span roughly 1.6.x → 1.10.1: infrastructure, API, web app, and user-facing documentation moved in step. For setup details and what each feature can do, see Mailoo’s documentation on the service website and under Docs in the product.

Thanks for reading. If you’ve already tried something here, tell us how it went in the wild; if not, spin up a test project and click everything while nobody’s watching.