WordPress powers a large share of the web, so every live chat vendor supports it. There are two ways to do it: install a dedicated WordPress chat plugin, or paste a hosted chat widget's script into your site. This guide compares them, shows both installation methods step by step, and covers the caching and performance issues that trip people up.
Some plugins run the whole chat system inside WordPress: messages are stored in your database and agents answer from wp-admin. They're cheap and keep data on your server, but they add load to your hosting and database, depend on WordPress staying fast, and rarely offer mobile apps, routing or translation.
Most live chat services, including ZhiDesk, run on their own servers. WordPress only loads a small script. Many vendors offer a thin "connector" plugin, but underneath it just inserts the same script. This keeps WordPress light and gives you features such as routing, reports and translation that plugins rarely match.
Rule of thumb: a self-hosted plugin can make sense for a very small site with one person answering. Once you have multiple agents, multiple languages or real traffic, a hosted widget is easier to run.
This survives theme updates and theme changes, which is why it is the recommended option.
If you already maintain a child theme, add the snippet to its footer.php right before <?php wp_footer(); ?>, or enqueue it from functions.php with a hook on wp_footer. Never edit the parent theme; updates will erase your change.
Block themes such as Twenty Twenty-Four and later don't have a classic footer.php, and the Site Editor strips raw script tags from Custom HTML blocks for users without the right capability. Use the code-plugin method, which works regardless of theme type.
A hosted widget loaded asynchronously adds very little to page weight and doesn't block rendering. A self-hosted plugin, by contrast, may poll your server every few seconds for new messages, which can be noticeable on shared hosting. Run PageSpeed Insights before and after installation if you care about Core Web Vitals.
If you use WPML, Polylang or TranslatePress, your visitors already read your site in several languages, so they'll ask questions in those languages too. Two things matter:
lang attribute (which WPML and Polylang set) and the browser language, and shows its interface in one of 18 languages.For WooCommerce, the widget appears on product, cart and checkout pages, which is where buyers hesitate. Prepare canned replies for shipping costs, delivery times, returns and payment methods; these cover the majority of pre-sale questions.
Translation is included on every plan, from US$49/month for three agents.
For most sites, paste a hosted chat widget's script into a header/footer code plugin such as WPCode. It survives theme updates and keeps chat traffic off your WordPress server.
A hosted widget loaded asynchronously has minimal impact. Self-hosted chat plugins that store messages in your database and poll your server can add noticeable load on shared hosting.
Yes. Choose a widget that follows the page language and offers two-way translation, so visitors on each language version can chat in their own language.