Frequently Asked Questions. 统一互联的运营层. 将机会转化为真实影响的可信流程。

CONSAI is a role-based operating ecosystem for agriculture, renewable energy, carbon markets, trade, finance and institutional collaboration. The public experience supports discovery and registration, while the protected intelligence backbone manages operational records, permissions, workflows and review steps.

The public website explains roles, solutions, marketplace opportunities and registration paths. Private identities, CRM records, farm data, documents, offers, orders, payments, deal rooms and administrative actions remain inside authenticated, permission-controlled workspaces.

No. Public profiles and listings are discovery surfaces, but the operating platform also supports CRM, RFQs, offers, orders, deal rooms, logistics, payments, project records, intelligence signals, carbon evidence and controlled approvals. Availability depends on role, plan, permissions and workflow status.

CONSAI is designed for international participation, subject to legal, sanctions, compliance, payment and operational restrictions. A country being selectable does not mean every service, payment method, partner program or commercial route is available there.

Public pages, selected insights, public marketplace summaries and exhibition content can be viewed without an account. An approved account is required for protected data, role workspaces, private documents, operational actions and direct engagement where applicable.

Authentication confirms who you are; authorization determines what you may access. A module can also require email verification, an approved account, a specific role, an active plan, a granted permission or completion of an onboarding step.

A business may operate across several functions, but access should reflect its verified responsibilities. Additional roles or modules may require review so that supplier, buyer, investor, partner, staff and institutional permissions are not mixed incorrectly.

Dashboards are role- and permission-aware. A farmer, supplier, Strategic Partner, investor, staff member and administrator receive different navigation, records and actions because they carry different responsibilities and data-access boundaries.

The public frontend and key protected workflows are designed responsively, and mobile access is available for supported journeys. Some data-heavy administration, mapping, reporting or document work is still easier on a larger screen.

No. Public descriptions show ecosystem capability, not universal entitlement. Actual access is determined by the live platform configuration, role, account status, subscription, permissions, geography and the stage of the relevant workflow.

Choose the role that best describes the responsibility you control: producing, buying, supplying, financing, investing, delivering services, coordinating institutions or developing a region. The Pricing Wizard and onboarding review help prevent a commercial company from being placed in an unsuitable role.

Typical information includes the farmer’s name, contact details, country and location, farm name, farm size, main crops or livestock, current products and expected harvest timing. Additional evidence may be requested before specific market, finance or carbon workflows are enabled.

A company should provide its legal or public name, business contact, country, role, products or services, operating coverage and intended use of CONSAI. Verification may also require registration documents, certifications, references, capacity information or authorized-representative confirmation.

Email verification reduces incorrect and unauthorized registrations and provides a controlled channel for account notices. It does not by itself verify the person, company, farm, products or commercial claims in a profile.

Some roles require administrative review before protected access is granted. The team may check role fit, contact quality, organization context, duplication, required documents and whether the requested permissions are appropriate.

An incomplete registration can be returned for correction or remain limited. Rejection means the requested account or role was not approved at that time; it does not create a right to platform access, commercial opportunities or reimbursement.

A partner invitation can attribute an onboarding path to an authorized Strategic Partner or campaign. Attribution helps operational reporting, but it does not automatically approve the new member, guarantee commission or transfer ownership of the member to the partner.

Role changes should be requested through support or the appropriate onboarding review. They may require new information, documents, pricing or permissions because role changes can alter access to sensitive records and commercial actions.

The currently offered farmer pathway may be free where shown in the live pricing and registration interface. Optional paid services, third-party services, verification, project work or future commercial modules are separate and must be disclosed before commitment.

Accounts should not be shared or informally transferred. Changes to the authorized representative, ownership or responsible contact must be reviewed to protect data, permissions, documents, payment records and audit history.

Supported workflows can include farmer identity, farms, fields, locations, crops, cultivation records, activities, notes, machinery, production context, expected harvests and market demand. The exact fields visible depend on the enabled role workspace.

The platform includes location-aware records and map-data routes for fields, notes and other operational entities. Map accuracy depends on the coordinates and source data supplied; a map pin is not a legal land survey or proof of ownership.

Field workflows can display weather or forecast information where a supported data source and valid location are available. Forecasts are advisory data and should not replace local observation, agronomic judgement or official emergency warnings.

No. Plant intelligence, signals and educational content can support decisions, but they do not replace a qualified agronomist, laboratory analysis, veterinarian or locally licensed professional. Users remain responsible for decisions made on their farms.

