Agencies and communities

Each client's accounts stay separate while your team works from one panel

Connect your clients' numbers, groups and channels. Every team member sees only the brands they are responsible for, and a leaver's access ends in one step.

The agency problem is access, not account count

An agency with ten clients has ten numbers, about as many channels and usually a drawer of spare phones. The accounts are logged in on staff members' own devices. When someone leaves you have to end sessions one by one, change passwords and tell the client. Half of that list tends to get skipped.

The second problem is visibility. A community manager answers a member in the evening, the morning shift does not know, and the same question gets a second, slightly different answer. When the client asks at the end of the month how quickly you reply, all you have is a guess.

MyCRM was built for these two problems. Today it works with Telegram: personal numbers, groups, channels and bots. WhatsApp is in development and coming soon, with Instagram after that.

How MyCRM organises agency work

Per-client number access: for each number you decide who can write and who can only read. Someone working on brand A does not even see brand B's chats in the list. See team permissions for the full set of rules.
Offboarding without password changes: a number is connected to the panel once and people sign in with their own panel accounts. Nobody is handed a Telegram password or login code. Disable a leaver's panel account and their access to every client account ends at the same moment.
One inbox: chats from all numbers land in a shared inbox. Each chat has an assignee, and internal notes sit next to the conversation without the customer seeing them.
Protecting end-user data: hide members' phone numbers from staff, restrict message deletion, or limit a person to the chats assigned to them.
Scheduled posting to channels and groups: prepare a post for the brand's channels and groups in advance, or send it to several destinations at once.
Labels, stages and custom fields: mark chats by campaign, request type or segment and follow partnership and sales conversations on a kanban board.

What you need and where it lives

Need	Where in the panel
Assign a person to one brand's numbers only	Team → member details
Hide customer phones, restrict deletion	Team → number permissions
See chats still waiting for a reply	Reports
First response time per number and per agent	Reports
Who did what, and when	Audit log
Scheduled posts to channels	Broadcasts
Track complaints and technical issues	Tickets

Reporting to a client

Because each brand is connected through its own numbers, you can read the reports number by number. Messaging analytics shows first response time per agent and per number, lists chats that are waiting, and draws an hour heatmap of when messages arrive. Export the data as CSV and drop it into your own report template.

One limit, stated plainly: there is no ready-made, client-branded report page. The numbers come from Reports and the CSV file; the presentation is yours. Channel subscriber statistics are not shown either.

A community manager's day

In the morning she opens the list of chats waiting for a reply. A note left by the night shift says a member asked about a prize delivery and the brand still owes an answer. She sets a reminder on that chat for the afternoon.

Before lunch she works through common questions with saved replies and opens tickets, each with a priority and a resolution target, for members who reported a problem. At the end of the day she schedules tomorrow's announcement to the brand's channel and two groups. At no point does she need the brand's phone or password.

To try it, create an account and connect a first number. Everything on the Telegram side is described at telegram.mycrm.sh.

FAQ

Do I need to know my client's Telegram password? No. A number is connected once, with the client's approval, by phone code or QR. After that the team works through panel accounts. Session keys are stored encrypted with AES-256-GCM.

Can one client see another client's chats? People see only the numbers you grant them. You can add a contact from the client side as a read-only member on their own numbers; they will not see any other brand.

Do you store message history? No. Message history is not kept in our database; it is read live from Telegram. The panel holds CRM data only: assignee, stage, labels, notes and the event records needed for reports.

Can I connect WhatsApp and Instagram accounts too? Not today. Only Telegram is live. WhatsApp is coming soon and Instagram follows it. We would rather say that than describe something unfinished as available.