Can I put DChat inside a signed-in customer portal?
Yes, and you can hand it the identity the page already has. Pass the visitor's name and email in the embed and the pre-chat form opens pre-filled, so a signed-in customer is not asked to retype details you are already showing them. Treat it as convenience, not authentication: the values arrive from the browser and the server treats them as untrusted.
Will the widget break my application's styling?
No. It renders inside a Shadow DOM, which isolates styles in both directions. Your CSS cannot leak in and break the chat window, and the widget cannot leak out and disturb an application layout.
Can different areas of my product route to different teams?
Yes. The embed carries a department, so a billing screen and a technical dashboard can route to different queues without any server-side work on your side.
Can I collect application context with the chat?
Yes. Custom pre-chat fields let you ask for an order number, account ID, severity or anything else, and the answers are stored with the conversation and shown to the agent. The server validates every submission against your own field definition.
Does it work on mobile and inside single-page applications?
Yes. The widget is responsive, follows the visitor's dark-mode preference, and can be initialised programmatically with DChat.init() rather than a plain script tag when a framework needs to control when it loads.