other
Autovit.ro is Romania's used and new car marketplace, the place most Romanian buyers already check before they visit a dealer. Connected to Neotask, an agent can take a loose description of a car, like an SUV with low mileage for a family of four, and turn it into a real search against Autovit.ro's listings instead of asking you to fill in a filter panel. You describe what you actually want, the agent runs the search, and when the first batch of results is too wide or too narrow, you keep talking and it narrows or widens the query. That back and forth is the point: car shopping rarely starts with exact numbers in mind, it starts with a shape of a need, and this connection lets the agent work from that shape.
| Natural-language listing search | Converts a described need (body type, budget, mileage, use case) into an Autovit.ro marketplace query |
| Follow-up query refinement | Adjusts an existing search based on a spoken correction instead of a fresh filter form |
| Listing shortlist retrieval | Returns a set of matching cars for comparison inside the conversation |
A buyer tells the agent they need something roomy for two kids and a dog, under a set budget, and don't want anything over 120,000 km. The agent queries Autovit.ro, comes back with a shortlist, and when the buyer says the results skew too small, it re-runs the search favoring larger body styles.
After an initial search returns ten cars, the buyer asks the agent to narrow to only automatics under a certain year, then to pull the three cheapest of those. The agent re-queries each time instead of the buyer manually re-filtering on the site.
No account is required to search and browse listings this way; the connection reads the public marketplace catalog.
No. The connection surfaces matching listings; contacting a seller or arranging a viewing still happens directly on Autovit.ro.
This specific connection is scoped to Autovit.ro's car marketplace, not its other listing categories.
That's the expected starting point. Describe the car loosely, review the first results, and correct course in the next message rather than trying to get the query exactly right up front.