A complete guide from account access to batch tasks

Feature overview

JQOneMatrix supports multi-account Telegram operations, including account access, collection and filtering, direct and group messaging, inviting and joining, registration and activation, group workflows and advanced tools. This guide groups features by workflow; use the V1, V2 and V3 names shown in the left menu when operating the application.

Recommended first-run sequence

1. Import accounts in Account Management and prepare proxies.
2. Select a few accounts and run Bulk Login or Account Check to verify both network and account status.
3. Review message, thread and network-concurrency options in Global Settings.
4. Prepare the groups, users, messages, media or tokens required by the task.
5. Run one account, a small dataset and a test target before scaling up.
6. Review successful, failed and unprocessed data together with the logs before retrying.

Installation, startup, multiple instances and data folders

1. Extract the complete package, keep its structure and make sure the folder is writable.
2. Start JQOneMatrixN.exe and wait for the main interface and left menu to finish loading.
3. Use a separate DataN folder for each instance; never let two processes operate on the same account files.
4. Back up or migrate the complete matching data folder because accounts, settings, logs, temporary files and reports live in different subfolders.

Logs, network and system time

For connection failures, code timeouts, Flood limits or authorization errors, read the account row and task log first. “Network connected” only means a connection was established; it does not mean Telegram authorized the account.

1. Verify the computer time and time zone.
2. Test proxy type, host, port, credentials and availability separately.
3. Run a login check on one account and distinguish Network Status from Account Status.
4. When reporting an error, keep the account, time, feature entry and complete error text.

Account Management

Account Management supports import, grouping, Bulk Login, Account Check, proxy switching, offline actions and export. Network Status and Account Status must be interpreted separately.

Import and check workflow

1. Select Import Accounts and choose the Session or account-file format.
2. Provide the correct two-step verification password when required; use force-password behavior only when an override is intentional.
3. Select a few accounts, choose a low thread count and run Bulk Login.
4. Wait for an explicit account state, then use Account Check for restriction, registration-time or other checks as needed.
5. Group or batch verified accounts and export a backup before using them in other tasks.

Proxy settings and batch proxy switching

1. Maintain proxies in the proxy dataset and verify type, host, port, username and password.
2. Test connectivity before selecting target accounts in Account Management.
3. Use Batch Change Proxy or Distribute Proxies to assign them.
4. Run Bulk Login or Account Check on one account after switching and verify both connectivity and authorization.
5. Scale only after validation; do not place too many accounts on one poor-quality proxy.

Advanced Import and Passkey

Passkey authorizes a new-device login. It does not contain all old-device information and does not require purchasing an additional token.

1. Open (P)Advanced Import and import a working original Session.
2. Run a login check and confirm the Session is authorized and can read account information.
3. Export and securely save the Passkey file.
4. For the new device, choose the matching type or file named like Passkey-*-New.
5. Wait for authorization, then run another login check in Account Management.

Datasets and random syntax

When the dataset under the second icon on the left contains values, {random} returns one random line; the default dataset contains emoji. If the dataset is empty, it returns one random English letter, number, symbol or space.

Workflow

1. Open the dataset, add one candidate per line and save it.
2. Insert the required placeholder into a text field that supports it.
3. Send several tests to verify dataset, fixed-length and ranged output.
4. If the dataset is empty, remember that {random} becomes one random character rather than an emoji line.

Supported message formats

1. Regular messages: text, image, voice and video are supported; at least one must contain data. Choose Markdown or Html for formatted text.
2. A single URL: select Default. If Convert Single Link to Media is disabled in Global Settings, the URL is sent directly and strangers usually see no preview; when enabled, it is sent as a media message.
3. Sticker: https://t.me/addstickers/stickershortname1 sends a random sticker from that pack; add /2 to select the second sticker.
4. PostBot: use @postbot content; for your own compatible bot use ~@mypostbot content.
5. Share a contact: use ~+15105226666 Display Name. The number may exist or not; only the display differs.

PostBot, Topics and content tools

Topic information, phone numbers or usernames, random media and deduplication are all task-preparation data.

1. Confirm whether the selected feature expects a link, phone number, username or collected-data format.
2. Deduplicate merged batches and keep an untouched source backup.
3. Prepare random-media folders using only media types supported by the task.
4. Provide the matching Topic information for topic sending; do not mix a group link with a Topic identifier.
5. Test one record before importing the complete list.

User, group and content collection

Current menu entries include Collect Users, Collect Users V2, Collect Groups/Channels and Collect Links/Messages. Each version has different sources and filters.

Collect Users V2 example

1. Select logged-in accounts and confirm they can access the source group or channel.
2. Enter group data; for channel sources, enable Include Related Group when needed.
3. Set Count, groups per operation and Online Time. Use 0 only where the interface explicitly says it means unlimited.
4. Enable Join Groups, Deep Collection, Collect from Cache, and username, display-name, bio or message-keyword filters only as required.
5. Select Start, watch account logs and the success count, then scale after a successful test.
6. Inspect and deduplicate the result before using it for inviting, direct messaging or filtering.

Filter PhoneNumber and Filter Phone/User V2

1. Prepare one deduplicated phone number or username per line in the format required by the selected entry.
2. Select logged-in accounts and configure threads, intervals and batch size.
3. Test a small input and confirm the meaning of successful, failed and unprocessed areas.
4. Run the complete task; after stopping, retain unprocessed data instead of classifying it as invalid.
5. Record the filtering time with exported results and sample-check again before a later task when necessary.

Bulk Private Message and Auto Group Message

