How it works
How the platform handles a review
Three diagrams are enough to understand the product. The first shows the overall shape, the second the path a review takes, the third the rule that protects your business.
The overall shape
A four-tier conveyor. Reviews come in at the top and leave at the bottom. The only tier that is not automatic is the decision one.
The path a review takes
In the database a review holds one state at a time. Four of them are crossed on their own. The fifth is not.
The rule that protects you
A one-star review about food poisoning must never get an automatic reply. The filter runs twice: on the incoming review, then on the draft the AI wrote.
The four publishing paths
A reply can leave from four places. The platform records which one, and that path decides whether the lock applies.
| Path | Triggered by | On a locked review |
|---|---|---|
| Manual | a person, from the review page | allowed, that is the whole point |
| Bulk | a person, on a selection of reviews | blocked |
| Automatic | the platform, with nobody present | blocked |
| MCP agent | an external agent, with an API key | blocked |
What runs while you sleep
Five jobs, spread across the early morning. They are what keeps the platform moving even when nobody signs in.
| Time | Job | What it does |
|---|---|---|
| 06:00 | Notification digest | folds the night into one message instead of one alert per review |
| 07:30 | Competitor snapshot | records the rating and review count of the listings you watch |
| 08:00 | Review upkeep | catches missed syncs and retries failures |
| 09:00 | Trial upkeep | closes expired trials and warns before the deadline |
| 2nd of the month | Management reports | computes the past month, builds the PDF and sends it |
The principle running through all of it
Nothing that binds you goes out unless an explicit rule allowed it. Automatic jobs can import, compute, warn and write. They cannot publish a reply on a review the safeguards have locked.