Astrotalk Clone Features: What a Consultation Marketplace Includes
This page describes proposed scope for a build in this category, agreed in writing per project. Nothing here is a finished product; counts are specification inventory from the supplied materials, not implemented or verified by this preview.
Six people touch this platform - customer, astrologer, assistant, finance desk, moderator, operator. The money loop is the part to inspect first.
Feature Set by Role
All six roles read the same schema. Everything below is proposed scope.
The customer
Discovery by skill, language, price and rating, then chat, audio or video call, or a live stream, with every minute metered against a prepaid wallet and a mid-session top-up that does not drop the session. Messages are end-to-end encrypted with real-time translation, and the free kundali, guna milan, panchang and muhurta tools sit alongside as the reason to arrive at all.
The astrologer
KYC gating before the profile goes public, availability windows, a request queue with automatic rejection of stale requests, and paid profile boosting for visibility. Earnings settle through a commission waterfall, and withdrawals run over UPI, bank transfer or PayPal against a configurable minimum with withholding applied and PAN captured at request.
The assistant
Sub-accounts under a practitioner with their own permission set, so a busy astrologer can have someone else work the queue, answer chats or manage the schedule without handing over the earning account itself.
The finance desk
A commission waterfall resolving boost override, then the per-astrologer rate, then the system default, with an admin commission ledger written per event. Withholding at settlement with reports exporting to CSV and PDF, withdrawal approval queues, wallet bonuses issued singly or in bulk, and a conversion-rate snapshot on every transaction row.
The moderator
Data monitoring across chats and calls, block-keyword moderation on messages, two-sided review moderation between customer and practitioner, and approval of astrologer-created puja packages before they reach the catalog.
The operator
89 admin menu pages across 151 Blade views per the specification inventory, governed by team roles with per-page grants, sitting on 298 system flags in 47 groups. Section toggles, feature pricing, commission defaults, referral caps, withdrawal minimums and the withholding percentage are all form fields.
The profession vocabulary is a single token across more than forty routes, so relaunching the same deployment as a tarot, counselling or coaching marketplace is a flag change rather than a fork.
Proposed Build vs a Generic Script
Most routes to a consultation marketplace hold up until the first payout run. The Omnistu column is proposed scope, agreed in writing per project - not an implemented product.
| What decides it | Omnistu proposed build | Generic script - what to ask |
|---|---|---|
| How a minute is billed | Metered against a prepaid wallet before service | Ask whether billing happens before service or is invoiced after, and chased |
| Running out mid-session | Top-up inside the session without dropping it | Ask what happens when the balance empties mid-call |
| Practitioner commission | Boost override, then per-astrologer rate, then default | Ask whether commission is one global percentage edited in code |
| Tax on payouts | Withholding at settlement, CSV and PDF reports | Ask whether tax is a spreadsheet reconciled by hand |
| A second country | Twenty gateway configurations, currency per gateway | Ask whether a second currency means reopening the payments layer |
| Overnight demand | Ten wallet-metered AI verticals answer | Ask what answers a customer at three in the morning |
| Changing a price | A form field among 298 flags | Ask whether a price change is a release, and a developer |
| Source code | Proposed: full ownership, no runtime licence, no per-seat fee - confirmed in your written quote | Ask whether the source is limited, or encrypted |
How It Works, End to End
Every step is proposed to run server-side rather than in the client, which is what makes the money reconcilable afterwards.
1 - A free tool brings them in
Kundali with seven report sections, guna milan matching, panchang with geolocation, a muhurta finder across six purposes, and daily, weekly and yearly horoscopes across a twelve sign catalog. None of it is metered, because its job is to attract intent rather than to earn.
2 - They find a practitioner
Discovery filters on skill, language, price and rating, against profiles that only appear publicly once KYC has cleared. Availability windows decide who is reachable now, and paid profile boosting decides who surfaces first - itself a revenue line.
3 - The wallet is recharged
Money enters once, through any of twenty gateway configurations spanning India, the Gulf, Turkey, Africa, Europe, Latin America and the global rails. Each carries its own currency, symbol and test and live key pair, and every transaction stores a conversion-rate snapshot.
4 - The session is metered
Chat, audio, video and live stream all bill per minute against that balance, with media carried by Agora, Zego or 100ms behind one provider switch and an Exotel PSTN fallback dialing masked numbers. If the balance runs low the customer tops up inside the session rather than losing it.
5 - Or the AI answers instead
When no practitioner is online, ten wallet-metered verticals take the session: AI counsellors, a site-wide master bot, tarot, numerology, vastu, vision reading, transit analysis, paid ask-a-question, the remedy engine and paid AI remedy reports. Each debits the same wallet.
6 - The commission resolves and the practitioner is paid
An append-only ledger row lands per consumption event; the waterfall checks boost override, then the per-astrologer rate, then the system default. Withholding is applied at settlement with PAN captured at the withdrawal request, and disbursement runs over UPI, bank transfer or PayPal Payouts with bulk support.
The same balance also buys remedies from the AstroMall with tax-aware checkout, puja packages delivered over a live broadcast, course seats and gifts sent during a stream, each carrying its own commission treatment.
Every Feature Earns Its Place
Each row is here because a metered marketplace stops working without it, not because a competitor lists it.
| Module | Why it is in the proposed base |
|---|---|
| Prepaid wallet, metered before service | Billing after a consultation means chasing payment for advice already given. Metering against a balance that exists first removes the collection problem entirely. |
| Mid-session top-up | A session that dies on an empty balance loses the minute, the sale and usually the customer. |
| Commission waterfall | A single global percentage cannot express a promotional boost or a star practitioner's negotiated rate. Three resolution levels is the minimum that survives contact with real supply. |
| Conversion-rate snapshot per row | Reconciling a multi-currency month against today's rate produces numbers that do not match what happened. Storing the rate that applied is what makes the ledger auditable. |
| Withholding at settlement | Withholding calculated after the fact is a reconciliation project every quarter. Applied at settlement with PAN captured, it is a report rather than an exercise. |
| Ten metered AI verticals | Consultation demand arrives at three in the morning when no practitioner is awake. AI covers those hours instead of losing the intent. |
| 298 flags across 47 groups | Feature prices, commission defaults, section toggles and referral caps are the numbers your margin depends on. They belong in a form rather than in a deployment. |
| KYC gating before listing | A marketplace selling personal guidance carries reputational risk from its supply side. Verifying before a profile is publicly reachable is cheaper than removing it afterwards. |
Underneath sit 8 scheduler tasks and 6 queue job classes carrying horoscope generation, appointment and puja reminders, commission settlement and notification dispatch - none of which belongs in a web request.
The Technology Behind the Features
Deliberately unexotic, because the operator has to hire for it. Counts are specification inventory, not implemented or verified by this preview.
Application core
Laravel on PHP with MySQL, Blade templating and a Vite build: the supplied specification records 170 database tables with incremental migrations, 179 controllers and 133 models, 8 scheduler tasks and 6 queue job classes, with parameterized bindings across roughly 500 raw query fragments.
Surfaces and routing
Roughly 191 customer and astrologer website routes, roughly 363 JSON API routes under a JWT guard serving both Android builds, and roughly 552 admin routes behind session-based role access, rendering 89 admin menu pages across 151 Blade views.
Real-time layer
Provider-agnostic voice and video behind a single switch across Agora, Zego and 100ms, live streaming with RTMP fan-out and recording, an Exotel PSTN fallback dialing masked numbers, and Firebase Firestore carrying admin support chat - proposed external dependencies, not verified integrations.
AI layer
One provider interface with the provider, model and key held as system flags, so all ten verticals inherit a single switch between OpenAI and OpenRouter. Wallet metering is applied before every call, and history persists with PDF export.
Money and ledger
A dual-currency wallet operating in amount or coin mode across twenty gateway configurations, an append-only transaction ledger, a conversion-rate snapshot per transaction, the commission waterfall with withholding, and withdrawals over UPI, bank and PayPal Payouts.
Configuration and storage
A system flag store of 298 typed flags across 47 groups, a profession vocabulary swap reaching more than forty routes, 143 seeded languages with ten active app-side and five on web, five design sets with dark mode, and storage selectable per deployment across local, AWS, GCS and DigitalOcean.
The interesting engineering here is not the framework. It is the flag store and the ledger: typed flags mean pricing and packaging change without a release, and an append-only ledger with rate snapshots means a multi-currency month reconciles against the rate that actually applied.
Named Here Rather Than Discovered After the Invoice
This preview does not implement or verify any of these; the required work is scoped, tested and quoted with you.
Reported inventory: three of twenty gateways verified
The supplied specification records twenty gateway configurations with server-side payment verification on three - Tap, Sadad and PhonePe - as the template the rest are built against. We would rather say that than let twenty configurations imply twenty verified integrations.
Reported gap: no audit trail
The security review supplied with the specification records no authentication-event log and no admin-action log, so operator actions are not currently reconstructable after the fact. On a platform moving money this is the item we would schedule first, and the build work is scoped and quoted with you.
Reported inventory: five of twenty-five CRM modules
The specification describes twenty-five; five have functional implementations - a Customer 360 timeline, nine computed behavioural tags, health metrics covering lifetime value, retention and churn, a recommendation engine and a centralized notification engine. Lead management, pipelines, tasks and campaigns have no tables, models or routes yet.
Reported gap: test hooks recorded in the codebase
The security review supplied with the specification records a test OTP bypass and test contact hooks in the codebase. Removal and testing are required scope, quoted before work starts - not work already performed.
Nine outside accounts are yours
Recorded in the supplied specification: MSG91 for OTP, Agora, Zego or 100ms for real-time media, OpenAI or OpenRouter for the AI layer, Exotel for PSTN fallback, FCM and OneSignal for push, Firebase for admin support chat, Google Maps for geocoding, an astrology chart API, and a merchant account for every gateway you intend to run - proposed external dependencies, not verified integrations.
Proposed base scope
The supplied specification records end-to-end encrypted chat with participant authorization and key versioning, parameterized bindings across roughly 500 raw query fragments, an append-only wallet ledger with conversion-rate snapshots, role-based access across the admin pages, and both Android builds with their own store listings - all as proposed scope this preview does not implement or verify.
Frequently Asked Questions
What do the ten AI features actually do?
Proposed: AI counsellor personas with admin-authored system prompts, a site-wide master chatbot, tarot on a 78 card deck with single and three card spreads, numerology across Chaldean and Pythagorean systems, a vastu compass evaluating eight directions, vision reading from an uploaded photo, planetary transit analysis, paid ask-a-question routing between AI and a human astrologer, the remedy engine, and paid downloadable AI remedy reports. Each is priced and toggled independently and each debits the wallet.
Does it handle practitioner payouts and tax properly?
This is the part to inspect first, because it is where homegrown builds usually fail. Proposed: commission resolves through a waterfall - boost-active override, then the per-astrologer rate, then the system default - with an admin commission ledger written per event. Withholding is applied at settlement with PAN captured at the withdrawal request, reports export as CSV and PDF, and withdrawals run over UPI, bank transfer or PayPal with a configurable minimum and bulk support.
Can I run this in more than one country?
That is the design intent. Twenty gateway configurations cover India, the Gulf, Turkey, Africa, Europe, Latin America and the global rails, each carrying its own currency, symbol and test and live key pair. Add 143 seeded languages with ten active on the app side, per-market store listings for both apps, and a conversion-rate snapshot on every transaction. You still need a merchant account per gateway you intend to run.
What can the operator change without a developer?
Most of it, per the specification inventory: 298 system flags across 47 groups covering section toggles for chat, call, live and AI, feature pricing for every paid surface, commission defaults, promotional offers, referral rewards and caps, withdrawal minimums and the withholding percentage, currency and language, storage and streaming provider selection, rate limits, and the store links for both apps.
Is there a CRM, and how complete is it?
We will be precise rather than let the word carry more than it should. The specification describes twenty-five modules and records five with functional implementations: a Customer 360 view with a unified timeline, nine computed behavioural tags, customer health metrics covering lifetime value, retention and churn scoring, a recommendation engine, and a centralized notification engine. Lead management, sales pipelines, tasks and campaigns do not exist yet.
Do I get the source code and both mobile apps?
Proposed handover: the Laravel application, the customer web portal, the astrologer portal, the JSON API, the admin back office, the 170 table schema with migrations, and both Android builds - the customer app and the separate astrologer app, each with its own store listing and package name. The documentation suite transfers too, including the schema reference, the entity relationship document, the API collection, and the developer and security handbooks.
Independence and third-party names
Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Astrotalk. "Astrotalk clone" is used descriptively - it is how the software industry refers to building a platform with similar functionality, and how buyers search for it. Astrotalk and all other third-party names and marks are the property of their respective owners, referenced here solely to describe the category of software offered.
Discuss your scope by message
Tell us which paid surfaces you would switch on at launch - metered consultations, AI verticals, the remedy marketplace - and which markets you are launching in. We reply by email with a scoped proposal - no calls required, no phone numbers collected.
