A careful first setup: start with a demo

01

Prepare before you connect anything

Choose one signal source that you already understand and can access legitimately. Gather a MetaTrader 5 demo account from a supported broker, and decide what you want to test: message reading, profile rules, or a complete demo order path. Starting with a small, specific question makes it easier to spot a configuration error than trying to automate every source at once.

The TTMT path is designed around a managed cloud service, so a first evaluation should not require you to write an integration or administer a VPS yourself. You will still need to connect eligible accounts and confirm their readiness. Cloud hosting does not mean every broker, Telegram source, account type, or execution feature is automatically available.

• Access to the Telegram source and permission to use its messages.
• A supported MetaTrader 5 demo account; do not use a live account to test setup.
• A short written list of the rules you want to verify.

02

Create an account and secure access

Create your TTMT account through the official sign-in flow and complete the email verification steps it requests. Use a unique password and keep sign-in and verification codes private. Where multi-factor authentication or passkeys are offered for your account, set them up before connecting a trading account or enabling an execution action.

Create your account, then connect your Telegram sources and MetaTrader account using the account screens. You do not need to install a server or write code. The setup is a few choices about your own trading workflow: which signals to follow, which account receives them and which settings to use.

03

Connect a supported demo account

Use the MetaTrader account connection flow for an eligible MT5 demo account, then read the displayed status instead of treating saved credentials as proof of readiness. The terminal, account identity, broker symbol catalog, and account permissions all affect what a later test can do. If the account appears pending, disconnected, or limited, resolve that state before interpreting a result.

Support is not universal across brokers. A broker appearing in a discovery list does not prove that its exact account has been connected or that a particular symbol can be traded. Confirm the account's own state and try only a clearly labelled demo workflow; do not infer live-account support from a demo connection.

04

Add one source and choose its route

Connect a Telegram source that you are authorized to use. Keep source monitoring separate from sending its signals toward an account: a source can be visible for review without being ready for execution. Assign the intended demo account and profile only after checking that the channel, account, and profile belong together in the displayed route.

The managed cloud route removes the need to leave your own computer running a copier, but it does not remove the need to check connection and readiness indicators. If a source or account is not ready, the useful next step is to find out why—not to retry a potentially consequential action until the status becomes clear.

05

Write down and preview your rules

Create a trading profile for the test and decide your sizing method, stop-loss and take-profit behavior, symbol mapping, and relevant filters before previewing a message. Read the settings in plain terms and check any account-specific mapping against the broker's actual symbol. Avoid copying a configuration from someone else without understanding its assumptions.

Use Preview to compare the parsed fields and the selected profile with the original message. A draft preview is a review step, not an order and not a backtest. It may not validate broker-dependent calculations when a terminal is offline. Save the version you mean to test, and check that the account has received the intended version before asking it to execute.

06

Run a test only in the demo path

Use Run demo execution in Signal Tester with your connected demo account to try one supported message. Check the selected account and profile, then follow the result. Run checks execution, not Telegram ingestion or channel routing. The same screen has a separate optional Telegram Bot receiver test; check its own status and requirements, and verify your connected source and route separately. If a connection or permission needs attention, resolve the displayed issue before testing again. Do not switch to real money simply to see whether an unfamiliar setup works.

A message accepted by the application is not automatically a broker-confirmed trade. Follow its event history and wait for an explicit outcome. If the result is uncertain or still reconciling, do not submit the same idea again merely to force a visible success state.

07

Review the whole path and keep monitoring

Compare the source message, parsed signal, profile version, account activity, and broker history. Check timestamps and whether a view reports its data as current, delayed, or stale. A position screen and a trade-history view answer different questions, so use the detail that matches the action you are investigating.

Pausing future execution is not the same as closing a position that is already open. Decide in advance how you will monitor an account and what you will do if a connection, market, terminal, or cloud service is unavailable. This guide describes a safe way to evaluate a workflow, not a recommendation to place a trade or to move beyond demo use.