RA OS — Setup Guide for Research Analysts

Onboard your practice onto RA OS step-by-step — when, where, what, how, and why.

1Sign up your organization

Go to the B2B signup page. Verify your email with a one-time code, set a password, then fill in your organization profile: name, SEBI registration number, BSE enlistment number, desired subdomain, and support contact.

2Upload verification documents

You'll be asked to upload:

• SEBI Registration Certificate
• Business Registration Proof — GST Certificate, or if you don't have GST (many individual RAs are below the registration threshold), a Shop & Establishment Certificate or Udyam/Udhyam Aadhaar registration instead. Optional either way.
• PAN
• Bank Account Proof
• Aadhaar
• A short live Video KYC (recorded in-browser — hold up an ID and state your name/ID number aloud)

You can add or remove any of these documents later too, from Settings → Verification Documents — you're not locked to what you submit at signup.

3Wait for approval

A platform reviewer checks your submitted documents and either approves or rejects your organization. You'll be able to log in once approved.

4Set up your Organization Profile

In Settings → Organization Profile, fill in your name, SEBI reg no, BSE enlistment no, logo, tagline, and brand color — this is what your own clients see on your public landing page and in emails.

Investor Charter (Welcome Kit): Settings → Investor Charter (Welcome Kit) — upload your own signed SEBI Investor Charter PDF once, and it's attached automatically to every new client's Welcome Kit email and dashboard from then on.

5Your own credentials (Digio, CVL KRA, Razorpay, PaRRVA, Resend)

Compliance rule for B2B tenants: client KYC/e-sign must run on your own vendor accounts — the platform's shared account is for the default org only.

Every integration below lives in Settings. Leave a field blank to keep using the platform shared default (only until you configure your own — B2B tenants should plan to use their own accounts).

6Telegram, WhatsApp & email channels

Settings → Channel Configuration — trade calls, the Welcome Kit, and your inbox all connect from here.

• Telegram — get your own bot token (from @BotFather), register the webhook, then use "Detect My Groups" to map plan categories. Replies show up in the Telegram Inbox.
• WhatsApp Business — Phone Number ID + Access Token (Meta Business). Outbound/inbound messages appear on the WhatsApp Inbox page.
• Resend email — see the credentials step above; without this, no Welcome Kit email can go out (B2B tenants should configure their own account).
• Owner Telegram chat id (optional) — get a personal copy of every client's Welcome Kit sent to you as well.

7Set up how clients pay you

In Settings, choose which payment method(s) your clients see:

