The most expensive missing word is often the unit

An instruction to buy “1” is not a size until somebody supplies the unit. One lot, one futures contract, one coin and one dollar of an asset are different propositions. A copier can carry the number faithfully and still produce the wrong exposure when the configuration gives it the wrong meaning.

Start with the destination's quantity model, then decide how a Telegram message supplies that quantity. Keep the provider's suggested size separate from your account's intended exposure. The provider may be trading a different balance, instrument specification or risk policy.

Quantity, notional, margin and risk

Quantity is the amount ordered in the destination's units. Notional describes the economic size at a price, while margin is the collateral requirement under the applicable account rules. Risk to a stop is a further calculation involving the entry, stop, quantity and contract value; these are related numbers, not synonyms.

For a deliberately simple linear example, buying 2 units at a price of 50 creates a notional of 100 in the quote currency. A stop at 47 implies a price-distance loss of 6 before costs and any difference in execution. Neither the 100 notional nor the 6 stop estimate tells you the venue's actual margin requirement.

What happens when the provider includes a size

TelegramSignal's documented Manual mode is a fallback, not an unconditional override of every size written by a provider. Auto depends on a usable supplied size, while Fixed Money has different precedence and availability. Check all current mode definitions in the official manual before choosing on the basis of the label alone.

Test both a message containing a size and one without it. The two cases reveal whether the fallback does what you expect, and they prevent a surprisingly common mistake: believing a saved default guarantees the same quantity for every incoming message. Record the result in destination units rather than only copying the displayed number.

Sizing from a stop requires a valid specification

Suppose an illustrative contract loses 5 currency units per price point for each contract, and the intended stop is 8 points away. One contract then represents a 40-unit stop-distance estimate before costs. A 100-unit budget would mathematically fit 2.5 contracts, but a venue requiring whole contracts does not accept that fraction.

Under those assumptions, 2 contracts represent 80 units and 3 represent 120. Rounding up crosses the stated budget, so the choice cannot be hidden inside a formatting operation. This example illustrates the arithmetic; it is not a recommended risk budget or a specification for every future.

A valid total can become invalid after splitting

Dividing quantity across multiple targets can create legs smaller than the minimum or incompatible with the step. On crypto venues, a quantity can also pass a size check but fail a minimum-value check. Binance's official filter definitions distinguish quantity increments, price increments and notional constraints.

Do not assume every connector resolves those situations in the same way. Inspect the resulting allocation and rejection messages on the destination being used. A broker's minimum is a condition of the actual order, not an inconvenience that disappears because the original Telegram number was sensible.

Verify the final ticket

Check the quantity after all route settings have acted on it. A later multiplier, contract conversion or target split can change the number you thought you chose earlier. The most useful evidence is the final accepted quantity alongside the source message and the relevant settings.

Then consider the account's existing exposure. Correct sizing on one order does not stop several channels from taking the same directional bet together. The account-level risk guide explains that next layer, while the crypto workflow guide separates the market types that often cause confusion at this stage.