Persistent cross-channel AI coworkers for a single job function

What to build

A support-triage AI coworker for small SaaS teams, built on CopilotKit/OpenDots, that lives inside Slack, takes customer voice calls, and chats with customers on-site — classifying, prioritizing, and routing tickets while persisting full context across whichever channel the customer or agent switches to.

OpenDots just commoditized the hardest part of building a multi-channel AI coworker (state, memory, channel-switching), so the opportunity shifts from building agent infrastructure to packaging one narrow job function — like support triage — as a sellable micro-SaaS on top of it.

Demand

Small SaaS and startup support teams (2-10 person ops/CS teams) want AI that reduces ticket backlog without replacing their whole stack, and now that the channel-switching plumbing is open-source, a solo builder can ship a single-function coworker instead of a general platform.

• GitHub - CopilotKit/OpenDotsProduct release

  1,533 GitHub stars on a TypeScript repo positioned as 'always-on AI coworkers that move between text, calls, and Slack' — high engagement signaling developer appetite for building on this primitive.

• Intercom Fin / Decagon / ForethoughtAdjacent product

  Established paid products already monetizing narrow support-triage AI coworkers, evidencing buyer willingness to pay for single-function agents rather than general platforms.

Stack

• CopilotKit/OpenDots
• Slack Bolt SDK
• OpenAI Realtime API (voice)
• Zendesk or Intercom API (ticketing integration)
• Supabase (state/memory persistence)
• Vercel

Solo + AI difficulty

The channel-switching and memory layer is now mostly solved by OpenDots, so a solo builder can skip that and focus on narrow triage logic and one system-of-record integration (e.g. Zendesk); the hard part is reliably classifying and routing real tickets without hallucinated escalations, plus the per-customer setup of Slack and ticketing auth. Realistic MVP for one vertical: 2-4 weeks with AI-assisted coding.

Entry threshold

Needs integrating an existing agent orchestration SDK (CopilotKit-style) with Slack API, a calling/voice API, and an LLM, which a solo builder can wire up in 1-2 weeks; the hard part is picking a narrow enough job function to avoid competing with general agent platforms.

Window

6-12 months

Where to find first users

• Indie Hackers launch post
• Product Hunt launch
• r/SaaS and r/startups
• Direct outreach in support-ops Slack communities (e.g. SaaStr, SupportDriven)

Competitors

• Intercom Fin
• Decagon
• Forethought
• Ada

Counter-signals & risks

• Commoditized infra like OpenDots lowers the barrier for everyone, including well-funded incumbents, which could compress the window of advantage for a solo-built micro-SaaS before larger players ship the same vertical feature.

• Vertical AI coworkers still need deep per-function integration with systems of record (CRM, helpdesk, ticketing), which can offset the simplicity gained from commodity channel-switching infra and extend time-to-value.

• Enterprise buyers may prefer consolidated general-purpose agent platforms over stitching together multiple narrow point-solution coworkers, creating platform risk for a single-function vendor.