Every pasted message is a mix of these three shapes — you can combine them freely in one paste.

11 A 99

Amount 11 · Type A · No. of numbers 99

Rs 22 234,,239 748,,784

Amount 22 · one row per number listed — the count is worked out automatically, you never type it

26.50
154
964

Bc
38
20

154 & 964 at amount 26.50 (whatever type is active)
38 & 20 as BC bets (amount stays 26.50 unless restated)
— a blank line ends a block and clears amount/type

A header can be just an amount (26.50), just a type (Bc), or a multi-type line (Ab-Bc-Ac or Ab Bc Ac — space or dash both work). Every bare number below it, down to the next blank line, is one pick against whatever's currently active.

Recognised types: A B C AB BC AC ABC ABCD, plus ALL (same as All bod/All board — see section 3) as a header on its own line meaning "route every number below by its own digit length" (1 digit → A/B/C, 2 digits → AB/BC/AC, 3 → ABC, 4 → ABCD). A number typed on the same line as the type still resolves against the amount's rate table as before.

A 99

Type A · 99 sets

Bc.19

Type BC, bet number 19 · counts as 1 set

This is the one rule worth training people on carefully — for the two-digit combo types (AB/BC/AC), a small number right after the type is almost always the customer's actual bet number, not "how many sets". For A/B/C/ABC/ABCD, a number after the type is a literal count instead.

AB-13

add "*2" for each-set: AB-13*2 → each set 2

A-1*10

Type A · 1 × 10 = 10 sets

A0=10set
AB12=7sets

Type A · 10 sets
Type AB · 7 sets

36-2

bet number 36 · each set 2

A,, 6,,50,set
A,, 6,,50,sat  ← typo, works too

Type A · 50 sets total
(6 is just which number was bet — it isn't multiplied in)

Dots work the same as dashes for this last shorthand — 5...10set means the same as 5-10set (a WhatsApp auto-correct quirk this handles automatically). Writing the bet number and the set count as separate comma-or-space tokens with a trailing set/sets word (like A,, 6,,50,set) works the same way — only the count (50) is added to the type's total, the bet number (6) is never used as a multiplier. The common typo sat/sats (a fat-finger of "set"/"sets" — a and e are next to each other on a phone keyboard) is recognised exactly the same as set/sets, since that's how it actually shows up in real pasted messages. A trailing line that's just Each2set (or Each 2 sets) retroactively sets the each-set for every bare pick above it back to the last blank line — handy when a whole block of numbers shares one each-set value stated at the end. The set/sets word on that line is optional too — Each 200 alone means the same thing — and the typo Ech (missing the "a") is recognised the same as Each.

All bod
61
65

61 & 65 are 2-digit → AB, BC, AC each get +1
(a 1-digit number would go to A, B, C instead)

Plain All on its own line (section 2) is now the exact same trigger as All bod/All board — both look at each bare number's own digit count: 1 digit → A/B/C, 2 digits → AB/BC/AC, 3 → ABC, 4 → ABCD — each family's count is how many numbers of that length were listed (the actual digits aren't kept, same as any other AB/BC/AC pick). The only exception: a number typed on the SAME line as the type header (e.g. "All 61 65" all on one line) still resolves against the amount's rate table the old way — this routing only applies to numbers on separate lines below the header. The typo bordu is recognised the same as bod/board. An each-set count can ride on the same header line — All board-2set, All bordu-2set, or board 2set (dash-joined or as its own trailing word, all work the same) — and stays in effect until the next board header line changes or restates it.

17.71.
13.31

17, 71, 13, 31 — four picks, not two decimals

A trailing or WhatsApp-glued dot or comma between two bare digit groups (17.71, 13,31) splits into two separate bet numbers, same as if they'd been typed on their own lines — this is what lets a whole row of glued pairs work under All board above. The one exception: if the whole glued number is actually a rate you've configured in Settings (like 26.5), it's left as that one amount, exactly as before — this only ever splits a pair that ISN'T a real configured amount. A 3-part date like 12.08.2026 is never affected either way.

• Never mentioned an amount at all in a block? It defaults to 11.
• An amount that maps to only one type in your Settings rate table gets its type auto-filled — nothing to check.
• An amount that maps to several types (e.g. 11 → A/B/C/AB/BC/AC in the default rate table) is added with a best guess and flagged amber in Preview — open the row and confirm or fix the type before committing.
• An amount that isn't in the rate table at all is flagged red — fix the amount, or add that rate line in Settings first.

Mention a date and/or session anywhere in a line (e.g. 8pm 06-06-2026, or just 1 pm) and every pick that follows routes to that show automatically — creating it if it doesn't exist yet. No date/session mentioned anywhere? Everything lands on whichever show is currently open in the Entry tab.

A date/session, once mentioned, is sticky for the rest of that block — you don't need to repeat it on every line. A blank line, or genuinely switching to a different session, starts a fresh block and clears it.

Pasting several forwarded WhatsApp messages together (each with its own [date, time] Sender: prefix) is fine — each forwarded message is treated as its own independent block and never inherits amount/type/session from the message above it.

Clicking Parse never touches a show — it only fills the Preview table below. Each row shows the amount, type, count, each-set and target show it resolved to. Fix anything wrong right there (amber = confirm the type, red = couldn't be read or amount isn't in the rate table), then click Add rows to shows to actually commit them. Nothing is written to a show until that click.