A copier can make a channel easier to follow, but it cannot turn a selective performance record into a complete one. Start by examining the source as a stream of decisions available at particular times. A screenshot of the final chart does not tell you what a subscriber could have known before the move.
Look for a complete record containing losing calls, cancellations, revisions and periods without attractive trades. Preserve timestamps and the original wording where you have permission to do so. Missing information should remain missing in your assessment rather than being filled with the most favourable interpretation.
In this guide
Reconstruct what a subscriber received
For each sampled instruction, identify the first actionable message, its entry policy and the information present at that time. Add later edits and replies in chronological order. A stop added after the price moved cannot be treated as protection that existed at entry.
Deleted posts and unavailable historical versions limit reconstruction. Say so in the record rather than treating the surviving messages as a perfect audit trail. Telegram exports and screenshots can help organise evidence, but neither automatically proves that a public performance claim includes every original instruction.
Ask whether the price was available
A quoted entry is not necessarily an executable fill. Compare the message's timing with the relevant instrument, session and available quote, including Bid and Ask where applicable. When that evidence is unavailable, classify the fill assumption explicitly instead of awarding a target to an imagined trade.
Entry zones make the problem larger because the chosen point changes both risk and reward. Use the format guide to distinguish instructions from commentary and the entry-range guide to document the execution policy. Apply the same policy to winners and losers.
Follow management through to closure
A channel may announce TP1, move a stop, add a position or cancel an unfilled entry. These are different events with different effects on the account. Reconstruct the quantity remaining after each action rather than adding every advertised target as though the full original position closed there.
Record ambiguous messages as ambiguous. A provider who relies on voice notes, unstated conventions or discretionary live commentary may require interpretation that your planned route does not support. Consistency of instructions is a separate question from trading performance, and both matter to automation.
| Evidence | What it can establish | What it cannot establish alone |
|---|---|---|
| Original timed instruction | Information available at publication | Your actual fill |
| Full management sequence | Intended trade lifecycle | Connector compatibility |
| Destination order history | Accepted orders and executions | Future profitability |
| Promotional result image | A selected reported result | Complete performance |
Include the bill and the quiet failures
Allow for spreads, commissions and financing relevant to the instrument. Also record skipped signals, rejected orders and the effect of the quantity convention you actually intend to use. A result calculated with arbitrary fixed size may not describe the account behaviour of a source that varies its size.
Do not judge reliability from a handful of attractive sessions. Observe varied conditions and document what your sample excludes; historical observation cannot guarantee future outcomes. The account-risk guide covers overlap between signals that may look independent when listed separately.
Move from observation to a controlled rehearsal
Run a demo route and compare source intent with destination records, including losing and cancelled instructions. Keep a discrepancy log with timestamps and the settings active at the time. This tests compatibility and execution behaviour rather than certifying the channel as a profitable strategy.
Only then use the setup guide to finalise the route. Automation should follow a decision about the source; it should not substitute for making that decision.
Put the route to a demo test
Use the current setup instructions and verify the resulting orders in your destination account. Start with a configuration you can inspect before adding more sources.
Open TelegramSignal in AlgoWay