RTX5 CRM:Onboarding, IB and Multi-Platform Operations
Preview broker CRM workflows for onboarding, IB, groups, spreads and payments. RTX5, MT5 and cTrader are compatibility targets; connector versions, supported tasks and live status require evidence.
CRM Workflow Scope to Verify
Client Onboarding
Specify document collection, review, account approval and provisioning permissions for the permitted client and jurisdiction; verify supported steps.
IB Management
Define referral ownership, tiers, eligible events, reversals and payout review. Confirm the portal and calculation outputs on the selected build.
Groups & Spreads
Propose group trading conditions with explicit spread, commission and leverage permissions, approvals and effective versions.
Deposits & Withdrawals
Separate broker approval, provider settlement and ledger posting. Confirm actual providers, currencies and supported permission controls.
Platform Connections
Review RTX5, MT5 and cTrader independently. Named versions, operation scope and acceptance records have not been published here.
Role-Based Workflows
Verify agent, manager and administrator access using allowed and denied cases; retain the supported audit fields and outcomes.
Follow a client through a scoped CRM workflow
A broker defines who can collect information, approve an account and authorize a money movement. The following example separates those decisions so the same client record can be followed across teams.
- 01
Collect and review
An onboarding agent collects the application and required documents. A reviewer records the outcome and reasons for any missing information. A submitted application is not yet an approved trading account.
- 02
Create an eligible account
An authorized operator selects the platform and account group after review. Keep the CRM client ID, trading account ID and connector response together; a failed provisioning attempt remains visible for reconciliation.
- 03
Assign the introducing broker
Record referral ownership, the agreed commission schedule and its effective date. Group or spread changes require their own permission; referral ownership alone should not confer trading-configuration access.
- 04
Review payment and account events
The payments team reviews a deposit or withdrawal request against the account and provider record. The broker's approval and the provider's settlement result are separate events; the operator reconciles both before closing the request.
Swipe horizontally to view all columns.
| Role | Assigned scope | Decision boundary |
|---|---|---|
| Onboarding agent | Assigned client records and required documents | Collect and request corrections; account approval is a separate permission. |
| IB portal user | Own referral tree and permitted commission statements | Visibility into eligible referrals does not grant access to unrelated clients or payment approvals. |
| Trading operations | Assigned platform, groups and account settings | Group, spread or leverage changes should carry an approver and effective configuration version. |
| Payments reviewer | Assigned transaction requests and reconciliation records | Distinguish request approval from provider settlement and ledger posting. |
Confirm each platform connection separately
A platform name identifies a compatibility target. The supported adapter, account operations and commercial access must be confirmed for that connection; a name alone does not establish a partnership or live integration.
Swipe horizontally to view all columns.
| Platform | Operations to review | Version and availability evidence |
|---|---|---|
| RTX5 | Client/account mapping, account provisioning, group assignment, balance events and operational reporting. | Status: not verified. Connector version, tested RTX5 build, review date and accepted operations have not been published. |
| MT5 | Account mapping, supported read/write operations, group changes and transaction reconciliation; confirm access granted by the platform operator. | Status: not verified. Adapter version, tested server/API scope and certification/acceptance record have not been published. |
| cTrader | Account linking, supported account events, reporting and permissions available through the agreed connection. | Status: not verified. Adapter/API version, granted scopes and test results have not been published. Availability must be assessed independently. |
CRM Pricing
| Plan | CRM Inclusion | Note |
|---|---|---|
| Entry (US$3,500/mo) | Included free | No additional licence charge |
| Standard (US$5,000/mo) | US$1,500/month add-on | Standalone CRM licence |
| Enterprise (US$50,000/yr, provisional) | US$1,500/month add-on | Standalone CRM licence |