Best for teams that want the quickest path to a polished live chat without managing provider keys on day one.
Clear seat pricing for the support setup you actually want.
Dchat separates managed AI, customer-managed AI, and human support access so teams can choose the operating model that fits their workflow.
Best for teams that want direct ownership of the OpenAI key, clearer internal cost tracking, or tighter governance.
Best for teams that want AI to handle the repetitive layer while people step into the conversations that need judgment.
These seats map to real support choices, not vague plan names.
Dchat separates launch speed, AI ownership, and human backup so pricing follows how support actually runs day to day.
Dchat-managed AI keeps the setup path short when you want to go live quickly.
Customer-managed AI keeps provider choice and internal governance in your hands.
Human seats cover the questions where judgment, tone, or account access matter more.
Dchat-managed AI
Dchat manages the AI key so the workspace can be configured quickly. final AI cost depends on usage.
Best for teams that want the shortest path from setup to live support.
- Full widget, inbox, routing, branding, and reporting surface
- Knowledge base, prompts, model settings, and site crawl tools
- White-label controls, proactive chat, ratings, and contacts
Customer-managed AI
Bring your own OpenAI key and pay the provider directly for AI usage while keeping the same Dchat support surface.
Best for teams that want AI ownership and provider-level cost control.
- Direct control over the AI key and provider configuration
- Same widget, routing, inbox, and knowledge tools as managed mode
- Useful when AI ownership and internal cost controls matter
Human support seats
Add human teammates who take over the conversations AI should not own alone and keep the thread moving inside the same inbox.
Best for teams that want a smooth handoff path instead of leaving people stuck with the bot.
- Shared transcript between AI and human support
- Team access, canned responses, and contact context
- Works alongside either managed or customer-managed AI
Most teams start with one AI seat, then add human support where exceptions happen.
The simplest rollout is usually one AI seat for first-response coverage and a few human seats for handoff, escalation, and account-sensitive issues. You can keep the same workspace either way.
Start with one AI seat to cover the repetitive layer, then add people once you know which conversations need a human touch.
Use customer-managed AI when procurement, governance, or provider ownership matters from the beginning.
Keep human seats available for the moments where tone, judgment, or account access matter more than speed alone.
Three quick questions usually make the right plan obvious.
If yes, Dchat-managed AI is usually the better starting point.
If yes, customer-managed AI gives you the cleanest governance story.
If yes, plan for human support seats so handoff feels smooth instead of reactive.
Compare the workflow, not just the sticker price.
Review the live widget, support workspace, and deployment path alongside the seat structure before deciding how you want to run support.