Logo
Endorsements
Property Endorse properties to help others make informed real-estate decisions.
Property Developer Endorse real-estate builders based on project quality, delivery, and service.
Property Agent Endorse agents’ professionalism, responsiveness, and service quality.
Property Owner Credibility Endorse property owners based on transparency, communication, and overall dealings.
Employer Endorse employers to help candidates assess company culture.
Dine/pub/bar/Restaurant Endorse food quality, service, ambiance, and overall dining satisfaction.
College/Institute Endorse educational institutions for quality, curriculum, and overall experience.
Store/Shop/Services Endorse stores and shops for quality, trust, and overall experience.
Product / Brand Endorse products or brands to help consumers choose better and trust smarter.
Services Endorse services for quality, reliability, and overall experience.
Endorsements Tag Cloud for profiles and entities (restaurants, properties, jobs).
Your voice matters : Real experiences create real trust.
Your feedback shapes better services, better businesses, and better experiences for all.
Endorse Now

More Dashboards

Endorsements
Top Property
Top Builder
Top Agent
Best Employer
Top Owners
Best Corporate House
Best College/Institute
Best Product / Brand
Top Restaurant
Top Store/Shop
Top Place to Visit
Best Services
Top Not Recommended
Must Be Avoided
Help
Claim Property
Claim Business
Report Issue
About Us
Contact Us

Frequently Asked Questions

First Prev show 38 of 231 Next Last

This FAQ is written for common Indian frontend usage patterns: mobile-first browsing, OTP login, Koovira Credits usage, add-money top-ups, pincode/locality discovery, trust concerns, screenshots for proof, and support escalation. Relevant frontend references: dashboard.php, feed.php, socialfeed.php.
  1. Check login and correct mobile number
  2. Check selected city, pincode, filters and internet connection
  3. Do not repeat wallet/booking submit buttons blindly
  4. Take screenshot with reference id and date/time
  5. Raise support ticket if wallet, escrow, safety or stuck status is involved

This FAQ is written for common Indian frontend usage patterns: mobile-first browsing, OTP login, Koovira Credits usage, add-money top-ups, pincode/locality discovery, trust concerns, screenshots for proof, and support escalation. Relevant frontend references: dashboard.php, feed.php, socialfeed.php.
  1. Check login and correct mobile number
  2. Check selected city, pincode, filters and internet connection
  3. Do not repeat wallet/booking submit buttons blindly
  4. Take screenshot with reference id and date/time
  5. Raise support ticket if wallet, escrow, safety or stuck status is involved

This FAQ is written for common Indian frontend usage patterns: mobile-first browsing, OTP login, Koovira Credits usage, add-money top-ups, pincode/locality discovery, trust concerns, screenshots for proof, and support escalation. Relevant frontend references: dashboard.php, feed.php, socialfeed.php.
  1. Check login and correct mobile number
  2. Check selected city, pincode, filters and internet connection
  3. Do not repeat wallet/booking submit buttons blindly
  4. Take screenshot with reference id and date/time
  5. Raise support ticket if wallet, escrow, safety or stuck status is involved

This FAQ is written for common Indian frontend usage patterns: mobile-first browsing, OTP login, Koovira Credits usage, add-money top-ups, pincode/locality discovery, trust concerns, screenshots for proof, and support escalation. Relevant frontend references: search.php, businesses.php, viewuserprofile.php.
  1. Check login and correct mobile number
  2. Check selected city, pincode, filters and internet connection
  3. Do not repeat wallet/booking submit buttons blindly
  4. Take screenshot with reference id and date/time
  5. Raise support ticket if wallet, escrow, safety or stuck status is involved

This FAQ is written for common Indian frontend usage patterns: mobile-first browsing, OTP login, Koovira Credits usage, add-money top-ups, pincode/locality discovery, trust concerns, screenshots for proof, and support escalation. Relevant frontend references: search.php, businesses.php, viewuserprofile.php.
  1. Check login and correct mobile number
  2. Check selected city, pincode, filters and internet connection
  3. Do not repeat wallet/booking submit buttons blindly
  4. Take screenshot with reference id and date/time
  5. Raise support ticket if wallet, escrow, safety or stuck status is involved

This FAQ is written for common Indian frontend usage patterns: mobile-first browsing, OTP login, Koovira Credits usage, add-money top-ups, pincode/locality discovery, trust concerns, screenshots for proof, and support escalation. Relevant frontend references: search.php, businesses.php, viewuserprofile.php.
  1. Check login and correct mobile number
  2. Check selected city, pincode, filters and internet connection
  3. Do not repeat wallet/booking submit buttons blindly
  4. Take screenshot with reference id and date/time
  5. Raise support ticket if wallet, escrow, safety or stuck status is involved

This FAQ is written for common Indian frontend usage patterns: mobile-first browsing, OTP login, Koovira Credits usage, add-money top-ups, pincode/locality discovery, trust concerns, screenshots for proof, and support escalation. Relevant frontend references: search.php, businesses.php, viewuserprofile.php.
  1. Check login and correct mobile number
  2. Check selected city, pincode, filters and internet connection
  3. Do not repeat wallet/booking submit buttons blindly
  4. Take screenshot with reference id and date/time
  5. Raise support ticket if wallet, escrow, safety or stuck status is involved

This FAQ is written for common Indian frontend usage patterns: mobile-first browsing, OTP login, Koovira Credits usage, add-money top-ups, pincode/locality discovery, trust concerns, screenshots for proof, and support escalation. Relevant frontend references: search.php, businesses.php, viewuserprofile.php.
  1. Check login and correct mobile number
  2. Check selected city, pincode, filters and internet connection
  3. Do not repeat wallet/booking submit buttons blindly
  4. Take screenshot with reference id and date/time
  5. Raise support ticket if wallet, escrow, safety or stuck status is involved

This FAQ is written for common Indian frontend usage patterns: mobile-first browsing, OTP login, Koovira Credits usage, add-money top-ups, pincode/locality discovery, trust concerns, screenshots for proof, and support escalation. Relevant frontend references: search.php, businesses.php, viewuserprofile.php.
  1. Check login and correct mobile number
  2. Check selected city, pincode, filters and internet connection
  3. Do not repeat wallet/booking submit buttons blindly
  4. Take screenshot with reference id and date/time
  5. Raise support ticket if wallet, escrow, safety or stuck status is involved

Login, OTP, Profile and Account is part of Koovira's core workflow. The main UI references are login.php, signup.php, otpverification.php, settings.php, profile.php. Support should identify the actor role, current status, exact reference id and whether the issue belongs to customer self-service, merchant operations, PAdmin governance, billing, moderation, or TechOps.
  1. open entry
  2. confirm login
  3. complete required profile
  4. perform primary action
  5. check status
2026 © TRISHARA VENTURES LLP