Live demo

Test real delivery from a CRM-style interface to Telegram and MAX without registration or an API key.

Open the live demo

What you need

A phone with Telegram or MAX installed. The demo uses dedicated MassAccess bots and does not connect your company bots or company data.

How to run the demo

  1. 01

    Open a channel

    Scan the QR code with your phone or follow the Telegram or MAX link.

  2. 02

    Start the bot

    Start the bot in the messenger. The channel status on the page updates automatically without a reload.

  3. 03

    Send a message

    Select one or both connected channels, then use a template or enter your own text.

  4. 04

    Check the result

    Receive the message in the messenger and compare the independent Telegram and MAX statuses in the chat.

What the statuses mean

StatusDescription
AcceptedMassAccess accepted the command and started processing the send.
SentThe provider accepted the message. This status does not confirm that the recipient read it.
ErrorThe selected channel failed; the other channel keeps its independent state.
Limit reachedThe session used all available sends. Restart the demonstration to continue.

Temporary session and limits

A session lasts up to 15 minutes and allows up to 10 channel sends. Sending one text to both Telegram and MAX consumes two sends.

Start a new demonstration

The “Restart the demonstration” button deletes the current temporary session, resets its connections, and issues new QR codes. Previous links stop working.

Data and privacy

The session is bound to a protected cookie. Chat history exists only on the open page, while temporary server state is removed automatically by TTL. The demo does not create a company, customer, message archive, or customer analytics in MassAccess.

If a channel does not connect

  • Make sure you opened the link from the current session and started the bot.
  • If the QR code or link is old, restart the demonstration and use the newly issued link.
  • If the page shows “Connection lost”, retry the connection before sending another message.
  • A provider error in one channel does not require reconnecting the other channel.