Every contact form, every site. One inbox, one reply.
Each site you run has a contact form, and each one posts somewhere different: your mailbox, the client's, a plugin's dashboard, a Slack channel from 2022. Multisite Agent gives every form on every site the same destination. You see which site and page a message came from, answer it from that site's own address, and spam blocked on one site is blocked on all of them.
One script tag per site · No form backend to host · One site free
The messages are there. They are just in twenty places.
Contact forms are the one part of a site that talks back, and across a portfolio they talk into mailboxes nobody checks on purpose.
Form mail scattered across mailboxes
Site A posts to the client, site B to you, site C to an address that stopped existing when the intern left. A lead sits unanswered for a week and nobody knows it arrived.
Spam, times twenty
The same bot hits every form you run within the hour. You tune a filter on one site; the other nineteen still forward the junk, and real messages drown in it.
Who answered this?
The client replies, you reply, or everyone assumes the other one did. There is no status, no owner and no record of what was sent.
A form backend per stack
A plugin on WordPress, a third-party endpoint on the static sites, SMTP settings that break silently after a password change. Each one is yours to keep alive.
One destination for every form. One place to answer.
Add the script tag once per site, and its forms post into the shared inbox. From there it works like a support desk, without a plugin or a backend per site.
Every submission in one list
Each message shows which site and page it came from, when, and in which language. Filter by site, status or date, and save a view.
Statuses, owners and notes
Open, waiting, resolved and spam. Assign a message to a teammate, leave an internal note, and see who replied with what.
Reply from the site's own address
The answer goes out from that site's domain, so the sender gets a normal email thread from the business they wrote to, not from a tool.
Language detected, translation one click
A German message on a German site, a Spanish one on a Spanish site. Read a translation, answer with a template in the sender's language.
Spam scoring shared across the portfolio
When the same sender or text hits several of your sites, it is flagged or blocked everywhere at once. Flagged messages stay visible under a label, never silently dropped.
No backend, no per-submission fees
One embed per site replaces the form plugin and the SMTP setup. Existing forms keep their fields; the script only changes where they post.
From "did anyone see this?" to a thread with an owner.
The inbox is less about reading faster and more about everyone knowing who is answering what, and the client seeing it too.
Before: a lead takes the scenic route
- A message lands in the client's mailbox, between newsletters.
- A week later the client forwards it to you: "did we ever answer this?"
- You answer from your own address; the sender has never heard of you.
- The client answers too, two days later, with a different offer.
- The same bot that sent the spam around it hits your other sites tomorrow.
After: one inbox, one owner, one reply
- The message appears in the inbox, tagged with the site and the page.
- It is assigned to whoever handles that site; the status says open.
- They reply from the site's own address, in the sender's language.
- The client sees the thread and its status in their workspace.
- The spam around it is scored once and blocked on every site.
The client sees the status
A client with a read-only workspace sees their site's messages, who owns each one and whether it was answered. The forwarding stops.
Replies look like they come from the business
Senders get an email from the site they wrote to. Internally, the thread shows the full history, notes and who sent what.
Handovers without a chat message
Assign a message, leave a note, change the status. The next person opens the inbox and knows where it stands.
Set up once. Then it runs.
Add one script tag
Paste the Multisite script into each site once, before the closing head tag.
Forms post to the inbox
Existing forms keep their fields. Submissions arrive with the site, page and language attached.
Triage
Open, waiting, resolved, spam. Assign to a teammate, add a note, save a filter per site or client.
Reply from the site
Answer in the sender's language, from the site's own address. The sender gets a normal email thread.
Questions about One Inbox.
Do I have to rebuild my contact forms?
No. The script picks up the forms a site already has and changes where they post. Fields, layout and validation stay as they are.
Where do replies come from?
From the site's own domain, so the sender sees a reply from the business they contacted. Each site's sending address is verified once in the panel.
How does spam filtering work across sites?
Every submission is scored, and what is learned on one site applies to all of them. A sender or text that hits several of your sites is flagged or blocked everywhere. Flagged messages stay visible under a spam label.
Can a client see only their own messages?
Yes. Group sites into a workspace per client and invite the client as a read-only viewer. They see their sites' messages and statuses, nothing else.
Does this work with WordPress, Webflow or a static site?
Yes. The inbox needs one script tag per site, which works on WordPress, Webflow, Shopify, static sites and custom code.
One inbox for all of them.
Add one script tag per site and answer every contact form from one place. One site is free.