No. Production and harvest data improve discoverability and matching, but demand, quality, quantity, timing, logistics, pricing, documents and counterparty approval still determine whether a transaction progresses.

A farmer demand records a requirement such as inputs, machinery, services, finance, irrigation or market access. It can be matched with relevant providers or opportunities, but a match is a lead for review rather than a confirmed contract.

Supported machinery workflows allow authorized users to create and manage machinery assets and service context. Availability, location, pricing, operator requirements, insurance and condition must be confirmed between the relevant parties.

The platform includes batch, compliance-event and trace routes that can organize evidence and QR-linked records. Traceability is only as reliable as the submitted data, controls and verification process; it is not automatically a certification.

Yes, a cooperative or authorized partner can coordinate structured onboarding where the required authority, consent and data quality are present. Each farmer record should remain attributable and reviewable rather than being treated as an anonymous total.

No. Registration alone does not transfer ownership of land, crops, production, carbon rights or future income. Any project-specific rights, mandates or benefit-sharing terms require a separate, clearly defined agreement.

The Marketplace is a structured discovery and transaction pathway for agricultural supply, inputs, machinery, services, energy requirements, projects and selected climate opportunities. Public summaries remain separate from protected commercial details and counterparties.

Listing creation is available only to authorized accounts with the correct role, plan and permissions. Draft, preview, publish, unpublish, archive and administrative review states help prevent uncontrolled public publication.

No. Publication or administrative review means the listing passed the applicable platform workflow; it is not a guarantee of title, quality, legality, availability, price, creditworthiness, delivery or investment performance.

Use the request form on that listing page. The listing title, reference, category and URL are attached automatically so the CONSAI team can identify exactly which opportunity, product or project your request concerns.

A Request for Quotation describes a buyer or project requirement, including relevant scope, timing, location, quantity or technical context. Suppliers can respond through the appropriate workflow, but submission does not guarantee acceptance.

The offer can be reviewed against the requirement and, where enabled, accepted into a controlled transaction path. Commercial terms, documents, counterparties, logistics, payment and compliance still require confirmation.

A Deal Room is a protected workspace for selected parties to coordinate documents, terms, milestones, delivery confirmation and disputes. Access is permission-based; entering a Deal Room does not itself create a completed or legally binding transaction.

Protected contact controls reduce scraping, unsolicited outreach and premature disclosure. Contact can be released only through the relevant role, review or transaction stage rather than being exposed in every public listing.

Not necessarily. A listing can contain indicative, unit, negotiated or time-sensitive pricing. Taxes, delivery, inspection, payment fees, currency, quality, quantity and contract terms can change the final commercial amount.

The operating platform includes dispute and resolution workflows for supported deals. CONSAI can structure records and review steps, but legal rights, governing law and remedies depend on the applicable agreements and jurisdiction.

Energy OS connects renewable-energy demand, suppliers, EPC companies, manufacturers, project developers, financiers and institutions with agriculture and infrastructure use cases. It supports structured discovery, RFQs, project context and finance-readiness workflows.

Relevant roles include solar manufacturers, EPCs, installers, battery and storage providers, irrigation-power providers, O&M companies, energy consultants, developers, utilities, investors and climate-finance institutions. Each organization must use the role matching its actual capability.

A useful energy RFQ should state location, load or capacity, application, grid context, operating hours, storage needs, timeline, budget stage and available site or technical documents. Better input produces better qualification and fewer irrelevant responses.

No. A project record organizes the opportunity and evidence. Technical feasibility, land or site rights, permits, grid access, offtake, financing, equipment specifications and counterparty capability require separate review.

The platform can structure finance-readiness information and connect relevant parties where available. It does not guarantee credit approval, investment, grant funding, insurance, bankability or financial close.

Authorized supplier accounts can present products, capabilities and supporting documents through enabled listing and profile workflows. Certifications, warranties, production capacity and project references remain subject to review and must not be overstated.

Common intersections include solar irrigation, cold-chain power, processing, storage, greenhouse energy, farm electrification, battery systems and productive-use projects. The shared platform helps connect site demand with suppliers, finance and implementation partners.

No. Calculators and finance signals are planning aids based on the inputs and assumptions provided. Real performance depends on resource conditions, equipment, degradation, tariffs, financing, maintenance, operations and site-specific engineering.

Relevant review can include legal identity, geography, technical capability, certifications, insurance, references, capacity and submitted documentation. Platform visibility does not replace local licensing, engineering review or contractual due diligence.

