Frequently Asked Questions

First Prev show 3 of 231 Next Last

Support needs traceable internal Credit Ledger and module records to resolve safely. OTP/PIN/password should never be shared.
  1. Use official Koovira wallet/add-money page for recharge only
  2. Use KooviraCredit wallet inside modules for transaction confirmation
  3. Keep wallet transaction id and module reference id
  4. Check escrow/hold/release/refund status
  5. Raise support ticket with proof if anything mismatches

Support should check society access, unit membership, user status, linked Koovira account, mobile number, resident role and any suspension/block audit records.
  1. Confirm user role and login account
  2. Open the relevant module/page
  3. Check current status, scope and permissions
  4. Collect reference id, screenshot and exact error
  5. Escalate to the responsible team if unresolved

Billing may involve `sm_invoices`, `sm_invoice_items`, `sm_payments`, society pricing settings and per-society overrides. Escalate platform payment mismatch to Billing and society charge dispute to society admin/PAdmin as applicable.
  1. Confirm user role and login account
  2. Open the relevant module/page
  3. Check current status, scope and permissions
  4. Collect reference id, screenshot and exact error
  5. Escalate to the responsible team if unresolved

Moderation should review content, author history, report reason, AI moderation logs where available and policy category before removing/restricting content.
  1. Confirm user role and login account
  2. Open the relevant module/page
  3. Check current status, scope and permissions
  4. Collect reference id, screenshot and exact error
  5. Escalate to the responsible team if unresolved

Moderation/PAdmin may review ownership documents, page roles, claim history, business contact, address and public evidence before changing or restricting the page.
  1. Confirm user role and login account
  2. Open the relevant module/page
  3. Check current status, scope and permissions
  4. Collect reference id, screenshot and exact error
  5. Escalate to the responsible team if unresolved

Users should report suspicious trust activity. Internal teams should review entity history, reviewer relationship, repeated IP/device/activity patterns, content quality and dispute evidence.
  1. Open the relevant Koovira page
  2. Check login, profile and selected city/pincode
  3. Read the status/message shown on screen
  4. Keep reference id and screenshot if money, safety or dispute is involved
  5. Raise support ticket if the issue is not solved

A Dating profile cannot be created without a valid date of birth confirming adult age. This keeps the dating space adults-only.

We request only the permissions the feature needs (sign-in, contacts, calendar, or content import) and store tokens encrypted. Disconnect anytime to stop data exchange.

You can re-publish imported content as Social, Professional, Business, Stories, Articles or Promotions. We only access accounts you personally authorise.

Reports and automated signals form a moderation case which may lead to removal or restrictions. Request a review and a reviewer will reassess it.