On 3 August 2026 Telegram disappeared from the App Store. Not in a single country, but worldwide. It came back within hours, so for most users the whole thing passed unnoticed. For companies that have built customer contact on a messenger, however, this is a good moment for one specific question: what actually happened, and what only appeared to have happened.
What actually happened
Apple pulled the app from the store after a review found content in it that breached App Store rules. Telegram removed the reported material and blocked the account that had posted it, and the app returned to the store the same day. The Mac version and the Android version were not affected by the removal.
This was not the first such case. In 2018 Apple likewise took Telegram off the store for several days over content, and likewise restored it after changes on the app's side.
What did not happen, despite how it was described
This is worth saying plainly, because many comments claimed that companies had „lost their channel of contact with customers". That did not happen, and it matters for a sober assessment of the risk.
Apps already installed worked normally. Chats did not close, messages went through, calls worked. Removal from the store does not delete the app from phones that already have it.
Something else stopped working – less visible, but more painful inside a company:
- A new employee cannot join the channel. Someone starting work on the day of such a block cannot install the app on a company iPhone. There is no way to plug them into customer service.
- Replacing a phone cuts you off from the channel. A lost, broken or replaced company phone means the app cannot be installed again until it returns to the store.
- Restoring from a backup will not work. Restoring a device downloads apps from the store. If the app is not there, the backup will not bring it back.
None of this sounds dramatic until it happens in a company whose customer service rests on a single messenger. Then it is simply a day on which nobody new can be added to the service channel.
The real problem: the decision belonged to nobody in the company
The most important part of this story is not the few hours of unavailability. It is who decided on them.
Not the company that uses the messenger to reach customers. Not its supplier. The decision was made between two external parties, over a matter unrelated to any of those companies, and it was carried out immediately, with no warning and no window to prepare.
This is a design feature, not a failure. A contact channel built on a consumer app from somebody else's store always has two authorities above it that can switch it off: the owner of the app and the owner of the store. Neither of them is a party to your contract with the customer.
The second risk, discussed less often: the number belongs to the employee
In the practice of Polish companies, a more common problem than a store block is that customer contact runs over sales reps' private numbers. The customer saves one particular person's number and writes to that number.
The consequences only show when that person leaves:
- The history of what was agreed with the customer stays on a private device and in a private account. The company has no access to it and no way to hand it over to a successor.
- The customer keeps writing and calling a number that does not belong to the company. From their point of view, the contact simply stops responding.
- In a complaint or a dispute there is nothing with which to document what was agreed and when.
This is not a question of trusting people. It is a question of where the record of customer contact physically sits.
A company number as the channel nobody can switch off on you
The alternative is not especially innovative, and that is exactly why it is resilient: contact on a number that belongs to the company.
A phone number is not an app in someone else's store. It cannot be withdrawn from distribution, it requires the customer to install nothing, and it does not stop working because somebody somewhere changed their terms. The customer calls or texts the same number as always.
W the ACTIO SIP Trunk adds something that is far from obvious in Poland: SMS on a company number works both ways. The customer does not just receive your message – they can reply to it on the same number they call. The reply lands in the company's system, not on a sales rep's private phone.
The practical difference looks like this:
| Situation | Messenger and a private number | A company number with ACTIO |
|---|---|---|
| The app disappears from the store | New employees and replaced phones are left outside the channel | No impact – a number is not an app |
| A sales rep leaves the company | The conversation history leaves with them | The history stays on the company's side |
| The customer wants to reply to a text | They reply to a private number, or not at all | They reply to the company number, both ways |
| Changing service provider | The channel stays with the provider | You take the number with the company |
What this article does not claim
We are not claiming that messengers are bad or that you should give them up. For many uses they are convenient and customers want them. Telegram's disappearance from the store lasted a few hours and ended without damage.
We are claiming something narrower: the channel through which a customer is supposed to reach you about money, a contract or a fault should not depend on the decision of a party you have no contract with. A messenger can be an addition. The foundation is better built on a number that belongs to the company.
If you want to test this against your own set-up, describe briefly how customer contact works at your company today and we will reply with what could be moved onto a company number, and how quickly. Your current number can be ported to ACTIO with no break in service.