One inbox. Every conversation.
A shared workspace for web chat, email, and Telegram, with ticket assignments, team roles, and real-time updates.
Inbox · Team workflowsA little farewell.
A lot to take forward.
on to the next chapter ↗I built Talki around a simple idea: customer support should feel connected. Conversations, customer context, and the tools to help should live in one place.
From March to September 2026, I worked on bringing that idea to life — from the chat widget and shared inbox to AI assistance, integrations, and the details that make a product feel complete.
My work on Talki has come to an end. The project is no longer maintained and the backend is offline. I’m keeping this website, the design, and the documentation here as a record of what I built.
Thank you to everyone who took a look, tried it out, or followed along. This page closes one chapter and leaves the door open for the next.
Here’s what I’m looking for nextThe pieces that made up Talki.
Preserved here as a product case study.
A shared workspace for web chat, email, and Telegram, with ticket assignments, team roles, and real-time updates.
Inbox · Team workflowsA knowledge base built from website content, automated replies, and conversation summaries to help agents pick up where AI left off.
Knowledge base · AI assistanceAn embeddable chat widget with custom branding, mobile layouts, file attachments, GIFs, and message read receipts.
Embeddable SDK · Chat UIDeepL integration for incoming messages and agent replies, bringing translation directly into the conversation.
Translation · Agent experienceBackend Connect brought plan details, orders, and custom customer data into tickets through signed webhook integrations.
Integrations · Customer dataOnboarding, workspace settings, billing interfaces, analytics, documentation, and a public website to tie the experience together.
Product engineering · End to endThis is an archive. Sign-in, live chat, and subscriptions are no longer available. The original website and documentation remain open to explore.
I’m looking for my next role as a Full-stack Product Engineer — working across the interface, backend, and product decisions that connect them.
If that sounds like someone your team needs, I’d love to talk.
Connect with me on LinkedIn
Open toFull-stack Product Engineer