The relationship has moved on

A person who was not ready for a service six months ago may return with a different project. In Tap Tap Go’s CRM and intended lead-assistance model, historical context can be useful, but it should not freeze the relationship in an old category. Read the new request before relying on a previous score or disposition. Ask whether the earlier assessment still applies to the current need, timing and available product scope.

Update rather than overwrite blindly

Keep relevant history while identifying which facts are current. Note the new enquiry purpose and any changed requirements. Do not ask the assistant to infer continuity where there is none, such as assuming a new employer has the same budget or priorities as the previous one. Prepare a response grounded in the latest message and review it before sending manually. Where the current app supports notes or CRM updates, use them to distinguish present context from historical observations.

Imagine this

Hypothetical example

A former prospect returns after joining a different company. Their earlier request was outside scope, but the new project is relevant. The salesperson reviews the new context, updates the working assessment and drafts a fresh response rather than repeating an old rejection or treating the previous score as permanent.

Make it practical.

Use this checklist as you read. Checks are not stored.

References & further reading

Tap Tap Go Journal: product context and editorial approach ↗

Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.