Jimdo does not include a built-in live chat or chat support widget, so any chat on a Jimdo site has to come from a third-party tool you add yourself. Jimdo's own support for you, the site owner, runs through its help center and email or form contact, not through a chat window on your published site.
That gap matters if you run a small business on Jimdo and your customers keep asking the same questions. This article explains what Jimdo actually offers, what your realistic options are, and how to decide between them.
Does Jimdo have chat support?
No, Jimdo does not offer a native chat support feature for visitors on your website. What Jimdo does provide is support for you as the account holder, and it is worth separating the two things clearly, because people searching this term usually mean one of them.
Support from Jimdo to you
Jimdo's help for site owners is documentation-led. You search the help center, read the article, and follow the steps. When that is not enough, you contact the team through the channels Jimdo lists in your account, typically a form or email. Response times depend on your plan and on how busy the queue is. There is no live chat window where you sit and watch an agent type.
Chat on your Jimdo site, for your customers
This is a different question, and the answer is also no by default. Jimdo does not ship a chat widget you switch on. If you want visitors to be able to ask a question in a chat window on your Jimdo page, you add a third-party tool.
That distinction saves a lot of frustration. If you are looking for faster answers about your own Jimdo account, chat is not the channel. If you want your customers to get instant answers, you are shopping for a tool, not a Jimdo setting.
How do I add chat to a Jimdo website?
You add chat to a Jimdo site by pasting a small embed snippet from a third-party chat or AI agent tool into your site's code area, or by using a widget integration the tool provides. Jimdo supports custom code, which is what makes this possible.
The general steps look like this:
- Create an account with the chat or AI support tool you want to use.
- Configure the widget: name, colours, greeting text, hours.
- Copy the embed snippet the tool gives you.
- In Jimdo, open the settings for the page or site where you want chat to appear and add the code to the custom code or embed field.
- Publish, then open your live site in a browser and test the widget as a visitor would.
A few practical notes from doing this on small sites:
- Test on a phone, not only on your laptop. Most visitors on small business sites arrive on mobile, and a widget that covers the whole screen on a phone is worse than no widget.
- Decide where chat appears. Site-wide is usually right, but a booking or checkout page sometimes deserves its own behaviour.
- Write your greeting as a real question. "Hi, how can we help?" invites anything. "Questions about delivery times or returns?" gets you useful messages.
- Check what happens when nobody is online. If messages land in an inbox nobody reads until Monday, say so in the widget rather than implying instant help.
What are my options for chat support on a Jimdo site?
There are three workable options, and they differ mainly in who does the answering and when. The table below is a fair summary.
- Live chat with your own team: Who answers: A person on your staff; Availability: Only when someone is at the desk; Best for: Businesses with staff who can watch a chat window
- A rule-based chatbot: Who answers: A script with fixed buttons and answers; Availability: 24/7; Best for: A handful of very predictable questions
- An AI support agent trained on your content: Who answers: An AI that reads your pages and documents; Availability: 24/7; Best for: Businesses whose answers already exist on their site
Live chat with your own team
The strength is judgement. A person can handle an angry customer, a special case, a negotiation. The weakness is arithmetic: someone has to be there. For a two-person business, staffing a chat window through the working day is a real cost, and evenings and weekends are usually uncovered, which is exactly when many visitors browse.
Rule-based chatbots
These follow a decision tree. If your customers ask five predictable things, a decision tree can cover them. The moment someone types a question that is not on the tree, the bot either loops or says it does not understand, and the visitor leaves. Rule-based bots age badly, because every new product or policy means someone has to redraw the tree.
AI support agents trained on your own content
This is the newer option and the one most Jimdo owners searching for chat support are really after. Instead of a decision tree, the agent reads your website pages, help articles, product information and policies, then answers visitor questions in plain language and points to where the answer came from.
The important part is the source. An agent that answers from your own content can be checked: you can open the page it cites and confirm the answer is right. An agent that answers from general knowledge will sound confident and be wrong about your delivery times, your return window or your opening hours.
Will a chat widget on Jimdo actually reduce my workload?
It reduces your workload only if the questions it answers are the questions you already answer by email, and only if it hands the rest to you with context. Those two conditions decide everything.
Before you install anything, do a simple audit. Open your inbox and your contact form history from the last month. Sort the messages into three piles:
- Questions already answered somewhere on your website or in your documents.
- Questions that need a person: complaints, special requests, pricing negotiations.
- Messages that are not really questions: spam, job applications, sales pitches.
The first pile is what a chat agent should absorb. In most small businesses it is the biggest pile, and it is also the most repetitive. The second pile is what should reach a human quickly, with the conversation attached, so the customer does not have to repeat themselves. The third pile is noise you should filter, not answer.
If the first pile is small, chat will not save you much. If it is large, the saving is real, and it shows up as fewer interruptions rather than as a dramatic number on a dashboard.
What should I check before choosing a chat tool for Jimdo?
Check five things before you commit: where the data is stored, whether answers cite sources, how human handoff works, what happens when your content changes, and what the pricing does as you grow.
- Data location and privacy. If your visitors are in the EU, ask where conversations are stored and under which rules. EU data residency and GDPR-compliant handling are reasonable things to require, not extras.
- Source citations. Ask to see the agent answer a question and show the page it used. If it cannot show its source, you cannot verify it.
- Human handoff. When the agent cannot help, the conversation should move to a person in the same thread, with the transcript and the cited sources attached.
- Content freshness. Your prices, hours and policies change. The agent needs to re-read your site after those changes, not once at setup.
- Pricing shape. Flat pricing that grows with your usage is easier to plan around than a per-seat model that punishes you for adding a colleague.
Adding an agent that answers from your own Jimdo content
Chatixy is an AI support agent that reads your website and documents, answers visitors 24/7 and cites the pages it used, then hands the conversation to your team with the full transcript when a person is needed. It is EU-hosted with EU data residency and GDPR built in, needs no code beyond a single snippet, and works with a Jimdo site the same way it works with WordPress, Shopify, Wix and other platforms.
You paste your website address, the agent reads your pages and help content, and you can watch it answer in minutes. Escalated conversations land in a shared inbox with the conversation attached, so nobody asks the customer to explain again.
Get started with a 7-day free trial. Add your URL, customize the support agent and watch it answer in minutes.