Concepts
Internal accounts
Distinguish workspace accounts from customers and understand the limits that still apply to internal exchanges.
Internal marks a Telegram person as one of the workspace’s own accounts, not a customer to approach. The system recognizes this when the person is linked to one of your accounts.
This is not a limit mode or a label that allows unrestricted sending. It keeps exchanges between your own accounts out of customer workflows.
How are Internal people different from customers?
| Mechanism | Customer | Internal |
|---|---|---|
| Customer stage | Can be managed | No customer stage |
| STOP | Checks matching direct private messages | Not checked |
| Automation rules for incoming messages | Can trigger | Skipped |
| Campaigns | Can participate if eligible | Do not run |
| Safety gate and limits | Apply | Still apply |
The link to a workspace account is the basis for identification. A tag you name “Internal” is not equivalent to this link.
Why do STOP and rules not run?
STOP records an external customer’s wish to stop receiving messages. Messages between your own accounts should not create such opt-out requests automatically.
When messages arrive, the system excludes Internal exchanges from the set used for customer processing. The rule runner also checks the link before executing. A message from an internal account may therefore appear in a conversation without producing the same effects as a customer message.
When testing automation, sending messages between two workspace accounts is not equivalent to a real customer messaging you. Rules not running in this case is not enough to conclude that the rule configuration is wrong.
Why do campaigns not run?
Campaigns check for Internal recipients and exclude them from customer execution flows, even if they are in your selected list.
If you cannot add someone to a nurture workflow, check whether they are linked to a workspace account. Changing the sending account does not skip this check.
Likewise, customer stage changes do not apply to Internal people. This is an audience classification, not a missing-permission error.
Checks that remain in place
When an account sends to an Internal account, the job still passes through the safety gate. The Telegram session, proxy, machine, pause state, safety state, and limits are still checked.
Actions are still recorded in the ledger and counted toward limits. A recipient not being a customer does not make the action exempt from limits.
If a job is waiting, read its actual hold reason. The Internal label does not release FLOOD_WAIT, restore a session, or bring a disconnected machine back online.