Turn business data into a useful customer review list

Build around the decision employees make. If account managers spend Monday morning checking service history, quotes, schedules, and messages to decide whom to contact, a connected review list can bring that evidence together.

The list should show why a customer appeared, who owns the next step, and what happened after review. Cass & York develops the data connections and interface behind that sequence.

Monday morning begins with two customers

In this fictional review, Cedar Court's Building C was last serviced on April 1. Its six-month planning interval came due on October 1. Building A was serviced recently, but that does not settle the need at Building C.

Harbor House also has an older service date. Its recent call note and booked visit change the decision.

Cedar Court / Building C

• Evidence in the connected records: Service CC-07; planning interval due; no visit booked for that building.
• Review result: Check the quote and contact history before choosing a follow-up.

Harbor House

• Evidence in the connected records: Service HH-08; recent call HH-C4; booked visit HH-V9.
• Review result: Exclude from new outreach and show the existing booking.

A list based only on service age would flag both. The schedule makes Harbor House a false positive.

Cedar Court needs judgment too. An open quote for another building might be relevant to the conversation without covering Building C. The account manager needs to inspect it rather than have the list treat every quote on the customer account as interchangeable.

Open the candidate before assigning the call

The manager selects Cedar Court and sees the service, interval rule, related quotes, scheduled work, and recent contact. A contact restriction stops an outreach suggestion.

If the phone import is stale, the screen says so. “No recent contact found” describes the available records; it cannot establish that nobody called.

The manager might decide to ask about Building C, wait for a response to an existing quote, or close the candidate with no action. Each outcome needs a reason and an owner.

Once a follow-up is assigned, the next Monday's review should show its existing status rather than create another task. A changed booking or new customer response can update the item. It should not erase the earlier decision.

Put rules and notes to different uses

A defined interval rule calculates when review is due. A scheduled visit can exclude a candidate. AI may help summarize what the customer said in notes.

The account manager still needs the underlying records when a suggestion is unclear. A planning interval identifies a reason to review, not proof that a customer is ready to buy.

For this proposed delivery, the account managers choose one recurring decision and confirm its eligibility rules. The connected list provides supporting records, assignments, outcomes, and source refresh dates. Testing includes an existing booking and an already-assigned follow-up before the list becomes part of weekly work.

Check whether the list earns its place on Monday

Measure how long users spend preparing the list, how many candidates they reject, and whether duplicate follow-ups occur. Compare similar workloads before and after delivery.

More suggestions are not evidence of more sales. A useful first result is that account managers can review the right customers with less searching and a clear record of the next action.

Bring us the list your team assembles each week.