Leads and pipeline
Create a lead from any chat and move it from New to Won or Lost on a list or board. Each lead records its budget band, configuration, purpose, timeline, location and first-touch source.
A shared WhatsApp inbox, a lead pipeline, site visits and reports, built around the problems real-estate sales teams have with WhatsApp.
Problem: leads stuck on one agent’s phone
Every chat sits in one queue, so an enquiry can't wait unseen on one agent's phone.
Problem: nobody knows which leads went cold, or why
Create a lead from any chat and move it from New to Won or Lost on a list or board. Each lead records its budget band, configuration, purpose, timeline, location and first-touch source.
The AI records each visit request in the customer's own words. Staff confirm, move or cancel it on a week calendar, send an optional reminder, and log whether the visitor came.
Keep 13 types of fact per project, with every change saved as a version and a queue for stale facts. Photos need approval too, from floor plans to amenities.
Marketing templates go only to contacts who agreed, and every answer is stored as evidence. Quiet hours, an hourly limit and a 15-day cap per contact apply to each send. Include each project’s RERA details in your templates where your state requires them.
Give follow-ups an owner and a due time. Set a response-time target, and any chat past it shows as Reply overdue until a staff reply is accepted by WhatsApp.
See today, 7 days, 30 days or a custom period, filtered by source and project. Compare with the previous period, view leads by source, and export to CSV.
Problem: staff leaving with your buyer list
Works unassigned and own chats and leads, tasks and site visits.
Sees all chats and leads, assigns work, and reads reports.
Runs members, WhatsApp setup, project facts, templates and campaigns.
Holds every permission, including assigning owners and administrators.
Views leads, projects, tasks, reports and campaigns, without chats.
Phone numbers and message bodies are encrypted in the database, and numbers are masked for roles without full access. The server checks every request against the organisation and role, and an audit log is available to administrators.
Plans differ by message volume and support, and staff users are unlimited.