Fees depend on the active membership, listing, referral, service or transaction arrangement presented to the parties. No commission should be assumed unless it is shown in the live pricing, order or applicable agreement.

It helps organize project intake, baseline context, evidence, monitoring records, buyer or verifier pathways and climate-finance readiness. It separates project preparation from independent validation, verification, registry issuance and commercial status.

No. Eligibility depends on methodology, additionality, baseline, ownership, monitoring, leakage, permanence, safeguards, validation, verification, registry rules and project performance. Registration or data collection alone creates no credit.

MRV means Monitoring, Reporting and Verification. The platform can support monitoring and evidence organization, while independent verification and registry decisions must be performed by appropriately qualified external bodies where required.

Depending on the project, evidence may include boundaries, participant records, land or activity rights, baseline data, practices, geospatial information, monitoring events, documents, photos, calculations and audit history. Required evidence depends on the selected methodology and standard.

Ownership cannot be determined from platform registration alone. It depends on applicable law, land and activity rights, contracts, project structure and benefit-sharing agreements; these must be resolved before credits are claimed or transferred.

The ecosystem can support buyer and project matching based on mandate, geography, stage, methodology and evidence readiness. A match does not mean the project has issued credits or that price, volume, delivery and claims have been agreed.

It is an internal record used to organize asset references, ownership events, balances or retirement requests within supported workflows. It is not automatically a public blockchain token, registry account or legally recognized carbon credit.

No. A digital token or internal asset record cannot replace methodology compliance, validation, verification and registry issuance. Digital representation should only follow clear rights, evidence and an authoritative underlying asset status.

Retirement is the process used to take an eligible issued unit out of circulation for a stated claim or purpose. A platform request remains subject to ownership, registry, authorization and review requirements before it can be treated as completed.

No. Revenue depends on eligibility, verified performance, issued volume, project costs, benefit sharing, buyer demand and market price. Farmers should understand responsibilities, deductions, timing and risk before joining a project.

Use the live registration and Pricing Wizard interfaces. Prices, billing periods, setup fees, included modules and add-ons should be taken from the current checkout or written proposal rather than from an old presentation or message.

Available payment methods are shown in the live checkout or invoice for the relevant order and country. Where enabled, online payment and administratively confirmed bank transfer follow different confirmation steps; never send funds to unverified instructions.

A bank transfer is not treated as paid merely because a receipt was uploaded. The finance or authorized administrative workflow must match the payment to the order and confirm cleared funds before access, commission or fulfillment is finalized.

Supported order workflows include invoice generation and payment-status records. The legal issuer, tax treatment, currency, buyer data and final amount must match the relevant company and transaction.

Refund, reversal and cancellation treatment depends on the payment method, order status, delivered services and applicable terms. Related access, commissions, passes or benefits may also need reversal through controlled administrative workflows.

Do not assume that a Deal Room or protected payment workflow is regulated escrow. Where a licensed payment or escrow provider is involved, its identity, terms, jurisdiction and release conditions must be shown explicitly.

No. Platform information is for structured discovery and review, not personal financial advice, an offer of securities or a guarantee of returns. Investors must perform their own legal, financial, technical and commercial due diligence.

Finance readiness organizes the information a lender or investor may require, such as sponsor context, use of funds, milestones, cash flow, contracts, risks, security and evidence. It does not mean that financing has been approved.

Commission is created only when the configured commercial conditions are satisfied and recorded by the platform. Registration volume, an invitation, an expression of interest or an unpaid order does not by itself create an earned commission.

Eligible earnings can progress through payout-method, approval, settlement and paid-status workflows. Identity, payment details, thresholds, reversals, compliance and the underlying transaction may be reviewed before funds are released.

A Strategic Partner develops qualified regional relationships, introduces suitable organizations, supports role-correct onboarding and progresses accountable commercial or institutional opportunities. The role is performance-focused and is not an employment relationship.

Not unless a separate written and authorized arrangement states otherwise. Standard Strategic Partner participation does not create automatic salary, field-cost reimbursement or payment per registration; commissions depend on qualifying revenue under the applicable rules.

No. Attribution records who supported an introduction, but members remain independent platform participants subject to their own rights, consent and account status. Attribution must not be represented as ownership of people, data or future revenue.

Authorized partners can access lead views configured for their role and assignment rules. They should only use the data for legitimate CONSAI activity and must not export, resell or contact suppressed, invalid or unrelated records.

