Your CRM Should Help You Keep Promises

Start with the promise

A contact list is not the same as follow-through.

You can have hundreds of names in a CRM and still forget the one thing someone asked you to send. The useful question is not how many contacts you have. It is whether you can see what needs to happen next.

As I work on implementing FollowKind CRM, I want it to support a simple habit: remember the person, keep the promise, and make the next conversation relevant. This is the workflow I want to build around, not a claim about features already available or results I have achieved.

The tool should reduce the work of remembering. It should not replace the judgment involved in deciding whether a message is useful or welcome.

A useful contact record

Write enough to help, not everything you heard.

• Context: How you know the person and the housing question they actually raised.
• Commitment: What you agreed to do, stated as a specific action.
• Timing: When that action is due and whether another check-in was agreed.
• Contact preferences: Their preferred channel, relevant permission, and any request not to be contacted.
• Outcome: What you delivered and whether anything remains unresolved.

Keep notes factual, relevant and respectful. Avoid collecting unnecessary sensitive details. Knowing someone socially is not a reason to add them to every marketing list. Handle outreach, storage and permissions according to your broker's policies and applicable requirements.

If your CRM does not support a particular field, a clear note and a dated task can still support the habit. Start with the workflow before adding automation.

Fictional example

A question about next spring.

A former coworker mentions that they may want to buy next spring. They are not ready for a property search, but they want to understand how to prepare.

The first task is to deliver the checklist—not to launch a campaign. If they want another conversation, agree on a useful time. If they do not, respect that answer.

Once the checklist is sent, record that it was delivered. Leave a future task only when there is a genuine reason for one.

The weekly review

Look for loose ends, not just new leads.

• Which promises are due or overdue?
• Who is waiting for information from me?
• Which notes are missing a clear next action?
• Which tasks no longer make sense?
• Have contact preferences or permissions changed?

Start with the time-sensitive commitments and the people waiting on you. A person who is not moving soon can still deserve a prompt answer. Review the system without turning relationships into a scorecard of someone's worth.

For now, useful measures are promises completed, overdue tasks resolved and fewer forgotten details—not a guarantee of referrals or transactions.

Try it this week

Begin with three conversations.

Choose three recent conversations. For each, record the relevant context, identify any promise you made and give the action a date. Complete one outstanding promise before adding another feature to your system.

Then ask: did the record help me follow through, or did it create more work? Keep what helped and simplify what did not.

Put it to work

Make the review small enough to finish.

1. Open three recent records.Replace vague tasks like “follow up” with the actual promised action.
2. Check the due date and preference.Confirm how the person wants to hear from you and whether the task is still appropriate.
3. Close one commitment.Deliver what was promised, record the outcome and leave a future task only when there is a useful reason.

At the end of the week, count promises completed and questions still waiting for answers. Use the result to simplify the workflow, not to score someone's worth.