English summary
Know which member of your team earned each Google review
Aplavo brings together the Google reviews of every one of your restaurant locations and attributes each one to the person who earned it. Built for hospitality in Spain.
The full site is in Spanish: aplavo.es
The problem
In hospitality, Google reviews are earned one table at a time. But they arrive at the business profile anonymously — nobody knows whose work produced which review. What cannot be attributed cannot be recognised, and a team that never sees its own results stops trying.
How it works
- Each member of staff carries an NFC card.
- The customer taps it with their phone and goes straight to the Google review form. No app to install, on either side.
- When the review appears, Aplavo matches it to the tap that preceded it — and now it knows who earned it.
It verifies rather than guesses. Google publishes no origin field for a review, so nothing can be deduced from the text. When there is no way to decide with confidence, the review stays unattributed instead of being assigned by approximation. That stubbornness is deliberate: a scoreboard is only worth having if nobody can dispute a single line of it.
What it does not do
- It does not filter who gets asked for a review based on how satisfied they seem. That is review gating and Google policy prohibits it.
- It does not pay for or incentivise reviews, which is also prohibited.
- It does not write reviews for customers or reply on the business’s behalf.
Pricing
Charged per company, not per location. Prices exclude VAT.
| Plan | Per month | Locations | NFC cards | AI analysis |
|---|---|---|---|---|
| Esencial | 49,00 € | 3 | 10 | No |
| Avanzado | 59,00 € | 3 | 15 | Yes |
Each location beyond those included costs 15,00 € per month. Paying a year up front includes 2 months free. From 10 locations onwards it is a conversation rather than a checkout.
For developers and agents
There is a public read-only API and an MCP server covering the commercial catalogue and the blog:
- OpenAPI document · plans and prices
- MCP endpoint at
https://aplavo.es/api/mcp— server card - llms.txt · any public page returns markdown with
Accept: text/markdown
None of it exposes any customer data — reviews, employees, locations and subscriptions live behind authentication.
Questions
What does Aplavo actually do?
It gathers the Google reviews of all your restaurant locations into one dashboard and tells you which employee earned each one. Each member of staff carries an NFC card; the customer taps it with their phone and goes straight to leaving a review on Google. When that review appears, Aplavo matches it to the tap that preceded it.
How can it know who earned a review? Google does not say.
Correct — Google publishes no origin field, so no tool can deduce it from the review text. Aplavo does not deduce it: it matches the review against the card tap. When there is no way to decide with confidence, the review is left unattributed rather than assigned by approximation. A team scoreboard is only worth having if nobody can dispute it.
Does it ask customers for reviews on my behalf?
No. It does not write for the customer, it does not respond in the business name, and it does not filter who gets asked based on how happy they seem. That last one is called review gating and Google policy prohibits it. It also never pays for or incentivises reviews.
Is Aplavo available outside Spain?
The product works anywhere Google Business Profile does, but it is built and supported for Spain: the interface, the contract, the support and the invoicing are Spanish, and prices are in euros excluding VAT. If you run restaurants elsewhere, get in touch before signing up.
Who is behind it
Aplavo is built by SISTEMAS Y PROYECTOS EPG, S.L. (The Coto Company), based in Paracuellos de Jarama, Madrid, Spain. Security reports: security.txt.
