Capabilities
Current scope and maturity
Dchat publishes capability maturity so buyers can separate shipped website-support behavior from configured intake, planned expansion, and unclaimed suite parity.
Available now
Website chat, human-owned conversations, approved knowledge boundaries, customer-managed AI mode, and launch evidence form the current core.
- Website widget
- Human inbox
- Provider clarity
Configured with evidence
Additional intake channels and HTTPS tools should be enabled with named owners, sample payloads, audit notes, and rollback steps.
- Owner
- Payloads
- Rollback
Not claimed yet
Voice agents, large marketplace breadth, formal compliance badges, and deep CRM-native workflows remain outside Dchat's public parity claims.
- No voice parity
- No fake marketplace
- No badge without proof
Capability status
| Capability | Status | Detail |
|---|---|---|
| Website chat widget | Available | Install script, capture first intent, keep human handoff visible, and review conversations in the inbox. |
| Human-owned inbox | Available | Operators own follow-up, use saved views, and keep resolution context attached to the conversation. |
| Approved knowledge drafting | Available | AI answers should be grounded in approved sources and escalate uncertainty or sensitive requests. |
| Customer-managed AI provider mode | Available | Customers can separate platform spend from model usage when finance or security review needs provider clarity. |
| Email, SMS, WhatsApp, and Slack intake | Configured | Use when routing, owner, fallback, and channel-specific evidence are recorded for the launch. |
| HTTPS tools and sensitive actions | Configured | Prefer read-only context and drafted work; require human approval before account, refund, or entitlement changes. |
| Native marketplace integrations | Planned | Do not market native OAuth or marketplace parity until scopes, auth boundaries, and rollback behavior ship. |
| Voice and phone agents | Not claimed | Keep voice out of public parity claims until Dchat ships a tested phone path with clear fallback ownership. |
| SOC 2, GDPR, SLA, and residency badges | Evidence required | Current trust copy can describe controls and decisions; formal badges need signed proof. |
Use this page as the source of truth when comparing Dchat to broader suites: shipped behavior first, roadmap language second, no unsupported parity claims.