New format
Chat with a company in Yandex: Dialogs and contact from search
“Chat with a company” in Yandex’s stack is a way to start a dialogue with a business not only from the site, but from search surfaces: the snippet, related voice-assistant scenarios where the product is still available.
Below: why it helps a business, what’s needed to connect, and how not to confuse it with a regular on-site widget. Cabinet names (historically Dialogs), partner CMS options, and display points have changed since 2018 — check current Yandex Help and product status at the moment you implement.
Why a business wants chat from search
Some demand closes before a site visit: “in stock?”, “how much is delivery?”, “open today?” If you can answer from the results, you shorten the path to contact.
The channel especially helps services and local businesses with a short sales cycle. For complex B2B with a long proposal, chat is an entry — not a replacement for a manager and a brief form.
When the channel earns the attention:
- someone answers during peak hours
- typical questions close in one to three replies
- leads go to CRM, not lost in DMs
- the site already has a privacy policy and offer
Where the button may appear
2018 announcements mentioned the search snippet and assistant scenarios (Alice). Surfaces have narrowed and expanded since — don’t treat an old screenshot as a display guarantee.
Practical cue: connect the channel → check whether a contact option shows on your commercial queries and on the organization card if it’s linked to the site.
How people connected it — and what to check now
Classic path: Yandex account → Dialogs or business-chat cabinet → unique chat ID → embed in CMS or hand off to an integrator. Some platforms had ready modules; others used the API.
If your chat provider still doesn’t speak Yandex’s channel, ask about a ready hookup or webhooks. Don’t promise a client a “button in the results tomorrow” without checking eligibility.
Checklist before you turn it on:
- named operator and schedule
- scripts for typical answers
- lead handoff to CRM or email
- personal-data consent in the flow
- test from a real smartphone and PC
Operator, bot, and dialogue quality
A button without a response SLA hurts trust more than its absence. Set first-response time, human escalation, and a ban on copy-paste “we’ll call you back” with no next step.
Bots cover FAQ; complex orders go to a person immediately. Dialogue logs feed site FAQ and ad keyword ideas.
Search chat vs on-site widget
You control the on-site widget: design, flows, A/B. The Yandex channel adds an entry point but depends on platform rules and moderation.
Best base: form plus messenger or widget on the site; search chat only if the product is available and the team can answer. Don’t spawn five chats with different queues and no shared CRM.
Takeaways
Chat with a company in Yandex is a dialogue channel from the search ecosystem — not one more icon for fashion.
Connect only with an answer process and a check of current product status; a thin 2018 announcement alone is not a setup.
FAQ
Is this a replacement for the site form?
No. Chat from search complements the site: a quick here-and-now question. Forms and CRM still handle structured leads.
Do I need my own chat operator?
Yes — someone must answer during business hours, or you set up a bot and routing. A dead chat hurts more than no button.
Does it only work on Bitrix?
Historically there were ready integrations with several platforms; others connected via API. Check the current partner list in Help.
Does chat show for every site in the results?
No. You need a connection, moderation / rule fit, and display conditions. Not every URL gets a button automatically.
How is it different from Jivo or Carrot?
A third-party widget lives on your domain. Yandex Dialogs is also a channel from the search ecosystem; Yandex sets the rules and entry points.
Want a Yandex search chat button — with nobody answering and no CRM?
We’ll verify product status, set an operator SLA, and wire leads so the channel helps instead of hurting trust.
Discuss the task
