Everything has a place.
Separate inboxes for different teams and accounts. Filter conversations by owner, status, or label to find the work that needs you.
Your conversations, together in one calm workspace. Give every message an owner, every teammate the context, and every customer a thoughtful reply.
Built for teams. Designed for focus.
Can I update my delivery address?
EmailAre you open this Saturday?
MessengerThat’s everything I needed.
EmailKeep the small details that make good support feel personal.
Separate inboxes for different teams and accounts. Filter conversations by owner, status, or label to find the work that needs you.
Assign a teammate, leave a private note, and keep the conversation’s context together. Bring new members in with an invitation link.
Keep drafts, reuse saved replies, and snooze conversations until the right time. Live updates keep your workspace in step with your team.
Start with the inboxes your team already uses. Keep ownership, notes, and follow-up in the same workspace.
Configure your inboxesGmail, Outlook, and IMAP or POP with SMTP.
Bring Facebook Page conversations to your team.
WhatsApp outreach and AI-assisted phone campaigns.
Chatalay is in early access. Connected-channel pilots need provider setup and live validation.
Customer conversations deserve your attention. The software around them should make that easier.
Chatalay focuses on readable screens, straightforward workflows, and a small self-hosted deployment. Your team gets a workspace built around the work.
Teams that share responsibility for customer conversations: support, sales, and community operations. Separate inboxes and explicit member access help each team find its place.
This site links to an existing workspace. Ask your workspace administrator for an invitation. Public self-service signup is not available yet.
Yes. Chatalay is designed for a single-server Docker Compose deployment with PostgreSQL and durable file storage. Your operator manages hosting, backups, and provider credentials.
These workflows are in development. They require provider connections, recipient permission, and a controlled live pilot before real outreach. They are not enabled by default.