The shared inbox for info@ and support@
Run your shared mailbox as a team.
Parly turns info@, support@ or sales@ into a shared inbox. Everyone signs in with their own login, sees who is handling what and who already replied, and every answer goes out as real email from your address. Work in Parly, or answer from a Slack or Microsoft Teams thread if that is where your team talks.
Create your workspace in a minute. First month free.
- Aria LundNew9:41Order #5120 didn't arrive · Hi, my order was marked delivered but nothing came
- Tom BeckersWaiting9:12Change delivery address · Could you still redirect this to my office before it ships?
- billing@northwind.coSnoozedTueInvoice question · We were charged twice on the May invoice, can you check
- Priya NairOpenMonBulk order, 40 units · Looking to place a larger order for the team, what is the
The problem
One password.
Everyone logged in.
The shared mailbox started as a convenience: one login for the whole team, taped to a monitor. Then two people answered the same customer, a third assumed someone had it, and nobody could say who sent what. There is no audit trail when everyone is the same account.
The problem was never the mailbox. It was that a mailbox was never meant to be a team tool.
How it works
Three steps. None of them are “migrate your mail”.
Connect the mailbox
Sign in with Microsoft 365, or connect any other mailbox over IMAP. No password to share for Microsoft, no DNS changes, no migration. info@ keeps working exactly as it does today, with your team on top.
Grant scoped access
Give people individual logins and a role: user, mailbox admin, company admin. No more one shared password taped to a monitor. Every action is attributed and audited.
Work it like a team
Leave internal notes, set status, see who replied last, run automations and SLAs. Replies go out under a send policy, so a restricted mailbox can only answer the recipients you allow.
Hi, the second jacket arrived damaged so I would like to return it for a refund.
@sven can you approve a refund over €200 on this one?
Work the thread
Talk it through before you reply.
Set a status, add a tag, and see who replied last, so nothing is answered twice. Helpdesk mode adds assignment. Leave an internal note and @mention a colleague to pull them in; notes are never emailed to the customer.
If your team lives in Slack or Teams
Answer from where your team already talks.
Link a mailbox to a Slack or Microsoft Teams channel and every customer email shows up there as a thread. Press Reply and the answer goes out as real email from your address. The shared inbox behind it keeps everything: logins per person, status, internal notes and an audit trail, so the channel can scroll on and nothing is lost. Not on Slack or Teams? Parly works on its own.
- Press Reply on a customer email in Slack and your answer goes out as real email from your address.
- Start a new email without leaving Slack with the /parly command, attachments included.
- Type in the thread to talk it over: it is saved in Parly as an internal note and never emailed.
- Get a direct message when a teammate mentions you, or assigns you a conversation in helpdesk mode.
- Snippet mode keeps full message bodies in Parly (EU), so only a preview lands in Slack.
Live chat on your site
Turn your website into a support channel.
Paste one snippet and a chat bubble appears on your site. Visitors get answers in real time: the AI assistant takes the first line and hands off to a human in the inbox or in Slack. Every chat becomes a Parly conversation, so it threads, notifies, and audits like email does, and the visitor still gets a reply by email if they leave.
- One script tag drops a chat bubble onto any site, no framework required.
- Answer live from the inbox or from Slack; the visitor sees replies instantly.
- An AI assistant handles the first line and escalates to a human when it should.
- Visitors can ask for a person at any time.
- It is just a conversation: threading, notifications, SLAs and the audit trail all apply.
Light by design
A help desk, without the help desk software.
Parly gives a small team the parts of a support tool that actually matter, and skips the weight that usually comes with them. It sits on the mailbox you already use, so there is nothing to migrate and nobody has to learn a new system.
- Status, per-user read state and who replied last
- Internal notes and @mentions
- First-response and resolution SLAs
- Tags, views and full-text search
- Reply from Slack, Teams or the app
- An audit trail on every action
- Customer portals and ticket forms to set up
- Per-agent licences that punish you for growing
- A migration off the mailbox you already use
- A system to administer and a vendor to learn
What you get
Small surface, serious control.
Who is on it, at a glance
The inbox shows who replied last and a live marker when a teammate is typing, so nothing is answered twice. Helpdesk mode adds assignment.
Answer from Slack or Teams
Reply to customer email from a Slack or Microsoft Teams thread as real email, start new emails with /parly in Slack, and keep the full thread and audit trail in Parly.
Restricted send
Limit a mailbox to an allowlist, enforced server-side on reply, reply-all, and forward; off-list sends are rejected.
Internal notes and mentions
Discuss a thread privately and @mention a teammate to pull them in; notes are never emailed to the customer.
SLAs and automations
First-response and resolution clocks per mailbox, plus rules that tag, route, notify, or assign in helpdesk mode.
AI assist
Summarise a thread, draft a reply, or suggest tags on demand; it never sends on its own.
Knowledge base
Import your support docs and AI assist answers from them and from tickets you already solved: steps for the agent, a draft for the customer.
How it works →Search, merge, split
Full-text search across messages, with merge and split that never lose history.
Views and snooze
Ready-made views like mentions me, waiting and breaching SLA (plus unassigned and mine in helpdesk mode), and snooze that wakes a conversation when it is due.
Forwarding rules
Mail meant for another desk goes straight on to them, before it reaches Slack, Teams or anyone's notifications, and can close itself here.
Everyone reads their own language
Parly translates a customer's email into each agent's language and can send the reply back in theirs, always marked as translated.
Notifications your way
In the app, as an email digest or a desktop push, set per mailbox and per kind of event, so nobody drowns in alerts.
See who else is on it
Parly shows who else has a conversation open and when someone is already replying, so two people never answer the same email.
Reports
Volume, SLA compliance, response and resolution times, and who carries the open work, per mailbox.
Ticket numbers and canned responses
Every conversation gets a number the team can search on, and the answers you type every day are one click away.
EU-hosted, tenant-isolated
Postgres in the EU, row-level security on every tenant table, and an audit log on every privileged action.
Send blocked. rival@competitor.com is not on this mailbox’s allowed recipients. Remove it to send.
Restricted send
A reply can’t reach the wrong inbox.
Limit a mailbox to an allowlist, enforced server-side on reply, reply-all, and forward. If one address is off the list the whole send is rejected, never silently trimmed, and nothing leaves until you fix it.
AI assist
Drafts the reply. Never sends it.
Summarise a long thread, draft a reply, or suggest tags, on demand. Every suggestion waits for a person, it never sends anything on its own.
Add the knowledge base and it answers from your own support docs and the tickets your team already solved.
Marta received a damaged jacket from order #4821 and is asking for a refund. No previous tickets.
So sorry about the damaged jacket, Marta. I have started your refund for order #4821, it will be back on your card in 3 to 5 days.
#4822 open Where is my shipment?
Programmable by design
Plug your own agents into the help desk.
Parly is an MCP server. Point the Claude API, Claude Code, or any MCP client at it with a scoped key and it can read, search, and reply to conversations, under the same send rules and audit trail as a person. Build your own triage, draft answers from your stack, or run support from the terminal.
- Connect any MCP client: the Claude connector, Claude Code, or your own agent.
- Company-owned keys, scoped to specific mailboxes and read-or-reply permissions.
- The same restricted-send and suppression rules apply to every automated reply.
- Rate-limited and fully audited: every call is logged.
- Or let a bot answer your chat widget and email, with a human safety net.
Why we built it
Parly started with a shared mailbox that had quietly become a mess. One password for the whole team, two people answering the same customer, no way to tell who had sent what. The honest fix was a help desk, but every one we looked at was a project to set up and a tax to run, far more tool than a small team answering email needs.
So we built the light version: individual logins, internal notes, and an audit trail on the addresses a whole team answers from, sitting on the mailbox we already used. And because we lived in Slack and Teams all day, we looked for a long time for a way to answer the shared mailbox from there and could not find it, so we built that too.
If a shared mailbox is slowing your team down, set up a workspace and connect it; the first month is free.
Parly · part of the Deuces family
Stop sharing a password. Start working together.
Set up your workspace and connect the mailbox you already have, in a minute. €19 per mailbox with unlimited teammates, instead of a price per agent. The first month is free.
FAQ
Questions we get, answered.
- How does Parly connect to our mail?
- You connect the mailbox you already have. For Microsoft 365 you sign in with Microsoft, so nobody shares a password with us. Any other mailbox, such as Gmail, TransIP or your hosting provider, connects over IMAP. Parly picks up new mail and sends replies from that same mailbox, so they land in its Sent folder and your mail hosting stays exactly as it is. It takes a minute, from the Mailboxes screen. For special cases, such as a separate address for each customer, Parly can also host addresses on your own domain; that takes some DNS work, so get in touch and we set it up with you.
- Can we reply to customer email from Slack?
- Yes, and it is one of the main reasons teams pick Parly. Connect Slack and a mailbox mirrors into a channel: each customer email becomes a thread, and pressing Reply on it sends your answer as real email from your address; what the team types in the thread itself is saved as an internal note. You can start a new email with the /parly command, attach files, leave internal notes and @mentions, and get a direct message when a conversation is assigned to you or mentions you. The full thread and audit trail stay in Parly, so nothing is lost when you answer from Slack.
- Does it work with Microsoft Teams?
- Yes. Your Teams admin adds the Parly app to your organisation once, from Parly's admin screen, and you link a mailbox to a channel with a one-time code. From then on each customer email shows up in the channel as a card, one thread per conversation. Press Reply to answer the customer by email from your own address, and anything the team types in the thread is saved in Parly as an internal note. Starting a new email and sending attachments from Teams are coming; the Slack integration has both today.
- How do you stop a reply going to the wrong recipient?
- Restricted send. A mailbox can be limited to an allowlist of designated recipients, enforced on the server at send time, on reply, reply-all, and forward. If any address is off the allowlist the whole send is rejected. We never silently strip a recipient, and suppressed addresses are dropped.