Frequently asked questions
Where do you search for tenders?
Two options. We search ourselves: government procurement in EIS under 44-FZ and 223-FZ, commercial and regional platforms. Or we connect with your API key to a tender aggregator you already subscribe to.
Which option is cheaper?
Usually the one with your service’s API key: the service maintains the sources. Our own search costs more because we run and maintain the sources and access to them ourselves. We quote for your task.
How does the bot know a tender is relevant to us?
By the phrase dictionary for your product range and stop words. Managers edit the dictionary in the workspace themselves, see the results preview and save a new version.
What about duplicates?
A tender the source returns as several cards with the same notice number and lot becomes one deal. Different lots of the same tender stay separate deals.
Can we do without CRM?
Yes. New tenders can arrive in Telegram and by email, and managers handle the dictionary and results in the workspace.
Do you build other bots?
Yes: website orders to email, forms and requests, CRM, messenger notifications, 1C exchange. Example flows are further down this page.
Who reviews the tenders found?
Your tender team or our AI tender manager: every day we read the documentation of new procurements, match the items with your catalogue and give a decision on whether to bid, with the reason. This is a separate service.
Which CRMs does the bot work with?
Any CRM with an API: amoCRM, Bitrix24, EspoCRM and others. If you have no CRM yet, we will choose and set one up as a separate service.
Will a Telegram bot work if the server is in Russia?
Telegram is currently unreachable from some Russian servers. We host the bot on a server where the messenger works reliably and set up the link to the website and CRM separately. VK and MAX bots work from Russia.