Channels
Where nicoolAI lives today, how each channel feels, and when to choose WhatsApp, Slack, web chat, or [email protected].
Channels answer one practical question:
Where should this conversation happen?
That choice matters because the same request carries different meaning in WhatsApp, Slack, web chat, and email.
Choose the channel that matches the context
| Channel | Best when | What to expect |
|---|---|---|
| the relationship and ongoing rhythm matter most | the most natural personal surface | |
| Slack | workspace context or a shared thread matters | more bounded behavior shaped by team context |
| Web chat | you want the clearest account-linked product surface | explicit, browser-native, and good for ongoing direct use |
[email protected] | the work already belongs in an email thread | slower, more conservative, more sensitive to participants |
WhatsApp is the closest thing to the product's natural home.
Use it when:
- the conversation is personal and ongoing
- low friction matters more than a formal interface
- the agent should feel present in everyday communication
What to expect:
- the most continuous feeling of relationship over time
- a message-first interaction model
- a good fit for reminders, check-ins, and lightweight follow-through
Slack
Slack is the work-context channel.
Use it when:
- the surrounding thread matters
- the request belongs in a workspace rather than a private conversation
- the answer may depend on who can see the thread
What to expect:
- behavior that respects workspace and thread boundaries
- some capabilities depending on Slack setup and scopes
- a more conservative trust model than a direct personal channel
Web chat
Web chat is a real channel, not just a setup screen.
Use it when:
- you want a browser-native conversation surface
- the interaction should be explicit and account-linked
- you want the cleanest direct product experience outside messaging apps
What to expect:
- a dedicated product surface rather than an ambient messaging thread
- clear account-linked behavior
- the same nicoolAI continuity model in a more explicit interface
Email at [email protected]
Email is a live channel, but it plays by stricter trust rules than chat.
Use it when:
- the work already belongs in an email thread
- you want to email
[email protected] - you want nicoolAI to stay inside an existing exchange
- participant visibility matters as much as the reply itself
What to expect:
- replies that stay inside the same email thread
- more conservative handling when multiple external people are on the chain
- personal behavior only when the participant list makes that safe
See Email Channel for the email-specific trust model.
About the dashboard
The dashboard is both a real web channel and the setup surface for linked accounts.
Use it for:
- talking to nicoolAI in web chat
- connecting Google Drive
- managing future connectors
- account-linked product setup
Rule of thumb
- Choose WhatsApp when continuity and everyday use matter most.
- Choose Slack when workspace context matters most.
- Choose web chat when you want the clearest account-linked browser experience.
- Choose
[email protected]when the conversation should remain an email thread and participant visibility is part of the meaning.