Frequently Asked Questions
Radar-style features typically depend on location, selected city/pincode, user interests, module availability and privacy settings. Results may differ by user role and local data density.
- Confirm user role and login account
- Open the relevant module/page
- Check current status, scope and permissions
- Collect reference id, screenshot and exact error
- Escalate to the responsible team if unresolved
Update location, check filters, allow browser location if comfortable, and try a precise pincode/locality. Support should check if location/pincode data exists for that module.
- Confirm user role and login account
- Open the relevant module/page
- Check current status, scope and permissions
- Collect reference id, screenshot and exact error
- Escalate to the responsible team if unresolved
Some transactional, safety or support records are not public Radar content. Public profile/listing/social activity may appear where module visibility allows.
- Confirm user role and login account
- Open the relevant module/page
- Check current status, scope and permissions
- Collect reference id, screenshot and exact error
- Escalate to the responsible team if unresolved
Koovira brings multiple local needs into one account: social feed, community, business discovery, services, ecommerce, classifieds, jobs, property, food, hotels, events, cab/bike, delivery, truck logistics, Koovira Credits, trust profile and support. The exact features visible to a user depend on location, role, module status and rollout.
- Open the relevant Koovira page
- Check login, profile and selected city/pincode
- Read the status/message shown on screen
- Keep reference id and screenshot if money, safety or dispute is involved
- Raise support ticket if the issue is not solved
Koovira uses one common account and connects it with module-specific workflows. Customers use frontend pages. Merchants use merchant setup, KYC, listings/orders/bookings and settlements. PAdmin manages approvals, moderation, pricing, policies, security and platform-level operations.
- Open the relevant Koovira page
- Check login, profile and selected city/pincode
- Read the status/message shown on screen
- Keep reference id and screenshot if money, safety or dispute is involved
- Raise support ticket if the issue is not solved
A user in a small city can still register, browse and create requests where available, but local results depend on serviceable pincodes, active merchants/providers, data availability and operational rollout.
- Open the relevant Koovira page
- Check login, profile and selected city/pincode
- Read the status/message shown on screen
- Keep reference id and screenshot if money, safety or dispute is involved
- Raise support ticket if the issue is not solved
Users should avoid duplicate accounts because Koovira Credits, trust, support tickets, KYC and activity history may get split. If mobile/email is wrong, update settings or contact support.
- Open the relevant Koovira page
- Check login, profile and selected city/pincode
- Read the status/message shown on screen
- Keep reference id and screenshot if money, safety or dispute is involved
- Raise support ticket if the issue is not solved
Policy handling varies by module. Koovira Credits debit/refund policies depend on order/booking stage. Trust and safety policies apply to profiles, posts, listings, endorsements, dating, chats and marketplace activity. Data retention may keep transaction/safety/legal records even if public data is hidden.
- Open the relevant Koovira page
- Check login, profile and selected city/pincode
- Read the status/message shown on screen
- Keep reference id and screenshot if money, safety or dispute is involved
- Raise support ticket if the issue is not solved
Support tickets connect user issues to CRM cases, participants, communications, assignments and module records. This helps support identify whether the problem belongs to billing, moderation, merchant operations, PAdmin or TechOps.
- Open the relevant Koovira page
- Check login, profile and selected city/pincode
- Read the status/message shown on screen
- Keep reference id and screenshot if money, safety or dispute is involved
- Raise support ticket if the issue is not solved
For payment cases include Credit Transaction id or top-up reference or Credit Transaction id. For fake/fraud cases include profile/listing/product/endorsement link and proof. For delivery/ride/booking cases include order, booking, trip or ticket id.
- Open the relevant Koovira page
- Check login, profile and selected city/pincode
- Read the status/message shown on screen
- Keep reference id and screenshot if money, safety or dispute is involved
- Raise support ticket if the issue is not solved
Quick Settings