A usable lead needs sufficient organization identity, role relevance, country or market context and a legitimate professional contact route. Missing, invalid, unsafe, duplicate or suppressed contact data should prevent outreach until corrected.

No. AI can discover, score, classify and enrich potential leads, but source quality, contact validity, relevance, suppression status and compliance rules must be checked. A high score is a prioritization signal, not proof that the lead is accurate or interested.

Outreach should be role-relevant, professional, accurate and sent only to a legitimate business contact under the applicable rules. Every message should identify CONSAI, explain the reason for contact and provide a simple opt-out route.

Replies should be recorded against the correct CRM lead, reviewed for intent and progressed through a meeting, proposal, qualification or suppression action. A reply must not be lost as a detached email without lead history.

Lead identity should be checked using organization, domain, email and relevant source data before a new record is created. Duplicate records can fragment outreach history, assignments, opt-outs and reporting, so they should be merged or suppressed through controlled processes.

Yes. Access can be suspended or terminated for inactivity, misuse, false claims, data abuse, security concerns, policy breaches or failure to meet the applicable agreement. Retention or deletion of records remains subject to legal, audit and operational requirements.

The Community Hub supports profiles, posts, discussions, messaging and ecosystem interaction. It is a collaboration layer and does not replace the trusted operating record for CRM, orders, payments, permissions or formal commercial workflows.

Where account synchronization has been completed, a member may receive corresponding Community access. Synchronization and account status must still be checked; access to the main platform does not guarantee that every connected service account was created successfully.

Members can manage supported profile fields and profile media within the Community interface. File type, size, image dimensions, account permissions and storage configuration can affect upload success.

No. Member posts represent their authors unless clearly published as an official CONSAI notice. Commercial claims, offers, project statements and advice should be independently reviewed before reliance.

CONSAI Cloud is the connected collaboration environment used for authorized files, calendars, contacts, maps, tasks, boards, mail and institutional documentation where configured. It supports operations but does not replace the protected core database.

Cloud access is limited to authorized administrators, staff and selected Strategic Partners or collaborators according to operational need. Farmers, leads and other contacts can be represented as records without receiving Cloud login access.

A contact card stores professional or operational information for authorized users. A Cloud user account grants login and app access, which is a separate and more privileged status.

Pins visualize contact, farmer, partner, lead or project locations where usable coordinates exist. They are operational references, not proof of residence, land boundaries, legal ownership or field-survey accuracy.

The booking interface states the operative time zone, and calendar invitations should preserve the event time zone for conversion by the recipient’s device. Users should confirm the displayed zone and UTC offset before joining.

Not necessarily. Connected records can be transferred by scheduled or controlled synchronization jobs, and each system retains its own access rules and data model. Temporary differences should be investigated rather than assumed to be data loss.

The operating model uses authenticated accounts, role-based permissions, protected routes, purpose-based access, encrypted web connections, administrative controls, backups and audit-aware workflows. No system can promise absolute security, so access remains limited to what is operationally required.

Public profiles, approved listings, booth information and safe summaries may be visible where the user or workflow authorizes publication. Sensitive contacts, identity records, documents, payment data and private operational context should remain protected.

CONSAI does not present unauthorized sale of personal farmer or member data as a platform service. Data must be processed for defined ecosystem, contractual, compliance or operational purposes under the applicable privacy terms and permissions.

You can contact CONSAI to request access, correction or deletion where applicable. Some records may need to be retained for contracts, payments, fraud prevention, legal obligations, disputes, security or audit history.

Use a unique password, keep credentials private, verify the domain before signing in and report unexpected messages or access immediately. Do not send passwords, one-time codes or payment credentials through ordinary email, chat or Community posts.

No. Upload controls and document intelligence can organize or inspect files, but they do not prove authenticity, legality or accuracy. Sensitive files should be shared only in the correct protected workspace with the minimum required audience.

No. AI output can be incomplete, outdated or incorrect and must be checked against source evidence, current market conditions and professional judgement. High-impact financial, legal, agronomic, technical and compliance decisions require qualified human review.

Supported modules maintain timestamps, status changes, activity records and audit-oriented events for accountability. Audit visibility depends on the module and permission; ordinary users may not see every administrative or security record.

State the affected page or module, account email, time of the issue, device or browser, exact error text and the steps that caused it. Attach a safe screenshot if useful, but remove passwords, payment credentials, identity numbers and unrelated personal data.

Stop the affected action, preserve relevant evidence and contact CONSAI through the official support channel immediately. Do not publish suspected vulnerabilities, credentials or private member data in Community posts or public messages.