Intake hub
Website forms, missed calls, WhatsApp notes, social messages, and spreadsheet leads are staged into one clear intake view.
Product
A lead recovery system your team can actually use each week.
Tarjun installs the operating layer between incoming enquiries and booked appointments: intake, reply guidance, follow-up ownership, board visibility, and weekly reporting.
What gets installed
Five connected parts, focused on booking recovery.
The system is not positioned as a chatbot. It is a practical follow-up layer for real staff and real appointment enquiries.
Response templates
Staff get approved reply drafts for common enquiry types, so first responses are faster and more consistent.
Follow-up sequence
Quiet leads are brought back with reminders, owner assignment, and a clear next action before they go cold.
CRM board
A simple board shows new, replied, booked, pending, and lost leads without forcing a heavy CRM migration.
Weekly report
Owners see missed enquiries, response speed, booked appointments, open follow-ups, and saved staff time.
Operating flow
From enquiry to owned next action.
01CaptureAll channels staged
02ReplyStaff-reviewed draft
03Follow upQuiet leads owned
04ReportLeadership visibility
Map lead sources
Calls, forms, WhatsApp, email, and social enquiries are mapped into one follow-up process.
Standardise replies
Common enquiries get reviewed response templates so staff are not starting from a blank page.
Recover quiet leads
Follow-up tasks keep pending leads visible until they book, decline, or need a later reminder.
Track every status
The board makes new, replied, booked, pending, and missed leads visible to owners.
Report weekly
The weekly report shows response gaps, recovered leads, booked appointments, and open tasks.
Installed system feel
Built to become the weekly operating screen for lead follow-up.
The board, queue, and report work together so staff know the next action and owners see the health of the pipeline.
Best first step
Start with the 3-point Lead Follow-Up Audit.
Send the lead channels, reply gaps, and follow-up process you want reviewed. The first output is a practical recovery checklist, not a backend integration.