Umi × Resdiary
Our work with ResDiary started with a data problem. Restaurant covers are one of the richest signals a hospitality business holds, and in most operations they sit entirely outside the guest profile. We used the ResDiary API to feed that data into CRM, and in doing so became the first to connect ResDiary and Revinate.
The result was better profiles, sharper segments and marketing automation that could finally act on what guests did at the table rather than only what they did at the front desk. From there the work has progressed into the full API, building table reservations directly into custom booking flows so dining stops being a separate journey the guest has to find for themselves.
Restaurant data into CRM
Covers, preferences and booking history pushed into the guest profile, turning a system that usually sits in isolation into one of the most useful marketing signals you hold.
Richer segmentation and automation
Campaigns built on real dining behaviour, so a regular at the restaurant is treated differently from someone who has only ever booked a room.
Rooms and tables in one booking flow
Table reservations built into custom booking engines, so a guest books dinner in the same journey as the stay rather than being handed off to a separate widget.
Member-only reservations
Table booking placed behind a logged-in gate for members clubs, with availability and access rules reflecting membership tier.
