Reply to email from Slack
Shared inboxes,
handled together.
The shared mailbox your whole team answers from, info@, support@, sales@, turned into a real workspace: who is handling what, who already replied, nothing answered twice. Answer it all from Slack.
Workspaces set up by hand while we are in beta.
- Marta OlsenOpen9:41Refund for order #4821 · Hi, the second jacket arrived damaged so I would like to
- 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
Point Parly at an existing address over IMAP and SMTP, or run a dedicated one through our relay on your own domain or a subdomain. info@ keeps working. No migration, no change to your mail hosting.
Using your own domainGrant 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
Assign, leave internal notes, set status, 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.
Assign a teammate, set a status, add a tag, so the inbox shows who owns what and nothing is answered twice. Leave an internal note and @mention a colleague to pull them in; notes are never emailed to the customer.
Answer email from Slack
Run the help desk where your team already is.
Parly mirrors a mailbox into a Slack channel: a customer email arrives as a thread, and the reply you write there goes out as real email from your address. No new tab, no forwarding, and the full conversation and audit trail still live in Parly.
- Reply to a customer email right in the Slack thread. Parly sends it as real email from your address.
- Start a new email without leaving Slack with the /parly command, attachments included.
- Assign, set status, leave internal notes and @mention a teammate, all from the thread.
- Get a direct message when a conversation is assigned to you or mentions you.
- Snippet mode keeps full message bodies in Parly (EU), so only a preview lands in Slack.
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.
- Assignment, status and per-user read state
- Internal notes and @mentions
- First-response and resolution SLAs
- Tags, saved views and full-text search
- Reply from Slack, or from 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.
Assignment, not guesswork
Assign a teammate and set status, so the inbox shows who owns what and nothing is answered twice.
Answer from Slack
Reply to customer email from a Slack thread as real email, start emails with /parly, 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 auto-assign, tag, route, or notify.
AI assist
Summarise a thread, draft a reply, or suggest tags on demand; it never sends on its own.
Search, merge, split
Full-text search across messages, with merge and split that never lose history.
Saved views and snooze
Named queues like unassigned, mine, or breaching SLA, plus snooze that wakes a conversation when it is due.
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.
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.
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, assignment, 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 all day, we made it answer email from there too, without leaving the channel.
It is in private beta because we want it right before we charge for it. If a shared mailbox is slowing your team down, ask for a workspace.
Parly · part of the Blake family
Stop sharing a password. Start handling together.
Ask for a workspace. If Parly fits how your team uses a shared mailbox, we will set it up and send you the link.
FAQ
Questions we get, answered.
- How does Parly connect to our mail?
- Two ways. Connect an existing mailbox over IMAP and SMTP, so info@ or support@ keeps working exactly as it does today, just with Parly on top. Or run a dedicated address through our relay, on your own domain or a subdomain (for example support.yourcompany.com), with SPF and DKIM so every reply is fully authenticated and your main domain's reputation stays separate. Either way we do not replace your mail hosting and we do not become your MX of record unless you choose inbound parse.
- 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 a reply you write in that thread is sent as real email from your address. 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.
- 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.
- Is Parly EU-hosted?
- Yes. Postgres in the EU (Ireland), row-level security scoping every tenant table, and an audit log on every privileged action. Secrets are encrypted at rest and never exposed to the browser.