Answer and hand off cleanly.
Dchat already has the core support loop: branded widget, AI replies, knowledge grounding, human takeover in the same thread, and live notification endpoints for external follow-up.
From AI answers to
support actions.
Dchat starts with the highest-leverage channel: your website. Today it adds notification endpoints, generic webhooks, Stripe-backed billing, and approval-safe outbound actions. The next layer is practical automation around the handoff loop: email, ecommerce lookups, CRM context, ticket creation, and workflows your team can understand.
Website chat today
AI key choice
Same-thread handoff
Webhook + action layer
Connected actions
From website chat to the tools your team already uses.
The current product already covers the first operational gap: notify the right people, queue outbound actions for review, and connect events to external systems without a heavyweight marketplace.
Team alerts
Ecommerce context
Action approvals
Why this matters
Competitors are selling agents that do work. Dchat should too.
YourGPT, Ada, Intercom, Gorgias, HubSpot, and Front all push beyond answers into connected actions. Dchat's answer is not to become a generic automation platform. It is to ship the support actions that close real buying objections, while staying explicit about what exists today versus what is still next.
Act on customer context.
The next buyer question is simple: can the AI look up an order, create a ticket, notify the team, or update the CRM without making support jump tools?
Controlled actions, not black boxes.
Actions should be visible, permissioned, and reviewable. The operator stays in control while AI does the repetitive work around the conversation.
Available now vs next
Separate the live product from the roadmap.
This is the honest split buyers need during evaluation. Dchat already covers alerting, billing, hosted help content, and approval-safe outbound actions. The next round closes the bigger channel and systems-integration gaps.
- Slack, Microsoft Teams, Discord, and generic HTTPS webhook endpoints
- Retry-backed outbox delivery for notification events
- Stripe-backed billing and subscription management flows
- Hosted help center pages backed by the knowledge base
- Task center approval queue for outbound webhook actions
- Templates for CRM, commerce, billing, and no-code workflow handoff
- Email inbox support so Dchat is no longer only website-first
- Native ecommerce context such as order, return, and shipping lookup
- CRM contact sync and account timeline enrichment
- Deeper workflow orchestration beyond event fanout and approved actions
- Broader channel packaging for buyers comparing omnichannel suites
Integration roadmap
The integrations that close the biggest product gaps first.
This is ordered by competitive impact. Email and ecommerce context make Dchat feel like a support platform. Team alerts and workflow tools make handoff operationally useful.
| Priority | Integration | What it unlocks | Competitor pressure |
|---|---|---|---|
| 1 | Email inbox | Turns Dchat from website chat into a focused support inbox and closes the most obvious comparison objection. | Zendesk, Intercom, Front, Help Scout, Freshchat |
| 2 | CRM and account context | Gives agents and AI the customer, account, and timeline data buyers expect during real support work. | Intercom, HubSpot, Front, Zendesk |
| 3 | Shopify and WooCommerce | Lifts Dchat from generic support chat into real buyer and order context. | Gorgias, Tidio, HubSpot |
| 4 | Stripe support context | Extends the current Stripe billing surface into support-side subscription, plan, and payment context. | Intercom, HubSpot, Front workflows |
| 5 | HubSpot CRM sync | Syncs contacts, lifecycle stage, deal context, and support notes after the broader CRM context layer exists. | HubSpot, Front, Zendesk |
| 6 | Zapier and Make | Gives smaller teams a no-code escape hatch for custom workflows. | YourGPT, Crisp, Front, HubSpot |
| 7 | WhatsApp-style inbox expansion | Closes the next channel objection after email and gives Dchat a clearer async support story. | Intercom, Freshchat, Crisp, Tidio, Zendesk |
Email inbox pilot
The first channel expansion should stay narrow.
Intercom, Zendesk, Freshchat, Crisp, and Front all make email feel native to the support workspace. Dchat can close the most visible gap with a focused email pilot before attempting every channel at once.
Forward into Dchat
Start with support-address forwarding so teams can route website replies and help emails into the same operator queue without migrating DNS or replacing their mailbox.
Keep the same conversation model
Convert inbound email into the existing conversation timeline, with channel labels, contact matching, assignment, tags, notes, macros, and SLA policies reused from chat.
Draft before sending
Let AI summarize, suggest replies, and propose knowledge fixes first. Human-reviewed sending is safer than launching fully autonomous email replies on day one.
Measure the upgrade
Track email volume, first response time, AI draft acceptance, unresolved topics, and overlap with website handoffs to prove the channel is worth expanding.
Execution order
Why the roadmap is sequenced this way.
The next moves are ordered by buyer impact, not by how many logos can be added to an integrations page.
Add email before broader channel sprawl.
Email changes how buyers classify Dchat immediately. It turns the product into website chat plus async support instead of a widget-only decision.
Add customer context before generic workflow claims.
CRM, account, billing, and order context make AI and human replies materially better. That matters more than a broad automation canvas for most support teams.
Expand channels after the support loop is deeper.
WhatsApp-style coverage matters, but it lands better after email and customer context are already in place. That keeps the product focused and the roadmap defensible.
Available today
Dchat already ships practical notification endpoints.
The current product surface is not a giant marketplace. It is a focused notification, help-center, and webhook layer that covers the first operational gap most teams hit after launch.
Slack, Teams, and Discord alerts.
Send handoff requests, visitor replies, and support activity into the channels your team already monitors.
Generic JSON endpoints for custom flows.
Route conversation events into Zapier, Make, HubSpot, Shopify, or an internal HTTPS endpoint without waiting for a full native marketplace.
Approval-safe action drafts.
Keep high-trust actions reviewable in the task center instead of letting AI fire off opaque automation behind the scenes.
Public answers outside the widget.
Publish visible knowledge-base articles to a hosted help center so visitors can self-serve before or after a chat starts.
Available in dashboard
Start with integration presets instead of a blank webhook.
Pick the outcome, paste the destination URL, test it, and keep every event visible. This closes the alerting and follow-up gap before Dchat expands into deeper native integrations.
Handoff alerts
Send human handoff requests and visitor replies into the channel your support team already watches.
conversation.handoff_requested
Support room pings
Route urgent website support activity into a Discord operations room for founder-led or community-led teams.
conversation.visitor_replied
No-code workflows
Push all conversation events into automations for tickets, spreadsheets, email follow-up, enrichment, and routing.
all events
Lead and contact sync
Create or update CRM records when a chat starts, then attach summaries when the conversation resolves.
conversation.created
Buyer support context
Connect store-side workflows when a shopper asks for help, escalates, or needs human follow-up.
conversation.handoff_requested
AI actions
The action layer should be small, useful, and auditable.
The winning version is not "AI can do anything." It is "AI can do the repeatable support work safely, then ask a human when judgment matters."
Look up context
Order status, subscription state, customer profile, recent conversations, and known account details before AI or a human replies.
Create support work
Create tasks, tag conversations, draft replies, open tickets, and summarize the thread for the person who takes over.
Ask before risky steps
Refunds, cancellations, account changes, and sensitive replies should enter an approval queue instead of executing invisibly.
Positioning
How this closes the YourGPT-style gap without losing Dchat's focus.
- No-code agents across many business processes
- Multi-step actions across connected systems
- Sales, support, internal ops, and automation in one pitch
- Broad integration language that can feel powerful but generic
- Controlled AI support actions for website conversations first, then email after channel expansion ships
- Human approval where trust matters
- Clear operator workflow instead of a broad automation canvas
- AI key ownership, pricing clarity, and a self-hosted path
Start focused
Add AI support now. Connect actions as you grow.
Launch the website chat loop first: AI answers, human handoff, knowledge, and routing. Then add the integrations that remove the most repetitive support work.