In private preview

Meet in the middle.

Customer data in from any source, resolved into one clean profile per customer, and sent out to any destination.

It starts with your sources.

Guests, bookings, wifi sign-ins, spreadsheets. Data arrives in orange.

inbetween does the work in the middle.

Matched, deduplicated and measured, into one profile per customer. The gold dot is inbetween.

Then it reaches your destinations.

Mailchimp today, more to come. Only what changed, kept in sync. Data leaves in purple.

What it does

One profile, from every system you run.

Sources

Bring it in

Pull from a connector, receive a webhook, or upload a file. New fields need no rebuild.

  • Mews PMS and booking systems
  • Inbound webhooks
  • CSV import with column mapping
inbetween

Make sense of it

People from different systems become one customer. Every sync updates rather than duplicates.

  • Identity resolution and dedupe
  • Engagement metrics
  • Scheduled, idempotent syncs
Destinations

Send it out

Push clean, current profiles wherever your team works, or read them straight from the API.

  • Mailchimp audiences
  • Incremental, changed-only pushes
  • Open client API
What you get

Everything between source and destination.

A canonical customer profile at the centre, with everything around it handled.

Connect any source

Start with Mews, then add webhooks and file uploads. A new source field never means a migration.

One customer profile

One record per customer, holding every email, phone, booking and tag the platform knows about them.

Identity resolution

The same person across systems is matched and merged, so you count guests once, not many times.

Engagement metrics

Bookings, stays and status are measured per customer, ready to segment and act on.

Scheduled syncs

Build a pipeline once and let it run every night. Re-running updates, it never duplicates.

Incremental push

Only changed profiles go to Mailchimp, so pushes stay fast and your audiences stay current.

Open client API

Read the same clean profiles straight from your own apps, no destination connector required.

Multi-tenant and secure

Every record is scoped to your organisation. Connector credentials are encrypted at rest.

Nothing lost in between

A failed booking or a single rejected member never discards the rest of a successful sync.

How it works

Three steps, running on a schedule.

A pipeline chains a source, the work in the middle, and a destination.

1
MewsNew bookings come in
2
Compute metricsMatch, dedupe, measure
3
MailchimpChanged guests pushed
Connectors

First connectors, with more on the way.

A new source or destination is a connector, not a rewrite. Ask us about the one you need next.

Mews PMS

Source guests and reservations in

Sync guests and reservations from your property management system, including new bookings incrementally.

Live

Mailchimp

Destination audience in

Keep an audience in step with your customer profiles, pushing only what changed since last time.

Live

ActiveCampaign

Destination contacts in

Send the same clean profiles into ActiveCampaign, so campaigns run off one current view of every customer.

Live

Brevo

Destination contacts in

Push profiles and their engagement metrics to Brevo for email and SMS campaigns.

Live

Klaviyo

Destination profiles in

Keep Klaviyo audiences current, with only changed profiles going across on each push.

Live

Leat

Destination profiles in

Send customer profiles and their booking history into Leat for loyalty and retention work.

Live

CircleLoop

Source calls from

Every inbound and outbound call lands against the right customer, so a conversation is part of the profile rather than a separate log.

Live

SevenRooms

Source table bookings from

Table bookings arrive with the guest, so a diner and a hotel guest are recognised as the same person.

Live

The Cloud

Source guest WiFi from

WiFi sign-ins add a visit and an email that other systems miss, matched onto the same profile.

Live

Wireless Social

Source guest WiFi from

The second WiFi platform venues run, feeding the same customer profile as everything else.

Live

Purple

Source guest WiFi from

Guest WiFi sign-ins arrive as visits and contact details, matched onto the customer they belong to.

Live

Webhooks and CSV

Source webhook or spreadsheet

Push data to a per-organisation endpoint, or upload a spreadsheet and map each column to a profile field. Anything without a connector still gets in.

Live

Your own apps

Destination read by your apps

Read canonical profiles from the client API, or ask us about the destination you need next.

Talk to us

Let's meet in the middle.

Tell us what you run and where your customer data needs to land, and we will show you the profiles coming together.