Overview
All profile statements
Imported client book
0Clients available for calling, WhatsApp and follow-up.
Connection activity
No API refresh yet.
Across your connections
Connection totals can overlap when API keys cover the same IB hierarchy. Counts shown here are sums of each connection’s reported totals.
| Connection | Clients | Sub-IBs | Income | Deposits |
|---|
Your client book
| Select | Client | Phone | Category | Status | Actions |
|---|
Import your Excel client list
Upload an .xlsx or .csv file with column headings in the first row. Choose the name, phone and email columns before importing. The first worksheet is used.
Existing phone numbers or matching emails are skipped. Reimporting the same source file repairs matching phone numbers affected by the earlier scientific-notation bug. Invalid phone numbers are skipped.
Total across all profiles
Combined totals use the latest saved cumulative statement for each profile. History preserves every saved snapshot. All money fields are USD.
Latest by profile
| Profile | Date | Clients | Active | Commission | Lots | Deposits | Withdrawals | Net deposit | Lots × $2 |
|---|
Statement history
| Profile | Statement date | Saved at | Clients | Commission | Lots | Deposit | Withdrawal | Net deposit |
|---|
Find and copy a link
Open linkSaved links
| Profile | Name | Split | Link | Actions |
|---|
Connect Telegram bot
Use a bot token from BotFather. Add your bot to the signal or support chat with the permissions it needs. This page receives messages available to that bot while you refresh. A dedicated bot avoids conflicts with an existing webhook or integration.
No bot connected.
Connection name and chat ID save in this browser. Bot tokens remain in memory until disconnect or page reload. Incoming messages appear only for chats your bot can access. This page has no background signal execution.Messages
Income at $2 per lot
Enter reported eligible lots by email and trading date. Estimates use your $2 per lot rate. MT5 balances are displayed in API data. Lot volumes must be entered here until a volume API is available.
Today and this month follow Asia/Kolkata. Each entry uses the trading date you choose. Entries are saved in this browser.Income by email
| Today’s lots | Today’s income | Month’s lots | Month’s income | Overall lots | Overall income |
|---|
Lot entries
Add only new volume. Entering the same volume again adds it to the total. Use Edit to correct an existing entry.
| Date | Profile | Lots | Estimated income | Actions |
|---|
Winpro API data
Choose a connection and load an endpoint.
JSON response
Deposits are shown as returned by Winpro. Total records counts transactions. A total deposit amount requires the confirmed amount fields and currencies. Affiliate users are shown under their API name until their role fields are confirmed.
Supabase cloud memory
Your project is preconfigured. Verify the same email on each device to access your CRM memory. Your verified CRM login also connects cloud memory. Load or save once to enable automatic cloud saves.
One-time project setup
Run the included supabase_setup.sql file in your project's SQL Editor. In Authentication → Email Templates, include {{ .Token }} in both the Magic Link and Confirm Signup templates so the email displays a verification code. Use the same email on every device. If email delivery is restricted, configure your SMTP provider or create the permitted user in Supabase first.
Row Level Security restricts each user's cloud record to that verified user. The publishable key is included in the site. Secret keys and database passwords are not needed here.
Database setup and email verification are required.
Save across devices
Save your original device first. On another device, verify the same email and load cloud data. After loading or saving once, automatic saves upload subsequent edits while this page is open. If another device saves a newer version, this device pauses saving and asks you to load it.
Cloud memory covers clients, income, profile statements, saved links and Telegram connection names/chat IDs. Winpro keys and bot tokens remain in memory. Verify your email again after reloading or when the session expires.
CRM memory in Google Drive
Save dated backups of clients, income, statements, links and Telegram connection names. Restore a backup when using another device. Google authorization is required for each session. API keys and bot tokens stay out of backups.
Open CRM folderGoogle connection setup
In your Google Cloud project, enable Google Drive API and Google Picker API. Create a Web application OAuth client with this site's exact address as an authorized JavaScript origin. Add your Google account as a test user if the consent screen is in testing.
Create a browser API key restricted to Google Picker API and website referrers for this site plus https://docs.google.com/*. Enter the same project's number below. These are application configuration values. No client secret is needed.
These configuration fields are saved on this device. Use the same Google Cloud project on other devices to access backups created by this app.Google Drive is not connected yet.
Save CRM memory
Each save creates a new dated JSON backup in your CRM folder. Your current browser keeps its local working copy. Save after making changes, then restore on another device when needed.
Restore CRM memory
Restore merges by record ID. Matching local records take the selected backup's values. Other local records remain. Deletions do not transfer through this merge. The list shows the latest 100 backups created by this app.
API connections
Add up to three Winpro keys. Keys stay in memory for this visit. Re-enter them after reloading. API requests use the included Netlify Function.
WhatsApp greeting
This message is prepared when you tap WhatsApp on a client.
Your phone chooses which WhatsApp app opens. Set WhatsApp Business as the supported-link handler if available on your device.