✔ Gather enquiries from every messaging app in one inbox
✔ Reply to customers from the CRM – in their own messaging app
✔ Share enquiries out among managers
✔ Keep the conversation history, even when an employee leaves
✔ Connect in minutes, with no developers needed
✔ Work with customers in five interface languages
The brief came from real life: small businesses’ customers write via WhatsApp, Telegram, Viber, e-mail and the website form, and managers reply from different phones – enquiries get lost and the history ends up scattered. I decided to build my own service that brings all of this together in one window.
I designed MyInboxify as a multi-tenant SaaS: each company signs up on its own and works in an isolated space. I wrote it in plain PHP with no framework so that it runs fast on ordinary hosting, and connected the official APIs – Meta’s WhatsApp Cloud API, the Telegram Bot API and Viber.
The result is a working product: a single enquiry inbox, two-way chat, a team of managers, statuses, contacts with duplicate detection, a mirror in a Telegram group, analytics, plans paid through Stripe and an interface in five languages. I built the service’s marketing website on WordPress.
A service where enquiries from every channel never get lost and the team replies from one window.
Messages from messaging apps, e-mail and the website become enquiries with a contact card
Managers write from the CRM, customers get the reply in WhatsApp, Telegram or Viber
Assignments, statuses, notes and an activity log – you can see who handles each enquiry
A separate topic in a supergroup for each enquiry; replies from Telegram reach the customer
Three plans, a free trial, monthly or yearly billing – no manual work
English, Russian, Ukrainian, French and German – the language can even be set in the URL
A service you can connect to in a few minutes and start using as a team straight away.
The service handles several key tasks:
Guaranteed reply within 24 hours.
The first call is free and with no commitment.
When customers write via WhatsApp, Telegram, Viber and e-mail all at once, a business doesn’t need yet another app – it needs one window for every conversation. Using my own product MyInboxify as an example, I explain what such a CRM is made of, the pitfalls of messaging app APIs and what a SaaS needs to have built in from day one.
MyInboxify is my own SaaS, a CRM for messaging apps. The idea is simple: a small company doesn’t need a heavy corporate system with dozens of modules – it needs to know that no customer message gets lost and that managers reply quickly. So all messages from the different channels land in one enquiry inbox, and working with them is designed to be learnt in a single evening.
I built the whole service: I worked out the structure and roles, wrote the back end, the dashboard interface, the integrations with the messaging apps and the payment system, as well as the marketing website with a blog and a help section. Sign-up is open, and the first 14 days are free.
Every incoming message automatically creates a contact card and an enquiry showing where it came from. Channels are connected in the settings, and step-by-step instructions are built right into the interface:
Managers reply from the enquiry card, and the customer receives the message wherever they wrote from – WhatsApp, Telegram, Viber or e-mail. Every outgoing message shows its author, time and delivery status. If a message isn’t delivered, the reason and a resend button appear next to it. New messages come in without reloading the page: the unread counter updates, the tab icon flashes and a short sound plays.
WhatsApp’s rule needed special handling: free-form text can only be sent within 24 hours of the customer’s last message. Once that window has closed, the service blocks normal sending and offers a choice of approved templates – so instead of hitting a confusing error, the manager immediately sees what to do.
The company owner signs up on their own and adds managers. Managers work in a shared inbox: they pick up enquiries, assign them, change statuses and leave internal notes. Each company sets up its own list of statuses to match its process, and the activity log shows who changed a status, replied or sent a template, and when.
Many teams are used to working in Telegram, so I built a mirror of enquiries in a supergroup with topics. Each enquiry gets its own topic with the customer card and “Take” and “Close” buttons. The customer’s messages from any channel are copied into the topic, and a manager’s reply sent straight from Telegram reaches the customer wherever they wrote from. Echo protection stops messages from going round in circles, and different companies’ data never mixes.
The service announces each new enquiry in the company’s Telegram chat, the assigned manager gets a personal notification, and enquiries left unanswered for more than three hours are collected into a reminder. The analytics show enquiries, closed deals and sources; the higher plans add manager workload, channels, UTM tags and statistics export to Excel and PDF.
I built payments right into the service: the three plans differ in the number of managers and the depth of the analytics, and customers can pay monthly or yearly at a discount. Subscriptions run through Stripe with a free trial, customers update their card and get receipts in the Stripe customer portal, and a plan change takes effect at the end of the paid period. The prices on the marketing website are pulled from the service’s admin panel, so they always match.
The interface is fully translated into English, Russian, Ukrainian, French and German. The language can be set right in the page URL – handy for ads aimed at different countries – and the login and sign-up pages have canonical and hreflang tags. For those who don’t want to set everything up themselves, there is a one-off onboarding service: customers pay for it on the website, and the order goes straight into the admin panel.
In a multi-tenant service, other people’s data is the biggest responsibility, so I built company isolation into every database query: one company can’t see another’s data, even by putting someone else’s record number into the page URL.
If you are planning a CRM for messaging apps, a WhatsApp Business API integration or your own customer service tool, the experience of MyInboxify suggests thinking through a few things from the very start:
I build web services and integrations tailored to the task – from a small “website form → Telegram” link to a full SaaS platform with payments and teamwork.