• Your own Razorpay account — enter your Key ID/Secret/Webhook Secret so your clients' payments go directly into your own account, not a shared one.
• Valid UPI — a free, always-available option: set your UPI ID (must contain @valid, per SEBI's Valid UPI requirement) and upload your QR code. Clients pay directly and submit a UTR for you to verify manually.
• 3 payment gateways available — Razorpay, PhonePe, and Cashfree, each configurable per organization in Settings with your own credentials. Need a different gateway (e.g. PayU, CCAvenue)? We can integrate it for you on request — it's a straightforward API integration. Customization is available at every step, at nominal cost.

Valid UPI is part of the exact same fully-automated onboarding as any other payment method — the one difference is a single manual check, since UPI has no bank API to auto-confirm the money landed. A Google Apps Script watches your Gmail for Canara Bank credit-alert emails and auto-verifies most Valid UPI payments on its own; when that alert doesn't fire, you verify it yourself — confirm the payment landed in your own bank account, then click "✓ Verify Payment," either from the dedicated Verify Valid UPI page (sidebar, directly below Client Master (Logs) — every pending UPI payment listed newest-first, so you never have to search for a name) or from the same client's row in Reports → Prospects, where an unverified UPI payment shows up immediately. Once verified, activation, the Welcome Kit email, and the Telegram invite all fire automatically — exactly like a Razorpay/gateway payment.

8Upload your compliance documents

On the Legal & Compliance Documents page, upload your own reviewed Disclosures, Terms & Conditions, MITC, Refund Policy, Grievance Redressal, Privacy Policy, AML Policy, and Internal Policy. These are attached automatically to your clients' Welcome Kit emails once uploaded.

9Subdomain, custom domain & website content

The Domain & Microsite and Website Content pages — your public site's URL, footer links, and text blocks.

Every organization gets a free subdomain by default (yourname.os.profitxresearch.com style). For a custom domain (whitelabel), enable the add-on in Settings → Add-ons, then follow Domain & Microsite — connecting a real domain needs DNS steps with your registrar and a manual Vercel step with the platform owner.

Website Content page lets you edit footer links and editable text blocks on your public site without code. Content Hub (platform owner org only) manages profitxresearch.com marketing CMS — B2B tenants use Website Content for their own microsite.

10Add plans and clients

Create your subscription plans in Plans, then either add clients manually in Client Master (Logs), or bring in an existing roster from prior software using Data Migration (clients, plans, and historical payments can all be imported).

When a client joins, they go through a sequential Sign Agreement → KYC → Payment flow. You control which method is used for each of the first two steps — this is entirely your own choice as the registered RA, not something RA OS imposes on you:

• Agreement signing: Aadhaar OTP e-sign via Digio (a paid, per-signature vendor cost), or RA OS's built-in "consent-click" method — the client reviews the agreement, draws a signature, and RA OS generates a Certificate of Electronic Consent as the audit-trail record, at no per-signature vendor cost. SEBI accepts any legally verifiable signing method, not Aadhaar OTP specifically — this is your own compliance judgment as the RA.
• KYC verification: an automated instant lookup via CVL-KRA specifically (a paid, per-check vendor cost), or manual verification — which works for a client registered with ANY KRA, not just CVL: you record what you personally checked (e.g. PAN + Aadhaar copy shared by the client) and the notes are saved to the same audit trail. Manual verification is your own liability as the RA — RA OS never verifies KYC on your behalf either way, it only provides the tool and the record-keeping.

On the KYC step, a client also selects their own Client Category — Individual (Resident), NRI, FPI, or Institutional/Company. NRI/FPI clients upload a Passport + overseas address proof alongside their normal PAN/DOB check; Institutional clients (Company/Trust/HUF/Partnership/etc) upload entity registration documents instead of a personal PAN/DOB and are routed to manual review, since a company has no date of birth. This also fixes your H1/H2 periodic report's "Clients And Fees" schedule, which now correctly splits client counts and fees across these categories instead of assuming every client is a Resident Individual.

11Client onboarding — admin walkthrough

Add clients from Client Master (Logs), share the signup link, and track every step — why: SEBI's audit trail requires every stage to be recorded.

1. Create your Plans first — category, segment, price, duration. These are exactly what clients see at signup.
2. Client Master (Logs) → Add Client: email, plan, optional payment link. Why: a pre-added client is auto-linked when they sign up.
3. Send the client your public signup URL (yoursubdomain.../client/signup or your custom domain).
4. Watch the status badges on the CRM row: Agreement (Digio pending/signed or consent-click), KYC (CVL processing/verified or manual), Payment (Razorpay auto or UPI pending).
5. UPI verify: when a client submits a UTR, the CRM shows payment pending — you verify it manually and activate the client. Why: Valid UPI has no automatic bank confirmation.
6. Once active, the Welcome Kit (Resend email + Telegram) goes out automatically — invoice, signed agreement, and policies attached.
7. Upload Signed (16-page): click Manage ▾ on any client's row to reveal this button alongside View Signed PDF and ⬇ Download Full-KYC PDF. RA OS's own record of a Digio Aadhaar-OTP signature is just a 1-page completion certificate — this button lets you manually attach the client's real full signed agreement PDF (the 16-page document Digio emails to you) so it shows correctly in View Signed PDF and in your Reports → Bulk Signed Agreements export. Choose the PDF file; it's stored against that client's record, replacing whatever was there before.
   Upload Signed (16-page): किसी भी क्लाइंट की row पर Manage ▾ क्लिक करें — यह बटन View Signed PDF और ⬇ Download Full-KYC PDF के साथ दिखता है। Digio Aadhaar-OTP signature का RA OS का अपना record सिर्फ़ 1-page का completion certificate होता है — यह बटन आपको क्लाइंट का असली पूरा signed agreement PDF (Digio से ईमेल पर मिलने वाला 16-page document) मैन्युअली अटैच करने देता है, ताकि वह View Signed PDF और आपके Reports → Bulk Signed Agreements export में सही से दिखे। PDF फ़ाइल चुनें; यह उस क्लाइंट के record में save हो जाती है, पहले जो कुछ भी था उसकी जगह लेकर।
8. Use the Resend to Customer dropdown to resend the Welcome Email or Telegram link — this does not trigger a new charge.
9. Telegram links always mint fresh — a resend never reuses a stale cached invite link, so it can't silently go dead. If a Welcome Kit or Telegram notification ever fails to send, it now self-heals automatically in the background — no admin click needed to retry it.
10. Telegram join detection: if an active client's onboarding timeline shows a Telegram link was sent but they haven't actually joined the group after a reasonable window, you'll see a 🔔 bell alert and it's flagged on their Client Master onboarding-journey timeline — so a delivery gap never goes unnoticed until a client complains.

12Daily operations (Dispatch, Compliance, Comms)

Your day-to-day work — sending trades, updating compliance, and client communication.

• Dashboard — pending KYC, UPI payments, expiring subscriptions, and recent dispatches, all at a glance.
• Trade Dispatch — send recommendations (all/category/individual). Use the Schedule option for auto-dispatch at a future time. PaRRVA segments (Intraday/Single Stock/Derivative) are submitted from here too — never touch the production PaRRVA logic itself; just set your own credentials in Settings.
• Compliance Tracker — Filing Calendar, Annual Audit Kit, Document Vault, and BSE Periodic Report data. Why: this collects the data you'll need for half-yearly filing well in advance.
• Complaints — log every investor complaint; this feeds both your public monthly disclosure and your BSE periodic report.
• SEBI/BSE Circulars — review new circulars and mark the ones relevant to you.
• Communication Center — send bulk email/Telegram/Dashboard messages to active clients, a category, one client, or anyone at all (any email address, not just clients). Connect your own Gmail, Titan Mail, or any other SMTP provider in Settings.
• Telegram / WhatsApp Inbox — view and reply to inbound messages.
• Public Appearance Master — log your TV/social/media appearances, for BSE periodic reporting.
• Client Activity Log — a single cross-client feed of every event (signup, agreement signed, KYC verified, payment, Welcome Kit sent, Telegram link sent, Telegram joined, portal logins), sortable and filterable with IST timestamps. Why: answers "who hasn't joined Telegram yet" or "who's actively using the portal" across your whole client base at a glance, instead of checking each client one by one.
• Reports — revenue, client lists, bulk signed-agreements ZIP, backups.

13Team, Moderator & MFA

Invite staff from the Team & Access page; secure your own account under Settings → Security (MFA).

• Admin — full access including Settings credentials, billing, team management.
• Moderator — Client Master, Trade Dispatch, Reports, Communication, Compliance, Blog/Circulars — but not Settings credentials, Platform Billing, the Team page, or permanent client deletion.
• MFA (TOTP) — Settings → Security — enroll in Two-Factor Authentication (Google Authenticator etc.). Why: your admin account holds Razorpay/Digio keys — MFA is strongly recommended.
• Passkeys — Settings → Passkeys (Touch ID / Windows Hello) — register your device's built-in biometric/PIN as a passwordless login option, alongside your password + MFA.
• Alternate Login Emails — Settings → add extra verified emails to the same account.

14Trade Dispatch & scheduled dispatch

Send recommendations from Trade Dispatch — targeting all clients, a category, or specific individuals. Use the Schedule panel to queue a dispatch for a future date/time (cron sends automatically). Use Compliance Tracker, Complaints, and Public Appearance Master for regulatory record-keeping.

15PaRRVA Verified Performance on site

Once you submit trade calls to PaRRVA (Trade Dispatch's Intraday/Single Stock/Derivative segments — see the earlier step), you can show your SEBI PaRRVA-verified performance directly on your own public site. Enter your own PaRRVA Enrolment ID/Password under Settings → Your Own PaRRVA Credentials, then turn on Settings → PaRRVA Verified Performance — Public Display.

16Blog & Social Media Auto-Posting — getting your developer credentials

Blog (Communication Center → Write a New Blog Post) — publish posts on your own domain/subdomain. Naming a security, or using market price data from within the last 30 days, anywhere counts as a research recommendation under SEBI rules — check the "count as a Public Appearance" box when it applies and it's logged automatically, no separate step.

Communication Center → Social Media Auto-Posting lets you connect unlimited accounts per platform (Facebook, Instagram, LinkedIn, Twitter/X, YouTube, Telegram) and post manually, on a schedule, or from an AI-drafted suggestion you approve. Every published post is automatically logged as a Public Appearance record, ready-made for your Reports exports (H1/H2 periodic and Annual Compliance Audit).

Facebook (Page posts, Reels, Stories)

1. You need an existing Facebook Page (not a personal profile) for your practice.
2. Go to developers.facebook.com → My Apps → Create App → choose type "Business".
3. In the app dashboard, add the Facebook Login and Pages API products.
4. Under Tools → Graph API Explorer, select your app, select your Page, and generate a Page Access Token with the pages_manage_posts and pages_read_engagement permissions.
5. Note your Page ID (visible on your Page's About section, or via the Graph API Explorer).
6. In RA OS: Settings → Social Media Auto-Posting → Connect Account → Facebook → paste the Page Access Token and Page ID.

Instagram (feed, Reels, Stories)

1. Your Instagram account must be a Professional (Business) account, linked to the same Facebook Page above.
2. Reuse the same Meta App from the Facebook steps — no separate app needed.
3. In Graph API Explorer, find your Instagram Business Account ID by querying your linked Page: GET /{page-id}?fields=instagram_business_account.
4. The same Page Access Token from the Facebook steps works for Instagram too.
5. In RA OS: Connect Account → Instagram → paste the Page Access Token and IG Business Account ID.

LinkedIn (Organization posts)

1. You need an existing LinkedIn Company Page for your practice, and you must be an admin of it.
2. Go to linkedin.com/developers/apps → Create App, linking it to your Company Page.
3. Request access to the "Share on LinkedIn" / Community Management API product (LinkedIn reviews this request — approval can take a few days).
4. Once approved, generate an Access Token via LinkedIn's OAuth flow (3-legged OAuth, w_organization_social scope).
5. Note your Organization URN — format urn:li:organization:XXXXXXX, visible in your Company Page's admin URL.
6. In RA OS: Connect Account → LinkedIn → paste the Access Token and Organization URN.

Twitter/X

1. Go to developer.x.com → apply for a developer account (free tier available, has a monthly post-write limit — check current limits before relying on this for volume).
2. Create a Project and an App inside it. Under the app's User authentication settings, set permissions to Read and Write.
3. Under Keys and tokens, generate: API Key, API Secret, Access Token, and Access Token Secret (all 4 are required — regenerate Access Token/Secret AFTER setting Read+Write permission, or they'll be read-only).
4. In RA OS: Connect Account → Twitter/X → paste all 4 values.

YouTube

1. Go to console.cloud.google.com → create a new Project.
2. Under APIs & Services → Library, enable the YouTube Data API v3.
3. Under APIs & Services → Credentials → Create Credentials → OAuth client ID (type: Desktop app) — note the Client ID and Client Secret.
4. Complete Google's OAuth consent flow once (as the channel owner) to get a Refresh Token — the standard way is Google's own OAuth 2.0 Playground: enter your Client ID/Secret in its settings, authorize the YouTube Data API v3 scope, and exchange for a refresh token.
5. In RA OS: Connect Account → YouTube → paste the Client ID, Client Secret, and Refresh Token.

Telegram (as a marketing/broadcast channel)

1. Message @BotFather on Telegram → /newbot → follow the prompts to get a Bot Token.
2. Use a separate, new bot for this — do not reuse your trade-dispatch bot token from Section 6, so a compromised marketing-post credential can never touch client trade delivery.
3. Add this new bot to your marketing channel/group and promote it to Admin.
4. Get the Chat ID — the simplest way is to forward any message from the channel to @userinfobot, or check the bot's own getUpdates API response after posting once manually.
5. In RA OS: Connect Account → Telegram → paste the Bot Token and Chat ID.

17Educational CMS — Courses & Mentorship

A separate, lighter offering from your regular trade-recommendation client roster: build and sell educational Courses (video, PDF, image, and link lessons, organized into modules) to your own students. Enable it from Settings → Add-ons (₹299/month — free for the default org).

• Course builder — /admin/educational-cms.html — create courses, modules, and lessons; video lessons embed via privacy-enhanced YouTube, PDFs/images upload directly.
• Separate student identity — students sign up and log in through their own dedicated flow (/edu-signup.html, /edu-login.html: name/email/mobile/password + email-OTP verification), deliberately kept apart from your ra_os.clients roster, since course enrollment is not the RA advisory relationship.
• Mentorship e-sign — an optional "Educational Course Mentorship" consent step for enrollees, signed either by drawn signature or Digio Aadhaar OTP — your choice of method, same as your regular client agreement options.
• Dedicated payment gateway — Settings → Educational Billing: your own Razorpay + UPI credentials, kept completely separate from your RA-service payment account, so student course-fee money never mixes with client advisory-fee money.
• Educational CMS's own UPI QR upload: on the /admin/educational-cms.html page's own Payment Settings tab, under "Dedicated UPI," set your UPI ID and upload a QR code image (PNG/JPEG/GIF/WEBP). This is a completely separate QR code from the one you upload for your regular client payments (Section 7) — it's stored and served only for student course-fee checkout, never mixed with your RA-service Valid UPI QR.
  Educational CMS का अपना UPI QR अपलोड: /admin/educational-cms.html पेज के अपने Payment Settings टैब पर, "Dedicated UPI" के नीचे, अपना UPI ID सेट करें और एक QR कोड इमेज (PNG/JPEG/GIF/WEBP) अपलोड करें। यह आपके नियमित क्लाइंट पेमेंट्स (Section 7) के लिए अपलोड किए गए QR कोड से पूरी तरह अलग है — यह सिर्फ़ student course-fee checkout के लिए store और serve होता है, कभी भी आपके RA-service Valid UPI QR से मिक्स नहीं होता।
• Catalog & player — students browse the published course catalog (/edu-catalog.html) and enroll with one click; lessons play through /edu-course.html.

18Your plan & pricing — revenue-share model

RA OS does not charge a flat monthly SaaS fee. Instead, the platform fee is a small percentage of your own advisory revenue — you only pay RA OS when you are actually earning from your own clients. The percentage and the minimum monthly floor both depend on which plan you pick (Basic/Professional/Growth/Scale/Enterprise); each month you pay whichever is higher — the percentage or the floor, never both added together. Each plan is also capped by your active (paid) client count — once you reach your plan's cap, you'll need to upgrade to add more clients. Fully customizable at every level, at no extra charge.

Included at every tier, no extra cost: the full admin dashboard (Client Master, Trade Dispatch, Compliance Tracker, Complaints, Reports, Settings, Team & Access), your own client portal on your own subdomain, PaRRVA trade submission + verified public performance display, Social Media Auto-Posting (unlimited connected accounts, manual/scheduled/AI-drafted posts, automatic Public Appearance compliance logging), unlimited plans/clients/trade dispatches, and the free self-service Data Migration importer.

18A. Market Analysis Software (one-time ₹99,999, lifetime support)

This is the tool the platform's own Research Analyst practice uses to prepare recommendations, and it is available to your organization as a one-time purchase. There is no subscription and no renewal — you pay once and it stays yours, with lifetime support.

What it unlocks:

• Live BUY/SELL Signal analysis on every Trade Dispatch watchlist row — CMP against today's open, with a segment-aware stop-loss and target preview.
• MCX Commodities board — GOLD, SILVER, CRUDEOIL, COPPER and the rest, live from your own broker connection.
• Trade Dispatch auto-fill — real lot size, live expiry dates and strike lists pulled from your broker's own contract master, and live CMP filled straight into the entry, target and stop-loss fields.
• Option chain, sector boards, Most Active and IPO listing-day tracking.

Without this add-on, Trade Dispatch keeps working in full — you enter the contract, the lot and the prices yourself, and dispatch and PaRRVA submission behave exactly as before. Only the automatic filling and the live analysis boards are switched off.

You bring your own broker. The add-on is the software; the market data comes from a broker account in your own name — Fyers or Zerodha (Kite Connect). That is deliberate and is what keeps it lawful: each RA sees data from their own broker account, and no exchange feed is redistributed from here to anyone. Your broker may charge its own API fee (Zerodha's Kite Connect is billed monthly by Zerodha, not by us). Connect it under Settings → Broker Connection.

Enable it from Settings → Add-ons. Payment is collected once through the platform's own billing account; the feature switches on as soon as the payment is confirmed and never lapses after that.

Optional paid add-ons (Settings → Add-ons, toggle on only what you need): Whitelabel custom domain (free to enable, you bring your own domain), Scheduled automatic backups (₹299/month), Trade Reports → Google Drive sync (₹299/month), NISM-XV + CPE Exam Prep for your team (₹499/year — note: the RA-XV main exam mock test and its CPE renewal mock test are now free and public for anyone at /nism-prep.html, unlimited retakes, no login needed; this paid add-on additionally gives your team full study-module access and the complete question bank), Automatic/Scheduled Trade Dispatch (₹299/month), Market Analysis Software — Market Watch Live Signal Analysis + Trade Dispatch auto-fill (one-time ₹99,999 with lifetime support — pay once, it never expires and never renews; see Section 18A below), Client Auto-Pay (₹299/month), Educational CMS — Courses & Mentorship (₹299/month, see Section 17 above), Hosting + Domain + Email (₹6,035 for the 1st year* — renewal from Year 2 onward is priced as per actual GoDaddy renewal rates, typically higher). Exact current pricing for each is always shown live on the Add-ons page in your dashboard.

19Platform Billing & Data Migration

The Platform Billing page shows your current client-count tier, your computed revenue-share fee for the period, and your full invoice/payment history — there is no separate plan to "subscribe" to, since your fee is calculated automatically from your own paid-client count each period (see Section 18 above). On the Data Migration page, import clients/plans/payments as a CSV from your prior software — a column-mapping step is included; migrated payments are excluded from the revenue-share calculation. This self-service import is free and always available.

GST & Company Details (optional). Settings → GSTIN for invoices; company name/CIN for Pvt Ltd/LLP.

Plan segments, PaRRVA categories, and where a recommendation lands

A plan's segment is not a label — it is the routing decision. Every segment files under one of PaRRVA's own five advice categories, and the same segment decides which Telegram group the advice goes to and which clients see it on the portal and in the app. One value, three consequences.

Strategy advice routes by what it is written on. A strategy or option on an index (NIFTY, BANKNIFTY, FINNIFTY, SENSEX and the rest) goes to the index group; one on a single stock goes to the stock group; a strategy with an index leg and a stock leg goes to both, because it genuinely belongs in both.

This is per tenant, not shared. Your plans, your clients, your Telegram groups and your own PaRRVA credentials — a recommendation you dispatch reaches only your own clients and is filed under your own PaRRVA enrolment. Another tenant on the same platform can name and price their segments completely differently; the PaRRVA category underneath each one stays fixed, which is what keeps the regulatory classification correct no matter how the plans are packaged.

20Bug report & fix approval

Sidebar → Bug Report (Platform B2B section) — upload a screenshot, add a description, and track your ticket.

From Bug Report in your admin sidebar (/admin/support-tickets.html): describe the issue, attach up to 5 screenshots (PNG/JPEG/GIF/WEBP), submit. Your org only sees its own tickets; the platform owner sees all.

• B2B admin: submit a ticket → wait → confirm once it's fixed, or reopen it if it's still broken.
• Platform owner: approve/reject from the Fix Approval Queue → an agent session picks up the ticket → marks it fixed.

21Admin portal — what every page does

The sidebar tabs you'll see — a B2B tenant gets the same practice tabs as a B2C admin, plus a Platform (B2B) section (User Guide, Bug Report, Billing, etc.).

Interactive tour: b2b-admin-tour.html — har page slide-by-slide.

22Sales CRM (Leads) — what to look at, and what it means

Sidebar → 📞 Sales CRM (Leads). This is the prospect side of your practice: the people your team is calling who have not paid you yet. Client Master (Logs) is the other side — your existing paying clients. A lead becomes a client only through the normal Sign → KYC → Payment flow; the CRM never creates a client behind that flow's back.

Open it in the morning — what to look at, in order

The Dashboard tab is a row of counters. Read them in this order, not left to right:

Below the counters, the Conversion Funnel by Source shows total → contacted → interested → converted → lost, and a conversion % per source. A source with plenty of leads and a 0% conversion rate is calling time being spent for nothing.

What each lead status means, and when to move a lead to it

Converted, Not Interested and Lost drop out of the follow-up queue automatically — a closed lead never keeps resurfacing in a calling list.

What a telecaller sees vs what you see

The Sales CRM reuses your existing Admin/Moderator roles — there is no separate permission system to learn. It is the same page, filtered:

Why they differ: a telecaller should be able to work their own book fully — log calls, move statuses, clear their queue, convert a lead — without being able to move work around or see everyone's money. Nothing breaks for them; the revenue section simply is not there.

Logging a call — the one habit that matters

Open any lead to get its drawer, then Log a Call: Outcome (Connected / No Answer / Busy / Wrong Number / Switched Off), duration, "Move status to", "Next follow-up", and what happened on the call. One save does all of it — the call is recorded, the status moves, the follow-up is scheduled, and the counters update.

Call duration is self-reported. RA OS has no telephony integration and deliberately isn't getting one, so treat it as an honest manual note, not a measured figure.

Every lead also has an Activity Timeline — an append-only record of every call, note, status change, reassignment, import and conversion, with who did it and when. For a SEBI-registered firm this matters: "who moved this lead to Converted, and when" must always be answerable.

Converting a lead into a client

There are two kinds of sale, and they convert differently.

Convert to Client (a subscription sale) creates the client through your normal Client Master flow — the same Add Client that page uses, including your plan and client-cap checks — then links this lead to it so the sale is attributed to the right telecaller. Sign, KYC and payment still happen afterwards exactly as usual; nothing is skipped.

Convert to Course Sale (an Educational CMS sale) works differently, and the difference is deliberate. A course buyer becomes an Educational CMS student — a separate, lighter record with no PAN and no KYC. They are not an advisory client and are never counted as one. The student must sign up themselves: the sign-up needs a password only they choose, an email code only they can read, and a mentorship agreement only they can sign, so nobody can create that record on their behalf. The panel gives you a course sign-up link with their details pre-filled — send it, and once they have signed up and paid, come back and Link Course Sale to attribute it. Linking never creates a student, an enrolment or a payment; it only connects two records that already exist.

A single sale can only be attributed once — if another lead is already linked to that client or that course student, the link is refused rather than crediting the same money to two telecallers.

Importing a list of prospects from Excel — and what happens to duplicates

Import / Export tab (admin only). Download the Sample Template first: a blank sheet with exactly the headers the importer understands, plus a "How to use" sheet.

• Only Name and Mobile really matter — everything else is optional, and header names are matched loosely ("Mobile", "Mobile No", "Contact Number" all work).
• Pick a default Source, optionally assign the whole sheet to one telecaller, then upload — .xlsx or .csv, up to 10 MB and 5,000 rows per file.

How a duplicate is decided: by mobile number, within your own organisation only. The number is reduced to its digits first, so +91 98765 43210, 098765-43210 and 9876543210 are all treated as the same person. A number already in your CRM is skipped — nothing is created and nothing is overwritten — so re-uploading the same sheet is safe rather than destructive. The rule is enforced by the database itself, not just checked in code, so two people uploading the same sheet at the same moment still cannot create two copies. One RA's leads are never compared against another RA's: every organisation's CRM is entirely its own.

This is not just tidiness — two telecallers ringing the same person from two rows is a real DND and annoyance problem, not a cosmetic one.

Reading the import result:

The result panel also lists the first rejected rows with the reason for each, so you can see exactly which row dropped and why.

Undo: Import History lists every upload, and you can delete a whole batch — but only while none of its leads have been called. Once even one call is logged against a lead from that batch, the bulk delete is refused, because deleting the lead would destroy a real call record. Remove those individually if genuinely needed.

Duplicate Check (same tab) shows two things: leads sharing an email address, and — the one to act on immediately — leads whose mobile number already belongs to one of your existing clients. That means your team is about to cold-call somebody who already pays you. Clear those before the calls go out.

Adding a lead by hand behaves the same way: if the number already exists, you get a message naming the existing lead instead of a silent second copy.

Cross-Sell — working your existing clients

The Cross-Sell tab lists your active and expired clients as candidates for a higher plan, straight from Client Master — the CRM never copies a client into its own tables, so there is never a second, worse copy of a real client record. Opening an opportunity creates a thin record pointing at that client; calls against it are logged in exactly the same way as a lead call, so one leaderboard covers all of your team's calling work.

The revenue figure — what it counts, and what it does not

The Revenue Breakdown (admin only) is read live from two ledgers, and the Sales CRM stores no money figure of its own — there is deliberately no "deal value" field anywhere in it, so nobody can type a number that reaches a revenue view.

What it counts:

• Subscription revenue — payments with status paid and source app, from your Payments ledger.
• Course revenue — Educational CMS enrolments with payment status paid, from your Course Enrollments ledger. That money is collected into your own dedicated educational payment account, kept separate from your client-payment account — the CRM only reads it, never moves it.
• Both use the exact same filters your platform revenue-share invoice is calculated from, and your invoice is charged on the two added together — which is exactly why both are counted here. The same sale is never counted two different ways in the two places.
• Every payment mode — UPI, Razorpay, PayU, PhonePe, Cashfree, and anything added later. It reads the payment-mode column rather than a fixed list, so a new gateway starts counting the day it is first used. The "Payment Mode" table shows the real mix, so you can check it rather than assume it.

Every breakdown — by payment mode, by month, by lead source — splits Subscription and Course side by side with a combined total, so you can always see which of the two businesses a number came from. There is also a "Course" table showing revenue per course, alongside the "Plan" table for subscriptions.

What it does NOT count — just as important:

• Any client or student the CRM never touched. It only counts people a converted lead points at. Self-signups, walk-ins, and everyone who predates the CRM are all real, billable revenue that simply is not sales-team-attributed. This figure is therefore always smaller than your total revenue, by design — it answers "what did my calling team produce", not "what did my practice earn".
• Imported/migrated historical payments — shown separately as "Imported history (not billable)", never blended into a this-month figure.
• A converted lead with no payment record and no paid course enrolment — it honestly counts as ₹0 rather than an invented figure.

Refunds — and one honest gap. "Net (matches invoice basis)" is the figure directly comparable to your invoice; "Gross (before refunds)" and "Refunded" sit next to it, and per-telecaller figures on the leaderboard are net of refunds, so nobody is credited for money the business gave back. The gap: subscription refunds are netted out, course refunds are not — course enrolments have no refund field at all, so a refunded course sale still counts in full here and on your platform revenue-share invoice. Both numbers are wrong in the same direction, which is why the page states it plainly instead of quietly absorbing it.

Two more numbers worth reading together: Payments / Enrolments matched against your conversion count (conversions climbing while matched payments and enrolments don't means sales are being marked converted without money actually arriving through RA OS), and Revenue by Lead Source — which answers the question a lead count never can: which source actually turns into money, and therefore whether cold calling is worth it next to referrals.

Finally, on the Team Leaderboard: a telecaller with plenty of calls but no conversions is a coaching or script problem, not an effort problem. Read their call notes before you read the leaderboard.

23. Frequently asked questions

Recommended for compliance — the shared platform account is only meant for getting started; a B2B tenant should configure their own.

Strongly recommended for B2B tenants — client e-sign and KYC must run under your own SEBI registration, not another RA's shared account. Settings has dedicated sections for each.

No. The platform owner approves the ticket first; only then does an agent session implement the fix. This is a zero-downtime discipline — sacred flows (onboarding, payments, trade dispatch) are never touched without approval.

Yes — it's a paid add-on (whitelabel). Enable it in Settings → Add-ons, then follow the steps on the Domain & Microsite page.

No — Valid UPI is a free alternative, and you can enable one or both. Custom/other payment modes may be added in future.

You'll be notified and can re-upload corrected documents for another review.

Yes — the Data Migration page accepts a CSV/Excel export from any prior software (clients, plans, and historical payments), with a column-mapping step so it works regardless of the source system's format.

Enter your own PaRRVA credentials in Settings, then switch on the "PaRRVA Verified Performance — Public Display" toggle. It's off by default, and only shows real data once PaRRVA has enough trade history.

Yes — the RA-XV main exam mock test and its CPE renewal mock test at /nism-prep.html are fully public and unlimited: no signup, no login, no payment, and no cap on retakes. Each attempt draws a fresh random set of questions from the full bank. The paid NISM-XV + CPE Exam Prep add-on (Section 18) is only needed for full study-module access and the complete question bank for your team.

More questions? See the Full B2B FAQ (English/Hindi + PDF), the User Guide PDF, or contact the platform team.