1. Where does the data live?
Ask where transcripts, visitor details, contacts and audit records are stored, and who can read them. With DChat they sit in your own SQL Server database. With a hosted helpdesk they sit in the vendor's cloud under its policies. Either can be right; the question is which one you can answer for your own compliance review.
Ask also what leaves your network. In a self-hosted product, the only outbound traffic you should expect is what you configure: the AI provider you choose, email you send, and any channel you connect. Read the vendor's documentation for a list, not a summary.
2. What is free, and what do you pay per seat?
Helpdesk vendors price in different ways: per agent, per ticket, per resolution, or a mix. Write down your agent count and your monthly ticket volume, then price both. DChat's Community edition is free for production with unlimited agents and domains. Its help center, contacts and reports are part of Community. Premium costs $19 per covered agent per month and adds the AI agent, custom roles, automation, extra channels and voice.
Ask whether any feature you need is behind a higher tier, and whether a lapse in payment switches features off or stops the product. In DChat, a lapse in paid coverage turns the paid features off, and live chat keeps running.
3. Does the helpdesk include a knowledge base?
Self-service reduces tickets. Check whether the help center is included, whether it supports more than one language and custom domains, and whether the chat widget can search published articles before a visitor starts a chat. DChat's help center, including its portal, categories, articles, languages, custom domains and widget search, is part of the free Community edition.
4. Which AI, if any, and who controls it?
AI in a helpdesk should answer from your own material, show its sources, and hand over to a person when it cannot answer confidently. Check three things: which model it uses, whether you can use your own key or a local model, and what gets sent to the model. DChat's AI agent, part of Premium, can use OpenAI, Anthropic or a local Ollama model, and answers from your help articles, your website and the documents you add.
If you do not want any content sent to a cloud model, a local Ollama model keeps prompts and answers on your infrastructure. The trade-off is hardware and model quality. Read the self-hosted AI chatbot page for the details.
5. What server does it need?
Plan for the runtime, the database and the operating system before you buy. DChat needs the ASP.NET Core 8 runtime, SQL Server 2014 or later (SQL Server 2022 is recommended), and at least 1 GB of RAM, with 2 GB or more recommended. It runs on Windows Server 2016 or later with IIS, on Linux behind Nginx, or in Docker. The full list is on the system requirements page.
Ask who will patch the server, who will back up the database, and how you will restore it. A self-hosted helpdesk is only as dependable as those answers. For DChat, the backup and restore guide lists what to back up and how to test a restore.
6. How do agents work from a phone or a desktop?
Check whether agents need a native app. DChat has no native iOS or Android app. The web dashboard installs on a phone as a web app and can send push notifications. A Windows desktop console is available for agents who prefer an application to a browser tab. If your team needs a native mobile app on day one, a hosted vendor with one may suit you better.
7. How is the licence tied to your site?
Ask whether the licence is tied to a domain, a server, or a number of seats, and what happens when you move the install. A DChat paid licence is tied to the deployment domain you enter at checkout, and it is emailed to you as a signed file. Coverage is prepaid for a set period, and nothing renews automatically. If you host on a subdomain such as chat.example.com, check that your licence matches that exact hostname before you buy, and read the pricing page for the current terms.
8. Which integrations do you actually need?
List the systems your agents use every day, then check each one. DChat posts chat notifications to Slack, Microsoft Teams and Discord for free, and on Premium each conversation can become a Slack thread. Check the integrations page for what is included on each tier, and ask every vendor for a written list of supported integrations rather than a logo wall.
When a hosted helpdesk is the better choice
- You have no one to run a server, a database and backups, and you do not want to learn.
- You need a native mobile app, a large catalogue of ready-made integrations, or a managed SLA from the vendor on day one.
- You want the vendor to carry the uptime risk and the security patching.
Choosing hosted is a reasonable decision. What matters is making it on purpose, after you have checked the points above.
Common questions
Is DChat a self-hosted helpdesk?
DChat is self-hosted live chat with a help center, an email inbox, contacts, reports and automation. It runs on your own Windows or Linux server with SQL Server. It is chat-first: its ticket features are simpler than a dedicated ticketing system.
Are the helpdesk features free?
The help center, contacts and reports, including their CSV export, are part of the free Community edition. Premium, at $19 per covered agent per month, adds the AI agent, custom roles, automation, extra channels and voice.
Is there a mobile app?
There is no native iOS or Android app. The DChat web dashboard installs on a phone as a web app and can send push notifications.
What does a DChat licence cover?
Community needs no licence file. A paid Premium or Enterprise licence is tied to the deployment domain you enter at checkout and is emailed to you as a signed file. Coverage is prepaid for a set period and nothing renews automatically.