OnDuty
← Back to use cases
🪙

USE CASE · WEB3

Web3 and trading communities

Support your community where it already trades and talks.

OnDuty helps web3 and trading communities answer token, listing, and process questions in real time on web chat and Telegram, while routing sensitive issues to human ops.

Pain points we solve

  • Communities ask repeated token and listing questions 24/7.
  • Sensitive account-specific issues require controlled escalation.
  • Manual moderation makes it hard to track engagement patterns.

Outcomes you can expect

  • Members get instant answers for common operational questions.
  • Sensitive issues route to ops with context instead of public back-and-forth.
  • Teams see activity and engagement patterns without exporting chat logs.

Signals & metrics

Moderator time saved-40%
Faster member response<2s

Handled by OnDuty

OnDuty

Token and listing FAQs

OnDuty answers recurring token, listing, and process questions inside your community channels.

Sensitive escalation routing

Routes account-specific or risky issues directly to ops with context.

Community signal tracking

Surfaces activity and member engagement patterns without manual exports.

Example conversation

User

When is token listing and where do I check eligibility?

OnDuty

Listing opens Friday at 15:00 UTC. I can share the official checklist and route account-specific questions to ops.

User

Can you check my specific wallet case?

OnDuty

I have routed your case to ops with full context. They will continue with you privately.

Enterprise extensions

For enterprise teams, this use case can be extended with custom workflow automation, private deployment options, and more advanced agent setups managed through OnDuty.

Where needed, we can deploy a more advanced automation layer using our own resources and manage it through the OnDuty platform.

Workflow steps

3 channels
  1. 1

    Answer common questions

    OnDuty handles repeated community questions across approved channels.

  2. 2

    Detect sensitive intent

    Potentially risky or account-specific topics are flagged immediately.

  3. 3

    Escalate with context

    Ops receives a structured escalation with conversation history.

  4. 4

    Track community signals

    Activity trends and engagement data remain visible for decision-making.

KPIs to watch

  • Moderator workload
  • Response time
  • Member engagement

Channels covered

  • Website chat
  • Telegram groups
  • WhatsApp Business