The application provides Bulk Private Message/V2 and Auto Group Message/V2/V3. Their target input, scheduling and optional conditions differ, so do not reuse another version's configuration blindly.

1. Select verified accounts and import user or group data in the format required by the current version.
2. Enter text or choose images, voice or video; at least one content type must be valid.
3. Select Default, Markdown or Html. Use Default for special message syntax.
4. Configure threads, per-account quantity, send intervals and stop conditions.
5. Send to your own test target and verify formatting, media, link previews and randomized content.
6. After running, retain successful, failed and unprocessed data and use logs to distinguish invalid targets, permission errors, Flood limits and network errors.

Auto Group Chat, Auto Private Chat, replies and marketing

Related entries include Auto Group Chat, Auto Private Chat/V2, Auto Group Reply/Forward, Auto Reply/Like/Forward and Automated Marketing.

1. Define the listening scope: group, private chat, keyword or message type.
2. Configure the action: reply, like, forward or send prepared content.
3. Set accounts, roles, quantity, time, interval and stop conditions.
4. Check that no other task is using the same account or processing the same message.
5. Create one test message and confirm the rule triggers once with the correct action.
6. Monitor logs while running and stop the task before changing its rules.

Bulk Create channels and groups

1. Open Bulk Create and select logged-in accounts that can create the required targets.
2. Prepare names, descriptions, channel/group type and public/private options shown on the page.
3. Set per-account quantity and operation interval, then create one test target.
4. Verify its link, permissions, visibility and administrator capabilities.
5. Save or export the result before using it in Bulk Inviting, Auto Group Message or Sync Groups.

Bulk Inviting / V2 / V3

The versions retain different workflows. Bulk Inviting V2 supports multiple accounts, multiple threads and changing the group title after joining.

1. Select logged-in accounts and import the target groups and users to invite.
2. Configure threads, per-account/per-group limits, intervals, stop conditions and whether to leave groups.
3. For title changes, enable Change Group Title When Joining, provide title candidates or random output, and enable unique titles when needed.
4. If Change Title After Interval Count is enabled, the title changes only after the invite interval is met; the first account does not need to rename immediately.
5. Enable Do Not Invite with Title-Changing Account when that account should only handle title changes.
6. Test with a few accounts and one group, then run the full task and inspect successful, failed and unprocessed data.

Batch Join Groups, checks, bots and synchronization

Batch Join Groups/Check, Batch Join Groups V2/Bot and Batch Join Groups V3 add accounts or bots to targets; they are different from Bulk Inviting.

1. Prepare one deduplicated group link or collected-format record per line.
2. Select accounts; in Bot mode, confirm the Bot is configured and has the permissions required by the target operation.
3. Set per-account join count, threads and intervals, then choose options such as group distribution, random groups or join only when needed.
4. Check links or join one test with one account before the full task.
5. Inspect successful, failed and unprocessed data; resume from unprocessed data after a stop.
6. For Sync Groups, verify source and destination again to avoid reversing the direction.

Bulk Register, Batch Activation/Online and one-week Premium

1. Open Bulk Register, select the registration platform or method, and prepare numbers, verification/authorization resources, proxies and matching tokens.
2. Verify the API/device type, country code, two-step verification, email and other options shown on the page.
3. For one-week Premium registration, purchase the matching Premium token and choose that type in the registration module; do not use a standard registration token.
4. Use low threads and intervals to test one number through verification, email, payment or Premium steps.
5. Confirm the new account reaches the regular account directory and can log in before starting the batch.
6. Use Batch Activation/Online as needed after registration; keep new accounts at low frequency before adding concurrent tasks.

Premium, tokens, bots and business tools

Depending on the licensed scope, current entries also include (P)Premium Management, (P)Group & Bot Management, (P)Report Links, Claim Username, Change Phone, Business, Email Management, Payment Management and Token Management.

1. Import and check the required resources in Email, Payment or Token Management.
2. Open the business feature and select logged-in accounts and target data.
3. Verify credential type, account permissions, target links and irreversible-action warnings.
4. Run one account and confirm both the result and resource-consumption state.
5. After a batch, retain successful, failed and unprocessed data and check whether used credentials were marked correctly.

Global settings, proxies and task parameters

Global Settings affects multiple features. Record the old value before a change and validate with one account, a small dataset and one target.

• System Network Concurrency: limits concurrent network connections that do not use a proxy; use the value displayed by the current application as the baseline.
• Proxy Network Concurrency: limits concurrent connections associated with a proxy and is separate from each task's thread count.
• Convert Single Link to Media: controls whether a Default-format single URL is sent directly or as a media message.
• Threads and intervals: adjust task threads, per-account quantity and action intervals gradually for account, network and target limits.
• Datasets: verify actual {random} and {random_p} output after changing content.

Stuck login, frozen accounts and Batch Offline

“Network connected” does not mean “account logged in.” A frozen account may return FROZEN_METHOD_INVALID during Telegram authorization, or it may stall on verification, two-step authentication, Session data or proxy handling.

1. Stop Bulk Login and wait for the task to finish; do not dispatch new work to the account.
2. Read Network Status, Account Status and the complete account log, and record the Telegram response.
3. Confirm that no other feature or application instance is using the same account.
4. In Account Management, select only the affected account and choose Batch Offline. In the current version this also force-cleans a residual client when its login count is already 0.
5. After going offline, switch or test the proxy and run Bulk Login or Account Check for that account only.
6. If Telegram still reports frozen, banned, revoked Session, verification or two-step errors, resolve that condition; repeated offline actions cannot remove an account restriction.