ONE PROFILE
LTV, orders, tickets — together.
Every order from POS or web, every support ticket, every campaign attaches to one customer profile. No stitching.
Live segments, loyalty, and email/SMS — built into the system. No CSV exports. No Klaviyo bill.
ONE PROFILE
Every order from POS or web, every support ticket, every campaign attaches to one customer profile. No stitching.
LIVE SEGMENTS
Define a segment once; it updates as orders and behaviour change. Trigger campaigns from a state, not a snapshot.
LOYALTY
Configure a program in minutes. No second login, no extra app, no margin handed to a third party.
In operation
The app sits inside the shared Kotao workspace. That is the difference between adding one more tool and running the daily workflow on an operating system.
Every action writes back to the same operating record instead of collecting data for later exports.
Roles, permissions, and audit logs stay connected to the rest of the workspace.
Reporting, CRM, payments, and website surfaces see the change without a team checking CSVs.
Rollout
Kotao does not need to be switched on all at once. Most teams start with the workflow that costs the most time today, then expand after the team trusts it.
We start with the way the team works today: who touches it, which data is missing, and which systems still need to connect.
Products, customers, roles, bookings, and payments are modelled so other Kotao apps can use the same source of truth.
One location, one team, or one clear process goes live first so operators see production behavior, not a demo script.
Once the core workflow is stable, more locations, apps, automations, and reports can be switched on without re-importing data.
Apps to wire up.
0
Connected apps
Once this workflow is live, adjacent apps can use the same customers, products, payments, and permissions.
POINT OF SALE
One POS for counter, table, and tap. Same data as your online store. Works offline.
WEBSITE & STOREFRONT
Build the public site without a separate Shopify or Webflow bill. Products, content, and bookings share one data model.
BOOKINGS & TABLE PLAN
One booking surface for restaurants, salons, classes, events. Confirmations, deposits, no-show protection.