HIRO
|
+ Let's Talk
|

Use case · Now

Live

Know which guests are worth bringing back.

A regular who came twice a month has not shown up in three. Nobody has noticed, because nobody looks at that.

It exists and can be demonstrated.

What it does

The Analyst sorts the base every night into six segments, flags the one who has stopped coming and proposes the reason they would come back. The Comms employee sends the campaign to that segment, with consent and without burning the rest.

Result

Reactivation with a reason, not a discount. And you know how many came back.

Most restaurants invest in attracting new guests while losing regulars through the back door. Not out of neglect: because spotting who has stopped coming means looking at the whole base every week, and nobody has that week.

The Analyst looks at it every night. Every guest lands in one of six segments, from the regular on the rise to the one slipping away, and each segment arrives with its next step written. When someone who used to come stops coming, they show up on Monday's list with the reason: their birthday, the dish they always ordered, the season they used to book.

The Comms employee turns that list into a campaign that only reaches who should receive it, through the channel they gave permission for. And afterwards it says how many came back, which is the only number that matters.

Real product

Recorded on the product, with a demo restaurant and synthetic data. In production, this is your house.

app.hiro-ds.com · Know which guests are worth bringing back.

Is this your problem? We will show it solved.

See HIRO in action