Buyers, sellers and your own team all send through one platform. Keep each of them in check.
Email for buyers, sellers and your team, with AI abuse flags and per-seller limits
User-to-user messages can be abused
Limits, suppression and abuse controls stop misuse of relayed mail.
Sellers expect their own branding
Verified sender domains and templates per workspace.
Support needs to trace any message
Searchable logs by recipient, subject or ID.
Notify sellers in real time about new orders, on a priority stream, and use delivery events to alert your team when a seller never receives one.
Confirm purchases to buyers at once, kept apart from user-generated messages so a content problem cannot delay core transaction mail. Delivery events confirm the buyer was informed.
Relay conversations through platform addresses so personal emails stay hidden, replies come back by inbound routing, and limits curb unsolicited volume. Abuse reports go to your team.
Send settlement and payout updates to sellers with an audit-friendly record, and give support a searchable log of what each seller was told. Disputes can be checked quickly.
Scan relayed user messages for spam, phishing links or off-platform solicitation and hold suspicious ones. Trust and safety staff review the queue and decide to release or block.
Group complaints and bounces by seller to show who is driving reputation risk, with a plain-language summary. Your team chooses whether to contact, limit or suspend.
Ask for the email history of an order or user in natural language and get the matching log entries. The tool is read-only and does not resend or edit anything.
Approved agents can check seller domain status or message state via an MCP-compatible API, with scoped keys and a human approval step for sensitive actions.
AI features are assistive and advisory, so your trust and safety and support teams review flags and keep control of seller and message decisions. [Confirm which AI features are available at launch.]
Route conversations through platform addresses so personal emails stay private and you keep a record of the exchange.
Start new sellers on modest caps and raise them with good history, so a single account cannot damage shared reputation.
Break down bounce and complaint rates per seller and act early on outliers, before providers notice the pattern.
Strip or rewrite risky links and attachments in relayed messages, and add a clear report-abuse link to every relay.
Only allow branded sending after DNS checks pass, and fall back to a platform address for sellers who do not verify.
Generate a unique platform reply-to address per conversation, send each message from your domain and receive replies through inbound routing. The platform forwards the reply to the other party, keeping real addresses private and logging the exchange. Expire addresses when conversations close.
Apply per-user and per-seller rate limits, screen relayed content, suppress addresses that complain, and provide a report-abuse link. Review outliers regularly and escalate repeat offenders according to your platform policy. Publish clear acceptable-use rules so enforcement is consistent and defensible when sellers dispute it.
Yes, if they verify their own sending domain with SPF and DKIM. Sellers who do not verify can send through a shared platform address with their name in the display. Unverified sellers keep a safe, working fallback sender. [Confirm per-workspace domain support.]
No. Keep order and payout notices on a protected stream and relayed user messages on another. Content written by users carries more risk, and separation stops an abuse issue from delaying core transaction mail. Treat each stream as a separate reputation.
Search the message log by recipient, subject or message ID to see accepted, deferred, bounced or delivered status with timestamps. Webhooks can also surface status inside your own support tools. Keep message IDs in your own order records so support can link them quickly. [Confirm log retention period.]
Use per-seller limits, suppress complaining recipients quickly, and track complaint rates by seller. Isolate high-volume or risky sellers on a separate pool if needed, and keep clear policies for warnings and suspension. Document the warning and suspension steps so decisions are consistent.
AI can score relayed messages for spam, phishing and solicitation patterns and hold suspicious ones for review. It does not decide alone: your trust and safety team approves release or blocking. Reviewers see why each message was held. [Confirm which AI features are available at launch.]
A copilot can find and summarise the email history for an order or user from the logs in plain language. It is read-only, and staff decide any action. Results link back to log entries. [Confirm which AI features are available at launch.]
[Add a customer quote or result from a marketplace customer]
[Name, title, company]Tell us about your volume and setup and we will walk you through the right configuration.
Create an account, add your domain and send your first email.