Web chat

Web chat is a real channel, not only a setup surface.

It is the clearest account-linked version of the product: explicit, browser-native, and direct.

Getting started

To get started with web chat, open web chat. This is the clearest entrypoint if you want to use nicoolAI in the browser and manage connected accounts from the same product surface.

What makes web chat different

Unlike messaging channels, web chat is already tied to an authenticated session.

That means:

• the account context is explicit from the start
• connector setup can happen in the same surface
• the conversation feels more product-like and less ambient

Account-linked by default

Web chat is the most straightforward place for personal context because the signed-in user is already known.

That makes it the cleanest channel for:

• direct product use in the browser
• linking Google Drive and future connectors
• testing account-scoped behavior without involving a messaging bridge

Read-only behavior on web

Web has one important idiosyncrasy:

some non-web conversations are read-only when viewed in the browser.

Today that applies to:

• WhatsApp conversations
• Slack conversations
• email conversations

That boundary helps keep web chat from silently becoming the write surface for every other channel.

Google Drive links in web chat

Web chat is one of the main places where Google Drive works especially cleanly.

If the signed-in user has a valid Google Drive connection:

• nicoolAI can hydrate shared Drive links directly in the chat flow

If not:

• the UI can point the user directly to the Google Drive connect page

What good use looks like

Web chat is strongest when:

• the user wants the cleanest account-linked experience
• browser-based interaction is preferable to messaging
• the same surface should handle conversation and connector setup

Related pages

• Channels
• Google Drive
• Connectors
• Security