Multigram
Everything you need to know about Multigram is here: how to use it day to day, from connecting your first number to mailings and channel posts. There's nothing to install: Multigram runs in the browser. If you're looking for something specific, use the search in the menu on the left.
The system in brief
Multigram brings your team's Telegram numbers together in one web panel. Managers reply to clients from the browser, and the manager can see the conversations on work numbers and step into a chat when needed.
You can upload clients from Excel, split them into segments and run a mailing. The system makes sure a number doesn't write to strangers too fast, because that's exactly what Telegram restricts accounts for.
For channels there are scheduled posts, sent as a bot or as a person. And roles, permissions and the action log help you see who does what in the system.
Key concepts
Two different logins
| What it is | Where | |
|---|---|---|
| Panel login | Email or Telegram @username + password. Gives access to the CRM. | Login page |
| Telegram connection | QR code or a code from Telegram. Gives the CRM access to the account itself. | “Accounts” → “Connect account” |
Account and bot
| Telegram account | Bot | |
|---|---|---|
| What it is | A regular number of a person or company | A bot created in @BotFather |
| How to connect | QR code or number + code | Token from @BotFather |
| What it's for | Client chats, mailings, posts as a person | Posts to channels and groups, buttons under a post |
Business and personal accounts
BUSINESS This is the company's work number. Managers with oversight permission can see its conversations and reply on its behalf, and the system records exactly who did it. Such a number can be handed over to another employee.
🔒 PERSONAL This is a person's own number. Only they can see its conversations, and no role changes that. Colleagues can't use such a number for their own mailings or posts.
The number type is chosen once, when connecting, and doesn't change afterwards. A person connects a personal number themselves, after logging in to the panel with their own login.
First steps
In the panel, the “Help” section has a “First steps” checklist. You don't need to tick it off by hand: as soon as you do something, the checkmark appears on its own. The order is:
- Connect your Telegram account. Without it there are no chats, contacts or mailings. See Connecting an account.
- Add people to the team. Invite by @username: the person sets their own password. See Add a person.
- For posts, connect a bot and a channel. The bot must be a channel admin with permission to post. See Bots and channels.
- Upload contacts. Excel/CSV with a “Phone” column. See Contacts and import.
- Launch your first mailing. See Campaigns.
- Create your first post. See Posts.
Next to the title of each panel section there's a “?” button: it opens instructions for that exact screen.
Roles and permissions
Everyone has a base role: OWNER, ADMIN or MANAGER. The owner can create a custom role with any set of permissions; it replaces the base role's permissions. The exception is the “Users”, “Invitations” and “Limits” sections: only OWNER and ADMIN get in there, even if a manager's custom role includes the matching permission.
| Permission | Owner | Admin | Manager |
|---|---|---|---|
| Contacts: view and edit | ✓ | ✓ | own |
| Campaigns: create and launch | ✓ | ✓ | own |
| Segments: create | ✓ | ✓ | — |
| Oversight of the team's business accounts | ✓ | ✓ | — |
| Write on behalf of someone else's business account | ✓ | ✓ | — |
| Connect accounts for others | ✓ | ✓ | — |
| Colleagues' bots and channels | ✓ | ✓ | own only |
| Users: invite, deactivate, reset password | ✓ | managers only | — |
| Sending limits | ✓ | ✓ | — |
| Audit log | ✓ | ✓ | — |
| Custom roles | ✓ | — | — |
Create a custom role
- “Users” → “⚙ Manage roles” (owner only).
- Set a name and tick the permissions. For example, “Supervisor” — oversight only, no right to write.
- Assign the role in the “Custom role” column or in the person's card → “Access permissions”.
Protection against privilege escalation: a person can't grant others permissions they don't have themselves, and only the owner manages admins.
Add a person to the team
Method 1. Invite by Telegram @username (recommended)
- “Users” → “✈ Invite by @username”.
- Enter the person's username: with @ or as a
t.me/usernamelink. - Choose a base role. Only the owner can choose ADMIN.
- Choose the connected account that will send the message with the link, or “Don't send — I'll just copy the link”.
- The person opens the link, enters a name and password (email is optional) and lands in the panel right away.
The link is valid for 7 days. You can resend it no more than once every 30 seconds; “New link” invalidates the old one.
If the person hasn't messaged your number before, Telegram may hide the message in “Message requests”. Warn them to check there. One more thing: if the person who sent the invitation is deactivated or has their permissions reduced, all of their invitations stop working.
Method 2. Create with email and password
- “Users” → “+ Create with email and password”.
- Name, email, temporary password (at least 8 characters), role.
- Give the login and password to the person in person. On first login the panel will ask them to set their own password.
Profile and passwords
A person's card opens when you click their name in “Users”, and your own profile when you click your name at the bottom of the side menu. In the card you can change the name, Telegram @username and email (at least one login must remain), the base and custom role, and deactivate or activate the person.
Your own password
“My profile” → “Change password”: current one and the new one twice. Your other sessions (another browser, phone) will end.
A manager's password
Person's card → “Reset password” → “Generate” → “Set”. The password is copied automatically; give it to the person in person. They are signed out of all sessions, and at their next login they must set their own password: the temporary password only gives access to that screen.
If the person has a personal Telegram account, a password reset disconnects it (the session also ends in Telegram itself) and wipes the cache of its chats. That way, whoever knows the new password can't see private conversations. The person will reconnect the number.
Login protection
After 8 failed attempts for one login from one IP address, 30 attempts for a login from any addresses, or 100 attempts from one address across different logins, login is blocked for 15 minutes. Every login, failed attempt and block is recorded in the audit log.
Connecting a Telegram account
- “Accounts” → “+ Connect account”.
- Who it's for — appears if you have permission to connect accounts for others.
- Account name for yourself, for example “Sales — Maria”.
- Whose number this is: the company's business account or a personal one.
- Sign-in method: QR code or phone number + code.
- QR: in Telegram on your phone go to Settings → Devices → Link Desktop Device and point the camera. The code refreshes itself every ~30 s.
Number: enter +380…, click “Get code” and enter the code. It usually arrives in the Telegram app (the “Telegram” chat), not by SMS. - Cloud password, if two-step verification is on. This is your Telegram password, not your CRM password.
- “✓ Account connected”. In a minute or two, dialogs will appear in “Chats”.
The Telegram login code is entered only in the panel. Don't forward it to anyone, even a colleague in a chat: Telegram notices such forwarding and may block the login.
The session is stored in the service only in encrypted form. A new device will appear in “Devices” on your phone; if you end it there, the account is disconnected in the CRM.
Hand an account over to another person
“Accounts” → “Owner” column → choose a person. Works only for business accounts, and you don't need to reconnect Telegram. The number's chats go with it; contacts imported by the previous manager stay assigned to them.
Disconnect a number
“Accounts” → “Disconnect”. The session also ends in Telegram itself, and the number's chat cache in the panel is wiped. Mailings from the number will stop. The number's owner can disconnect it, and for a business number, so can anyone with permission to manage accounts. You can connect the number again at any time with the “Connect →” button.
Account statuses and tiers
| Status | What it means | What to do |
|---|---|---|
| CONNECTED | Working | — |
| LOGIN REQUIRED | Account created, login not finished | “Connect →” |
| DISCONNECTED / ERROR | Session ended, for example on the phone | Reconnect |
| FLOOD_WAIT | Telegram asked for a pause | Nothing — the account will come back on its own |
| RESTRICTED | Telegram restricted writing to strangers (PEER_FLOOD), for 3 days. In the API — RESTRICTED_STRANGERS | Lower the new-dialog limits |
| PERMA_RISK | 3+ restrictions: the account is excluded from auto mailings | Check manually, reduce the load |
Tier and warm-up
The tier (NEW, REGULAR, OLD, PREMIUM) determines the sending limits. For the first 21 days after connecting, an account always works as NEW, whatever tier you set.
To change the tier: “Accounts” → “Tier” column (you need permission to manage limits). Rule of thumb: REGULAR — the account is a few months old and already sends messages; OLD — a year or more; PREMIUM — with a Telegram Premium subscription.
Chats, oversight and media
Chats
- At the top there's a switcher: “All accounts” or a specific account.
- Dialogs sync automatically every 30 seconds; ↻ refreshes manually (no more than once a minute).
- Enter sends, Shift+Enter adds a new line.
- Message history is stored for business accounts: the last 100 messages per chat per sync.
Media
Photos open full screen, videos and GIFs with the ▶ button, voice messages and audio have a player, and files download on click. Files over 25 MB are available only in Telegram. Media cache that hasn't been opened for 7 days is deleted automatically.
Oversight
For the owner and admins: “manager — account” cards with recent chats. You can open the conversations of a manager's business account and reply on their behalf.
The client will see the message from the manager's number, and your name will go into the action log. Before sending from someone else's number, the panel asks whether you're sure.
Contacts and import
Add a contact
“Contacts” → “+ Add contact”: first name, last name, @username (without @) and/or phone in the format +380…. At least a username or a phone is required. Optionally, specify the account to use when writing to this contact.
Status
The “Status” column in the table: New, Active, Inactive, VIP, Lost. A change is saved immediately; the status is used in segments.
Import from a file
Formats .xlsx, .xls, .csv, up to 20 MB and up to 10,000 rows.
| Column | Name in the file | |
|---|---|---|
| Phone | Phone or phone | required |
| First name | First name or first_name | optional |
| Last name | Last name or last_name | optional |
Contacts are added to the account's Telegram contacts in batches of 20 with pauses. The account's daily import limit applies: whatever doesn't fit is marked “Skipped: daily import limit” — repeat the next day. Only one import runs per account at a time. Import history is available in the section.
Segments
A segment is a saved set of selection conditions. The list of people in it isn't fixed: every time you launch a mailing, the system searches again for contacts that match the conditions. While you set up a segment, you can see next to it how many people match.
| Field | Operators |
|---|---|
| Last activity, Last message, Date added | older than N days, newer than N days, empty |
| Status | equals, does not equal |
| Manager, Account, On Telegram, Had a dialog | equals |
| First name, Last name, @username, Phone | contains, equals, empty, filled |
Conditions are combined with AND / OR (up to 50 conditions). Example: “Had a dialog = yes” AND “Last activity older than 30 days” → clients who haven't written in a while.
Campaigns (mailings)
A campaign is one message that needs to be sent to a group of people. It's sent by your team's connected numbers.
Audience
- Segment or All clients — the list is determined at the moment of launch.
- Selected contacts — fixed when you create or schedule it.
- Several managers — tick the people, and their clients will be messaged; duplicates by phone are removed. The sender is an account available to you: your own or a colleague's business account.
Modes
| Mode | How it works |
|---|---|
| Automatic | Messages are queued and sent within the limits. Each contact is messaged by the account they were added through, or by their manager's first connected account. |
| Manual | A list of recipients opens. Next to each: “Send” (the CRM sends it itself), “Open chat” + “I sent it myself” (write from your phone and mark it) or “Skip”. |
| Scheduled launch | Not a separate mode but an option for both: “⏰ Schedule…” for a date and time (up to 90 days ahead). You can “Launch now”, “Change time” or “Cancel schedule”. |
Controls and statuses
“Pause”, “Resume”, “Stop”. The campaign card has counters: sent, errors, in FloodWait, queued — updated live. In manual mode, failed messages (FAILED) can be sent again, even when the campaign has already finished; in automatic mode, the system retries temporary failures itself up to 5 times. A campaign becomes COMPLETED when no recipients are left pending, and ERROR (with an explanation) if the launch failed. Limits: up to 10,000 selected contacts and text up to 4,096 characters.
Pace and strangers
Telegram watches most closely how you write to strangers, meaning people the number hasn't chatted with yet. That's why a daily quota applies to them. When it runs out, the remaining messages wait until tomorrow. A new number sends roughly one message every 1.2 seconds. If Telegram asks for a pause (FloodWait), the number waits and then continues on its own.
Limits and warm-up
Limits exist so that Telegram doesn't restrict your numbers. They're set at three levels: shared for everyone (by tier) → your company → an individual number. The closer to the number, the higher the priority: a number's settings outweigh the company's settings.
| Field | NEW | REGULAR | OLD | PREMIUM |
|---|---|---|---|---|
| New dialogs / day (@username) | 10 | 20 | 30 | 50 |
| New dialogs / day (by number) | 7 | 10 | 15 | 20 |
| Contact import / day | 15 | 20 | 40 | 50 |
| Messages / min to one chat | 20 | 25 | 30 | 35 |
| Messages / s to different people | 0,83 | 0,91 | 0,91 | 1 |
Warm-up
For the first N days after connecting (14 by default), the daily quotas for new dialogs and import grow linearly from a starting value to the full one. Separately, the “first 21 days — NEW” rule applies: until then the number works with NEW limits, whatever tier it's assigned. Warm-up can be turned off with a checkbox for the company or an individual number, but we don't recommend it for new numbers. The account's statistics show whether warm-up is active and which limits are currently effective.
Aggressive mode
The switch in the tier row raises the daily limit of new dialogs by @username to a level that usually still passes without consequences, and turns off warm-up. The risk of a restriction (PEER_FLOOD) is noticeably higher, so turn this mode on only when you understand why you need it.
The shared limits by tier are the same for all companies and are set by the Multigram team. In your panel this tab opens for viewing only, while you change your company's and individual numbers' limits yourself.
Bots and channels
Posts to a channel are usually published by a bot. For this to work, you need to create a bot, get its token and make the bot a channel admin. It takes about five minutes.
- Token. In Telegram open @BotFather →
/newbot→ name and username → copy the token. - Connect the bot. “Channels” → “Connect bot” → paste the token and choose which of your numbers to link it to. A token is like a password: don't forward it to anyone.
- Make the bot an admin. In the channel: Manage → Administrators → add the bot with the “Post messages” permission.
- Add the channel. “Channels” → “Add channel” → the channel's @username or numeric id (for a private channel it starts with -100).
Without a bot: as an account
“Channels” → accounts section → choose your connected account and specify the channel or supergroup. The account must be a channel admin with permission to post (or a group member with permission to write). Buttons under a post aren't available in this mode — that's a bot-only feature.
If it doesn't work
| Message | Cause and fix |
|---|---|
| “The bot hasn't been added as an admin yet…” | The bot was added as a member, not an admin — do step 3 |
| «chat not found» | Typo in the @username or id; for a private channel you need the id starting with -100 |
| “posting permission not confirmed” | Enable “Post messages” for the bot and click “Refresh status” |
| Bot INVALID_TOKEN | The token was revoked — disconnect the bot and connect it again with a new token |
Posts
“Posts” → “+ New post”: choose a channel, write the text (bold, italic, links, monospace — select the text and click the button), add media and buttons, then “Publish now”, “Schedule” (up to a year ahead) or “Save draft”. There's a “Silent” option.
Telegram rules
| Limit | |
|---|---|
| Text without media | up to 4,096 characters |
| Caption for a photo/video/file | up to 1,024 characters |
| Photo | up to 10 MB (more — tick “as file”) |
| Video, audio, documents | up to 50 MB |
| Album | 2–10 files; photos can be mixed with videos, documents and audio only among themselves |
| Buttons | not shown under an album; unavailable in posts from an account |
Statuses
| Draft | Saved, won't go anywhere |
| Scheduled | Will go out at the set time (checked every 30 s) |
| Sending… | On its way to Telegram, can't be edited |
| Sent | In the channel; for a public channel there's “Open in Telegram” |
| Error | The reason is in the post's row. Fix it and “Publish now” |
Security
You give the service access to work numbers and your client base, so we reviewed the code against OWASP Top 10 2021, OWASP API Security Top 10 2023 and the main ASVS 4.0 requirements, and fixed all critical and serious findings. Here's how your data is protected now:
- A separate space for each company. Employees of other companies can't see your contacts, chats or mailings.
- Passwords. Stored only as a bcrypt hash. After a password change all old sessions end, and a temporary password from a manager must be changed on first login.
- Brute-force protection. After a series of failed attempts login is blocked for 15 minutes, and every attempt goes into the action log.
- Telegram sessions. Stored only encrypted (AES-256-GCM).
- Privacy. Personal conversations are visible only to the number's owner. The text of messages from personal numbers isn't recorded, not even in the action log.
- Browser protection. HTTPS only, a strict content security policy (CSP), and the panel can't be embedded on someone else's site.
- Files. The type of every uploaded file is checked by its content, not by its name.
REST API
The API lets you integrate Multigram with your systems. The base URL is https://<service address>/api, the format is JSON. Authorization is the header Authorization: Bearer <accessToken>, and the token is issued by POST /api/auth/login. Permissions are checked the same way as in the panel.
curl -X POST https://<service address>/api/auth/login \ -H 'Content-Type: application/json' \ -d '{"login":"owner@company.com","password":"…"}' # → { "accessToken": "…", "user": { … } }
In the login field you can pass an email or a Telegram @username. There are no separate API keys yet: an integration signs in under an employee's account, and the token is valid for a limited time (usually 8 hours), after which you need to sign in again.
Campaign progress is streamed in real time over Socket.IO (namespace /realtime) at the same address; the token goes in handshake.auth.token.
Main endpoints
| Method | Path | Description |
|---|---|---|
| POST | /auth/login | Log in, get a token |
| GET | /users | List of the organization's people |
| GET | /users/me/permissions | My permissions |
| POST | /users | Create a person |
| PATCH | /users/:id | Edit profile |
| POST | /users/:id/password | Change or reset a password |
| GET | /roles, /roles/catalog | Custom roles and the permission catalog |
| POST | /invites | Create an invitation |
| GET | /telegram/accounts | Accounts |
| POST | /telegram/accounts | Create an account record |
| POST | /telegram/accounts/:id/login/qr | Start QR login |
| POST | /telegram/accounts/:id/login/phone | Start login by number |
| PATCH | /telegram/accounts/:id/owner | Hand over an account |
| PATCH | /telegram/accounts/:id/tier | Change tier |
| GET | /chats | Dialogs |
| GET | /chats/:chatId/messages | Chat messages |
| POST | /chats/:chatId/send | Send a message |
| GET | /contacts | Contacts |
| POST | /contacts | Add a contact |
| POST | /contacts/import | File import (multipart) |
| GET | /contacts/imports | Import history |
| POST | /segments/preview | Count contacts by conditions |
| POST | /segments | Save a segment |
| POST | /campaigns | Create a campaign |
| POST | /campaigns/:id/start | Launch |
| POST | /campaigns/:id/schedule | Schedule |
| POST | /campaigns/:id/pause · /resume · /stop | Control |
| GET | /campaigns/:id/recipients | Recipients |
| POST | /campaigns/:id/recipients/:rid/send | Send to a recipient (manual mode) |
| GET | /limits | Organization limits |
| POST | /limits/organization · /limits/account | Change limits |
| GET | /bots · /channels | Bots and channels |
| POST | /channels/via-account | Channel for posts from an account |
| POST | /media/uploads | Upload a file for a post |
| POST | /posts | Create a post |
| POST | /posts/:id/publish-now | Publish now |
| GET | /audit | Audit log |
| GET | /telegram/accounts/:id/stats | Account statistics and effective limits |
Request bodies are validated strictly: unknown fields are rejected with a 400 error. Rate limits return 429.
Errors and fixes
| Message | What to do |
|---|---|
| “API unavailable” | The service is temporarily unavailable. Wait a minute and refresh the page |
| “Session expired — sign in again” | The login time ran out or the password was changed — sign in again |
| “Too many failed login attempts” | Wait 15 minutes. Resetting the password doesn't lift the block |
| “No MANAGE_… permission” | The message says which permission is missing. Ask the owner to add it to your role |
| “Account not connected” | “Accounts” → “Connect →” |
| FloodWait / “Telegram asks for a pause” | Nothing — the account will continue on its own after the timer |
| “Skipped: the account's daily import limit (N) is exhausted” | Repeat the import tomorrow or carefully raise the limit. Re-uploading the same numbers counts too |
| “The bot doesn't have permission to post in this channel” | Give the bot its admin rights back with permission to post and click “Refresh status” in “Channels” |
| “Bot inactive — check the token” | The token was revoked or changed. Get a new one from @BotFather and connect the bot again |
| “Unclosed tag…” / “Tag … isn't supported” | Remove the formatting at the problem spot and save again |
| “Invitation has expired” / “Invitation already used” | Ask for a new invitation to be sent |
Telegram and security restrictions
- Buttons under a post work only in posts from a bot.
- For the first 21 days an account works as NEW, whatever tier you set.
- A colleague's personal Telegram can't be used for mailings, posts or viewing conversations.
- Resetting the password of a person with a personal Telegram disconnects their personal accounts.
- Old regular groups (not supergroups) and
t.me/+…invite links aren't supported for posts from an account. - A campaign can be scheduled no further than 90 days ahead, a post no further than a year ahead.
- Limits reduce the risk of restrictions but don't override Telegram's rules: the company is responsible for the content and recipients of its mailings.
Glossary
| Business account | A company number: managers see the conversations and can reply on its behalf |
| Personal account | A person's private number: only they see the conversations |
| Tier | NEW / REGULAR / OLD / PREMIUM — the account's “age and status”, which the limits depend on |
| Warm-up | Gradual growth of a new account's limits |
| Stranger | A contact you haven't had a dialog with yet |
| FloodWait | Telegram asked for a pause of N seconds; not a ban |
| PEER_FLOOD / RESTRICTED | Telegram temporarily banned the account from writing to strangers |
| Segment | A saved contact filter |
| Campaign | A mailing of one message to a group of contacts |
| Bot | A Telegram bot from @BotFather for posting to channels |
| Album | 2–10 photos/videos in one post |
| Audit log | Who changed or sent what in the CRM, and when |