Desk
Sourcing requests
Request parameters, Scout search, landed cost and margin, an offer card to the client and their reactions.
Available Route in Desk: /requests
Purpose
A sourcing request is "what the client is looking for": make, model, years, budget, country. From it the manager finds options and proposes them to the client.
How it should work
- Request parameters: car, year range, budget, fuel, destination country.
- "Find with Scout". Scout collects normalized listings from dozens of sources (list: Scout sources). If one source is broken or blocked, the search does not fail: it is flagged and the rest work.
- A list of results immediately with landed cost and margin for your tariffs: no need to calculate each car separately.
- "Offer to client". The system builds an offer card with photos, a calculation and buttons "Like", "No", "Call me" and sends it to Telegram or the client's cabinet.
- History of offers and reactions: what was sent, what the client viewed and how they reacted. An offer can become a deal.
Offers have states: draft, sent, viewed, reacted, converted to a deal, withdrawn, expired.
What already exists
The requests and offers service and the Telegram reaction buttons contract are already described in the
core. The Data API already serves the same search externally: GET /v1/listings/search.