03 · Social media
BetaHIRO Community
Your social inbox is not one inbox. It is four queues
The Social One
A restaurant's direct messages arrive all mixed together: the one who wants a table on Saturday, the umpteenth collaboration pitch, the supplier offering product and the one who only asks what time you open. The Social One reads it, sorts it and acts on what it is: it answers the question, hands the booking to the Host and leaves the commercial ones tidy so your team decides in a minute instead of twenty.
Built and working, limited availability.
Ninety per cent of your social inbox does not need a person. The remaining ten per cent needs one entirely.
The work
What it does, exactly.
Every line carries its own status. If something is in beta, it says so on the line, not in a footnote.
- Answers social messages at any hourBeta
- Sorts every message: booking, collaboration, supplier or questionBeta
- Answers hours, menu, allergens and directions in the message itselfBeta
- Hands to a person what needs judgementBeta
- Hands the table request to the Host without the guest repeating anythingBeta
- Recognises whoever wrote before or came beforeIn development
What it does not do yet
It does not publish content or schedule posts: it handles what comes in, it does not feed the profile.
It does not manage ads or campaign budget.
Recognising the guest through the memory is in development: today it sorts and replies, it does not yet arrive holding the history.
24/7
Social messages do not arrive during office hours. They arrive on Sunday night and Tuesday at seven in the morning.
Four queues, not one
Booking, collaboration, supplier and common question. Each with its own path, and only one ends up with your team.
Wired to the Host
What is a booking does not stay a message: it goes to the Host and ends up made in CoverManager.
In the house voice
It replies the way your team would, not the way a form would. And what it does not know, it says so.
HIRO Community · The Social One
Four different queues coming through the same door. Only one needs your team.
What it works with
It plugs into what you already have.
Redes sociales
BetaThe direct messages that arrive through the house profile, read and sorted before they reach your team.
WhatsApp Business API
BetaOfficial Meta API, with the house's verified number. No grey bots, no accounts at risk of being blocked.
CoverManager
BetaReal availability, creation, modification and cancellation of the booking. The employee does not leave a note for someone to key in later, the booking is made.
Anthropic Claude
BetaThe reasoning engine behind every employee. A provider with a no-training policy on your data.
When it goes on duty
The hospitality year is not flat.
The periods where this employee carries the most weight.
July and August, volume
Summer brings no new problems. It brings the same ones, multiplied.
September and October, the group diary opens
Group season starts long before Christmas.
November and December, the house at full load
Six weeks worth a quarter, and the team has nothing left to give.
The vacant post
What happens without it
Social messages answered late or not at all
Collaboration pitches mixed in with guests who want a table
The same question about hours and allergens, a hundred times a month
Bookings that arrive over social and have to be copied by hand into the system
What changes
With it on the team
Every message answered, including on Sunday night
Your team only sees what genuinely needs a person
Commercial pitches arrive sorted, not mixed in
The table asked for over social ends up made in the booking system
Do you want it on your digital team?
Tell us what your team still does by hand and we will show you how this employee works in a house like yours.
Tell us what your team does by hand