How we built a missed-call recovery workflow for leasing

A missed leasing call is still an inbound inquiry. Recovering it sounds simple until duplicate records, prior follow-up, incomplete contact information, and opt-outs enter the picture.

Our first version of the problem was straightforward: identify missed calls and give the leasing team a way to follow up. The real work was making sure the workflow did not send the same message twice or treat every phone number as automatically eligible for follow-up.

Start with the call record

We export the relevant inbound call records and normalize each phone number into a consistent format. That lets us compare the number against earlier calls, existing prospects, prior messages, and suppression records.

Normalization sounds minor, but it prevents the same number from appearing different because of punctuation, country codes, or formatting. The workflow should not create a new prospect just because one system stores "(609)" and another stores "+1 609."

Check before creating or contacting

For each missed call, the workflow asks several questions:

• Is this a valid phone number?
• Does it already belong to a prospect?
• Did the team already respond to this inquiry?
• Is there a recorded opt-out or other reason not to text?
• Is the proposed message consistent with the context and scope of the inquiry?

If the record is uncertain, it goes to a person. Automation should not fill in missing consent or contact history with an assumption.

Lock the batch before sending

Duplicate protection needs to work even if someone reruns the job. We assign each eligible record a durable identifier and lock the batch before any follow-up begins. Once the system creates the message or task, it records the result against that identifier.

A rerun can then distinguish a new record from one already processed. That is safer than relying on an operator to remember which row was completed during the last run.

Keep the message narrow

The follow-up refers to the person's recent inbound leasing inquiry and gives them a simple way to continue the conversation. It should not turn a missed call into an unrelated marketing sequence.

The process also needs a clear opt-out path and a suppression list that every future run checks. If someone asks us to stop, that request must carry across the communications stack rather than living in one employee's inbox.

Consent requirements depend on the type of message, the technology used, the surrounding facts, and applicable law. An inbound call should not be treated as unlimited permission for future marketing. The FCC's rules address consent for certain automated calls and texts and require reasonable revocation requests to be honored. We designed the workflow to preserve the contact basis, recognize opt-outs, and escalate uncertain cases for review. Operators should have their own counsel review their use case.

Create the prospect and the task together

When follow-up is appropriate, the workflow updates or creates the CRM record and assigns the next action. The audit history keeps the original call, the eligibility checks, the message or task created, delivery status, and any response.

That history matters when a carrier rejects a message, a prospect calls again, or a leasing agent needs to understand why the record exists. It also gives the operator a way to review the process instead of trusting that it ran correctly.

The useful control points

A practical missed-call workflow should have a few non-negotiable controls:

1. Normalize and match the phone number.
2. Check prior contact and suppression history.
3. Prevent duplicate processing across reruns.
4. Keep the follow-up tied to the inbound inquiry.
5. Record delivery, responses, opt-outs, and the next owner.
6. Send uncertain records to a person.

The point is not to contact every missed caller automatically. It is to recover legitimate inquiries without losing the controls that protect the prospect and the operator.