When a former guest asks about another course, useful context can save a long exchange: which course they attended, what was recorded afterwards and whether there is an open booking or payment question.
Start with the known customer record
TIDEFORCE connects supported booking and operational records around the customer. Customer 360 is available as a source-backed view; its completeness depends on enabled modules, records, permissions and identity configuration.
Read the actual history before recommending a next step. A recorded level is context for the team, not an automatic guarantee that a course is suitable. Ask the guest about experience since their last visit when that matters.
Keep website discovery in its own scope
An anonymous visit to the school website is not automatically part of that customer's history. Optional Website Insights provides aggregate analysis. Connected Journey can connect supported activity to bookings and customer history only when identity, attribution and consent or another valid basis support it.
There is no fingerprinting promise or retroactive identification of every visitor. A gap in attribution should remain a gap rather than an invented journey.
Offer a useful next step
Staff may discuss a follow-up course, rental or suitable shop item based on the actual conversation and records. Make the proposed offer and price clear. Personal use of a specific item needs an explicit usage record before the school describes it that way.
The existence of a profile does not automatically send a campaign, request a public review or grant a loyalty benefit. Use the supported communication tools and the appropriate basis for contact.
Read Customer 360 for the relationship view and Website Sync and optional analytics for the website connection.
How does this work at your school?
Bring an everyday task from your school. We’ll show you how it could work in TIDEFORCE.
Request a demo →