Skip to content
Use cases

Role · Commercial Director

Commercial teams acting on one profile.

Loyalty and CRM should read the resolved guest, not own a second copy. Recognition is the layer’s job; the programme keeps the points engine.

  1. Problem

    Each tool keeps its own guest.

    Loyalty, CRM and campaign tools each do real work, and each tends to keep its own copy of who the guest is. A richer points ladder does not fix a person split across those lists.

  2. Outcome

    One person those tools act on.

    A campaign, a tier and desk recognition attach to the same guest. The programme keeps the points engine. The CRM keeps the campaigns. This page does not invent a return figure.

  3. How Casa fits

    Under the stack. The tools stay.

    Casa Layer resolves the person and stops. The Master Profile sits under the stack. Change the CRM or the loyalty tool later and the resolved record carries on, because it never lived inside them. Casa Layer builds the record and holds it. We sell no applications on top of it, so there is nothing here for it to be locked into. Your own source systems stay the record throughout, and every copy is deleted 30 days after cancellation. You decide what Casa Layer can do in each system, and you can revoke it. Every connection live today reads only.

Who reads the profile

Recognition is the layer's job. The programme keeps the points engine.

Loyalty, CRM and a commercial agent read one Master Profile. Recognition is the layer's job. The programme keeps the points engine.

  • Not a loyalty product, a CRM, or a messaging suite.
  • Commercial tools stop acting on different people.
  • You issue credentials and can revoke them. Every connection live today reads only.
  • No invented return figures.

See it against the commercial tools you already run.

Book a 20-minute demo