Today, B2B customers prefer to research on their own before contacting sales. According to a Gartner study, 67% of B2B buyers prefer purchasing without sales rep contact, and 70% want a completely digital self-service experience. For simple products, this works well. For a portfolio with hundreds of variants, however, self-research hits a limit: the customer finds too many similar items and does not know which one fits their specific installation.
This is where the difference between a public chatbot and an assistant in the login area becomes clear. One answers general questions. The other knows the logged-in customer and provides tailored advice for their specific situation.
Why Generic Answers Fall Short in B2B
Complex products often differ by just a single attribute: voltage, connection, diameter, or software version. To the customer, the product series looks identical, but selecting the right product comes down to that exact variation. An assistant that only knows the public catalog cannot resolve this question and provides generic answers. If the customer subsequently selects the wrong variant, returns or operational downtime are the result.
In addition, there is the so-called translation gap: the customer describes their request in everyday language, while the product knowledge exists in technical jargon. "The small valve on the 200 series" needs to be translated into the correct part number. This mapping is only possible with the right context—and the login area provides it. How this translation works in detail is explored in our article on digital product advisors.
The Login Area Makes Consultation Personal
As soon as the customer is logged in, the assistant knows who it is talking to. It knows the installed products, their configurations, the negotiated terms, and the order history. A general inquiry is thereby transformed into a specific answer: the compatible spare part for this exact installation, the pricing valid for this customer, and realistic delivery times.
This personalization transforms the advisory experience. With targeted follow-up questions, the assistant guides the customer to the right item—focusing on the attributes that truly narrow down the selection, and filtering out everything that is not compatible with their installation. Guided Selling in the login area combines the conversational capabilities of the language model with what the company already knows about the customer.
Consistency Instead of Contradiction
A second advantage carries significant weight in B2B. The same Gartner study shows that 69% of buyers experience contradictions between information on the website and statements made by sales reps. Such discrepancies undermine trust.
An assistant whose answers are grounded in verified sources and real customer data provides the same correct information everywhere. The answer in the portal aligns with the data sheet and with what sales says, because everyone draws from the same source. If the assistant cannot find a reliable data point, it hands over to a human rather than guessing. Trust would be severely damaged if a bot were to recommend a spare part that is not even available in the B2B shop.
Roles and Data Separation in the Portal
A login area brings responsibility, as the assistant works with sensitive data. Upon login, the portal passes the user's role to the assistant, ensuring that each user group only receives the content authorized for them. A purchasing manager sees different terms than a service technician, and the data of different customers remains strictly segregated.

For data protection, the location of data processing is also critical. Processing in Germany, backed by a data processing agreement, is the reliable path in B2B. What role-based knowledge delivery looks like is described in the article "From Documents to AI."
What Service Portal Consultation Requires
For an assistant in the login area to provide reliable advice, three elements must come together.
Product data must be structured, with attributes, variants, and compatibility rules defined as data relations. Seamless integration with existing systems must be in place so the assistant can access customer-specific data from ERP and CRM, such as availability, pricing, and the installed base. The article on CRM and ERP integration shows how this technical connection is achieved. Finally, handover to a human must be defined, because according to Gartner, many buyers still seek confirmation from an expert for final, complex decisions. The whitepaper on Guided Selling in B2B demonstrates how to integrate PIM systems and real-time data for consultation.
How Mercury.ai Implements This
Mercury.ai brings Guided Selling to the login area by uniting these three building blocks. The Knowledge Hub maintains structured product knowledge and links every answer to a verifiable source. Through integration, the assistant accesses transactional data from ERP and CRM, making every answer customer-specific. The portal passes the user's role, and the assistant respects data separation. An orchestration of specialized models verifies the source before generating responses, significantly reducing the risk of hallucinated answers.
The Böllhoff case study demonstrates how viable this is in industrial B2B. The fastening technology specialist used Mercury.ai to resolve a complex portfolio and eliminate common media disruptions in service, generating qualified leads from dialogues every day. The solution for product search and consultation offers an ideal entry point. When building such portals, Mercury.ai also collaborates with solution partners such as comspace.
Frequently Asked Questions
What is Guided Selling in a customer portal?
Guided Selling in a customer portal is guided product consultation that recognizes the logged-in customer. The assistant leverages identity, installed products, and terms to lead the user to the right item on an individual basis.
Why is a chatbot in the login area better for complex products?
Because it understands the customer's context. It resolves confusion between similar variants by referencing the specific installation, configuration, and compatibility of the logged-in customer, rather than providing generic answers.
How is customer data protected in the portal?
The portal passes the user's role, each group receives only authorized content, and data from different customers remains segregated. With Mercury.ai, data is processed in Germany.
Does the assistant replace sales?
No. The assistant handles recurring advisory tasks and pre-qualification. For the final, complex decision, it hands over to a human, whom many B2B buyers still rely on for confirmation.
What data does the assistant need for consultation?
Structured product data with variants and compatibility rules, along with access to customer-specific data from ERP and CRM, such as availability, pricing, and the installed base.
Consultation Begins with Context
For simple products, a public chatbot is sufficient. For a broad portfolio requiring explanation, context determines value. The login area provides this context, transforming a general source of information into an advisor that knows the customer and their equipment.
Companies that structure their product data, connect their systems, and strictly separate roles provide their B2B customers with the digital self-service they expect—while maintaining the reliability of their catalog.
Looking to bring product consultation to your customer portal? Talk to us or explore our solution for product search and consultation.
Sources
Gartner (2025/2026): B2B Buyer Survey. 67% of B2B buyers prefer purchasing without sales rep contact; 70% prefer completely digital self-service.
Gartner (2025): B2B Buyer Survey. 69% of buyers report contradictions between website information and statements made by sales reps.

About the Author
Dr. Hendrik ter Horst
Chief Product Officer @Mercury.ai
Dr. Hendrik ter Horst is Chief Product Officer at Mercury.ai. He holds a PhD in Computer Science from the CITEC Institute at Bielefeld University, with a focus on machine information extraction and data processing. For ten years, he has been working on dialogue-based AI systems, overseeing the conception, implementation, and validation of AI-powered applications from initial idea to production deployment.





