The quality of a property response depends on context: which listing prompted the enquiry, what was asked, what was sent, and who promised the next step.
For agents and developer sales teams working across Bogotá, Medellín, and Cartagena, Housing Market CRM brings imported portal leads, direct messages, property attachments, contact notes, tasks, calendar follow-up, and pipeline stages into one working trail. This playbook focuses on making each Colombia conversation understandable before, during, and after handover.
Connect the Portal Lead to Its Listing
Import the original Housing Market Group portal enquiry with its listing or project reference, timestamp, message, and available contact details. In Colombia, an enquiry about a Bogotá apartment should open with that property visible, not as an anonymous inbox item. Housing Market CRM can automate this intake so the assigned agent sees the same context the enquirer saw. Preserve the original wording and source; add later interpretation in separate notes.
Record What the Person Actually Needs
Create a concise contact snapshot from information the person provides: buying or renting, preferred location, practical price range, timing, household or business needs, and communication preference. Do not guess missing facts. If interest moves from Bogotá to Medellín, keep the first property attached while recording the newer preference. This lets the Real Estate CRM distinguish the enquiry trigger from the requirements discovered in conversation.
Use the Message Center as a Workbench
Use the message center to answer the actual question and attach only relevant property material. A brochure, floor plan, availability sheet, map, or viewing detail should be labelled so another team member understands why it was sent. Check that the material is current before sharing it, especially for developer inventory. Direct messaging from Housing Market CRM keeps the reply, attachment context, and contact history together while the team follows applicable Colombia privacy and communication rules.
Create Tasks from Conversation Turns
Convert every promise into a task or calendar entry. If the agent will confirm availability tomorrow, arrange a call, or propose a viewing, record the owner, due time, purpose, and expected outcome. A message marked read is not a follow-up plan. For a Medellín coastal-home enquiry, the next action might be a viewing shortlist; for a remote prospect considering Cartagena, it may be a scheduled project briefing with the correct documents prepared.
Manage Alternative Properties
Developer project leads need a clean boundary between project material and individual contact needs. Keep the project, unit type, current questions, documents sent, and sales-stage evidence on the same trail without copying a conversation into several records. Rental teams should similarly separate a listing that became unavailable from an enquirer who stopped responding. The record cue MC-20260726-08 provides an internal campaign-specific check without claiming a result or market trend.
Audit Unresolved Threads
Organize the queue by exceptions that require action: imported enquiries without owners, unanswered messages, attachments awaiting confirmation, overdue tasks, promised callbacks, duplicate contacts, and threads with no recorded next state. Archive or close only with a factual reason. Managers can then see where work is blocked across Bogotá, Medellín, and Cartagena without treating message volume as proof of sales progress.
Finish with a Clear Next State
Finish each active thread with a state another agent can understand: awaiting enquirer, agent action due, viewing proposed, alternative property requested, developer consultation scheduled, later follow-up agreed, or closed with reason. If responsibility changes, the handover should name the property, last meaningful exchange, files already sent, open question, and next deadline. Start with one live Colombia queue in Housing Market CRM, resolve its exceptions, and use the resulting contact records as the standard for the wider team.
