One customer record,
across every
touchpoint.
Most CRMs are a separate system. Yours sits inside the same platform as the POS, the storefront, the ticketing, and the memberships — so a customer is one customer, regardless of how they reached you.
Used by Kaishing for ICC member management and by Sun Ferry for passenger CRM. Available to every operator on the platform.
Every touchpoint writes to the same profile, one history, one segmentation surface.
Trusted by
Powered by
CRM doesn't usually mean
what people think it means.
Most operators don't have one CRM — they have several. A loyalty system from the POS vendor. A customer list from the e-commerce builder. A separate database for memberships or subscriptions. Marketing tools that scrape what they can from each.
The result is a customer who's a different person in every system. A POS regular and a /shop customer with the same email aren't connected. A passenger and a member are tracked in different places. Campaigns target a fraction of the relationship; loyalty rewards a fraction of the spend.
The actual customer — the one who walks in, orders online, takes the ferry, renews a membership — sees the whole relationship. The merchant should too.
Every touchpoint writes to
the same customer record.
POS visit, /shop order, ticket purchase, membership renewal, supplier-side B2B order — all flow into one profile, one history, one segmentation surface.
What's in a profile
- Contact details — name, email, phone, language preference
- Transaction history across every module on the platform
- Visit frequency, spend, channel mix
- Loyalty status, membership tier, points or rewards balance
- Tags and segments applied by the operator
- Communication history and preferences
What the operator can do
- Segment customers by behavior, spend, channel, or custom criteria
- Run campaigns to a segment — email, SMS, app notifications
- Issue and track loyalty programs, rewards, and discounts
- Manage memberships, tiered access, and recurring billing
- Pull customer insight into reporting for product and pricing decisions
What unified CRM looks like
in production.
Three deployments, three very different verticals — building memberships, ferry passengers, diners.
Kaishing
Kaishing uses Synque to manage facility memberships at The International Commerce Centre, Kowloon’s tallest building. Member profiles, tiered access, recurring billing, and amenity bookings all live in one record — renewals, access changes, and usage patterns visible in one place.
Sun Ferry
Sun Ferry uses Synque as the passenger CRM behind their ticketing operation. Every ticket purchase creates or updates a passenger profile, with route preferences and travel frequency visible in real time. The same profile drives the island coupon and merchant-network experience — one record, ticket to destination.
F&B groups
F&B operators running both POS and /shop see one customer record per diner, regardless of channel. A regular who orders ahead online then collects at the counter is one customer with one history — and a loyalty program runs against the full picture, not the fragment any single channel captures.
CRM that's part of the platform,
not bolted onto it.
Standalone CRMs require integration — usually a partial one. Some data flows; some doesn't. Customer IDs match in one system and not another. New tools require new integrations.
Synque CRM doesn't have an integration with the rest of the platform. It is the rest of the platform.
Writes every transaction to the customer record automatically. No tagging, no export.
Orders create or update the same profile. Order-ahead-then-walk-in is one person, not two.
B2B customer relationships on the same architecture — distributors managing restaurant accounts.
Ticket purchases create customer records the same way, in the same database.
Member profiles, tiers, and recurring billing on one architecture.
Every charge, refund, and chargeback links to the customer record by default.
No connectors to maintain. No integrations to debug. One customer record, one source of truth, one operating picture.
Built for the way different
operators actually work.
For F&B groups
Diners across in-store, online, delivery, and loyalty in one record. Multi-outlet, multi-brand customer data consolidated automatically.
For property & facility operators
Member profiles, tiered access, recurring billing, and amenity usage in one system. Renewal management and member experience in the same software.
For transport & travel operators
Passenger profiles tied to ticket purchases, travel patterns, and destination engagement. Tourist and local segmentation built in.
For distributors & B2B operators
Restaurant or business-customer accounts managed with the same architecture as direct consumers — order history, credit terms, account relationships in one place.
Customer-facing experience,
where the operator wants it.
Some deployments use the CRM purely on the operator side — a back-office database that drives marketing, loyalty, and reporting. Others extend it to a customer-facing app: members and passengers see their profile, balance, history, and rewards directly.
Sun Ferry's passenger experience, and the island merchant coupon network, runs on this customer-facing layer.
The CRM works either way. Operators choose how much of the customer experience they surface — in our app, or in their own digital channels.
Profile · balance · rewards
In production for Sun Ferry passengers and the island merchant coupon network.
Run CRM as part of the platform —
or as a standalone module.
Operators can run CRM alongside POS, /shop, ticketing, or memberships — or as a standalone module connected to existing systems.
Most deployments are live within days of onboarding, depending on the operator's existing data and the integrations they need.
Questions operators
ask us.
How is this different from a loyalty system bundled with a POS?
POS-bundled loyalty captures only what happens at the counter. Synque CRM captures every channel — POS, /shop, ticketing, memberships — in one record. A customer who orders online and then walks in is the same person, with one history.
Can we use the CRM without using the POS?
Yes. The CRM is a module — operators can run it standalone, alongside other parts of the platform, or as part of a full deployment. Kaishing and Sun Ferry use the CRM without using our POS at all.
Can the CRM integrate with our existing POS or e-commerce system?
Yes. We’ve integrated our CRM with multiple third-party POS systems and online platforms in past deployments. New integrations are scoped on a per-operator basis.
Can we send emails or messages from the CRM?
Yes. Operators can segment customers and send campaigns through the channels they have set up — email, SMS, app notifications, depending on the deployment. We work with operators to plug in their preferred messaging channels.
Who owns the customer data?
The operator. Customers are the operator’s — not ours, not the platform’s, not a delivery aggregator’s.
Where is the data stored?
On infrastructure compliant with the data and privacy requirements of the markets we operate in. Specifics available under NDA for operators evaluating us.
Is there a customer-facing app?
Some deployments use one — Sun Ferry’s passenger app and the island merchant coupon network are examples. Others run CRM purely as an operator-side tool. Both are supported.