Set Up Trade-Only or Logged-In Visitor Context

A practical setup guide for sites that need different assistant behaviour for trade, logged-in, guest, or unregistered visitors.

When to use this

Use this setup when the assistant should behave differently for registered trade users, guests, account holders, or visitors on a specialist platform.

Example for a trade account holder

window.HelpSupportDeskWidgetContext = { platform: 'trade_portal', loggedIn: true, customerType: 'trade', accountStatus: 'existing_trade_customer' };

Example for an unregistered visitor

window.HelpSupportDeskWidgetContext = { platform: 'trade_portal', loggedIn: false, customerType: 'guest', accountStatus: 'unregistered' };

Suggested assistant instruction

When visitor context says loggedIn is true and customerType is trade, answer using the trade-account guidance in the approved knowledge base. When loggedIn is false or accountStatus is unregistered, guide the visitor towards registration or account application steps. Treat context as a helpful signal, not proof of identity.

Important boundary

Custom context should steer wording and next steps. It should not be used as the only authority for private pricing, personal account data, order details, refunds, or secure account actions.