← All resources
TIDEFORCE JournalOperations
#040

Why Complete Customer History Matters Across Locations

A complete customer profile gives an outdoor sports school reliable context across stays and authorized locations, so office teams can understand a guest without piecing the story together manually.

Read full article

A complete customer profile gives an outdoor sports school reliable context across stays and authorized locations. TIDEFORCE now records the location of an active stay explicitly, preserves previous stay snapshots and loads cross-location bookings more reliably for team members who have access. That means less guessing at the office and a clearer operational picture of every guest.

Why customer history becomes fragmented

A guest may book at one base, check in at another and return in a later season. If location, stay and booking information is separated, staff have to reconstruct the story from several screens or ask colleagues for context.

The problem becomes more visible in multi-location groups, where the same customer relationship continues across bases but access permissions still need to be respected.

What has improved in TIDEFORCE

  • The active stay now carries its location explicitly.
  • The check-in flow includes a dedicated Stay location step.
  • When an active stay is replaced, its previous snapshot is preserved in the check-in history.
  • The customer profile loads bookings from other locations more reliably when the team member has access to them.
  • Manual customer-tier changes are logged internally with the previous value, timestamp and administrator.

A clearer check-in workflow

During check-in, staff select the location that belongs to the stay. TIDEFORCE first uses the customer’s current stay location when available, then the tenant’s current location, and finally the first available location. The team can confirm or change that choice before continuing.

Authorized cross-location context — the full booking story, shown only where a team member has access
Authorized cross-location context — the full booking story, shown only where a team member has access

This small step makes the resulting history more useful because the stay is connected to the correct operational context from the start.

Reliable context across authorized locations

When a team member opens a customer in People, the bookings panel now loads bookings from other locations more reliably. It still respects the locations that person is allowed to access.

For a multi-location school, this makes the customer profile more useful without turning it into an unrestricted view of the whole group.

A clearer check-in workflow — confirming the correct stay location so the operational context is right from the start
A clearer check-in workflow — confirming the correct stay location so the operational context is right from the start

Better accountability without overpromising the interface

Manual customer-tier changes are now recorded internally with who made the change, when it happened and which value was replaced. Previous active stays are also archived when the stay is overwritten.

Important: these records are captured now, but a visible tier-change and stay-history timeline inside the customer profile is a later step.

How to use the improved profile

  1. Open the check-in dialog and confirm the new Stay location step after the check-out date.
  2. Open People, choose a customer and review the bookings panel for activity from other locations you can access.
  3. Continue changing customer tiers from the People table as before; the manual change is now recorded internally.

A stronger customer relationship starts with reliable context

Booking is only the beginning. A connected customer profile helps an outdoor sports school understand the guest beyond a single transaction and gives the team better context for the next interaction.

Frequently asked questions
01

Does every active stay now have a location?

+

Yes. The active stay stores its location explicitly, and the check-in flow includes a Stay location step so the team can confirm the correct base.

02

Can staff see bookings from other locations?

+

The customer profile loads bookings from other locations more reliably, but only for locations the team member is allowed to access.

03

What happens when an active stay is updated?

+

The previous active-stay snapshot is archived in the check-in history before it is replaced, helping preserve the operational record.

04

Are customer-tier changes visible in a profile timeline?

+

Manual tier changes are logged internally with the administrator, time and previous value. A visible timeline in the customer profile is planned as a later step.

05

Who benefits most from this update?

+

Office teams, managers and multi-location operators benefit from clearer stay attribution, preserved history and more reliable cross-location booking context.

TIDEFORCE product update — complete customer history across every location
TIDEFORCE product update — complete customer history across every location
Next update →Why Outdoor Sports Schools Need More Than a Booking System

See how TIDEFORCE fits your school

In a short demo, we'll walk through your real workflows: services, booking, planning, team, guests, inventory, guidebook and shop.