Installing LiveChat takes about ten minutes. Copy a snippet, paste it before the closing body tag, done. If you are on Shopify or WordPress you do not even do that much, because there is an integration that handles it.
The install is not the part that decides whether live chat works for your store. The decisions around it are, and most of them have to be made before you paste anything. Pick the wrong plan and you will lose your chat history at 60 days. Put the widget in the wrong place and you will generate conversations you do not want. Commit to hours you cannot keep and the widget will actively cost you sales.
I run Ecommerce Paradise and a high-ticket store of my own, so this is a setup I have done rather than a process I looked up. Everything below about plans and limits came off LiveChat’s own pages on 16 September 2026, read from the source rather than a summary.
Decide the Plan Before You Install, Not After
The entry plan allows one user and keeps 60 days of history. Both of those bite later, and both are cheaper to plan around than to fix.
Before You Install: Three Decisions
Get these wrong and you will be redoing the setup in three months, so spend ten minutes on them now.
How many people will answer chats. LiveChat’s Starter plan at $19 per person per month allows exactly one user. Not one included seat with more available, one user. The second person moves you to Team at $49 each, so two people is $98 a month rather than $38. If you already know a VA will be answering alongside you, start on Team and skip the migration.
How long you need chat history. Starter keeps 60 days. Team and Business keep it indefinitely. On a high-ticket product where a buyer researches for months before purchasing, a conversation from March is gone by June, which is exactly when you want to read it. This is the gate that catches the most people.
Whether you are going to answer at all. Not a glib question. An unanswered widget is worse than no widget because it sets an expectation and breaks it in public. Decide your hours honestly before you install, because the setup below assumes you will actually be there.
Step One: Start the Trial
Every LiveChat plan comes with a 14-day free trial and no credit card is required. Take the trial on the plan you think you will buy rather than the cheapest one, because the point of the trial is to test the real configuration and the gates differ by tier.
If you are not yet sure live chat is worth paying for at all, there is a case for testing on a free tier first. Tidio publishes a free plan at $0 a month covering 50 answered conversations and ten seats, which is enough to find out whether anyone actually wants to talk to you before any money changes hands. Come back to LiveChat once you know the answer.
Step Two: Install the Widget
There are two paths and the right one depends on your platform.
The code path. LiveChat’s own instructions are to open Settings, then Channels, then Website, copy the code, and paste it before the closing body tag of your site. That is the whole procedure. It goes on every page you want the widget to appear on, which on most platforms means the theme layout file rather than individual pages.
The integration path. LiveChat documents prebuilt integrations for Shopify, WooCommerce, WordPress, Wix, Weebly, BigCommerce, Big Cartel, Magento 1 and 2, OpenCart, Zen Cart, Drupal and Joomla, with more in its marketplace. If your store is on any of those, use the integration rather than the snippet. It installs the same widget and it survives theme updates, which hand-pasted code does not always do.
On Shopify specifically the integration earns its place, because it does more than install the script. LiveChat’s own listing for the app says it gives agents order status, tracking numbers and delivery details during a chat without switching applications, and lets them send product cards containing an image, a description and a link to the product page. On a high-ticket store, being able to drop the right product into a conversation without asking the customer to go hunting for it is worth the five minutes of setup.
Step Three: Check What You Just Did to Your Page Speed
This step gets skipped and it should not, because a chat widget is a third-party script and third-party scripts are the most common cause of a store that suddenly feels slow.
Install the widget, then run your product page through a page speed test before and after. You are looking for a meaningful change in how long the page takes to become interactive. Google’s guidance on third-party JavaScript is worth reading once if you have never thought about this, because the same principles apply to every pixel and app you will add later.
In practice LiveChat’s widget is one of the better-behaved ones in this category and you are unlikely to see a problem from it alone. The reason to measure is that it will not be the only third-party script on your store, and the one that breaks your page speed is usually the fourth one you added rather than the first.
Building the Store, Not Just the Stack?
Live chat is one line item. Suppliers, entity, store and launch are the other four. We build all of it with you.
Step Four: Decide Where the Widget Appears
The default is everywhere, and everywhere is wrong for most stores.
Conversations are not free even when the software is. LiveChat does not meter conversations on any tier, so the cost is your attention rather than your bill. What the Starter plan does cap is visitors tracked, at 100, and putting the widget on pages nobody buys from spends that allowance on people who were never going to buy. So the question is not how to get more conversations, it is how to get the conversations that lead somewhere.
Product pages, yes. Someone reading the spec sheet on a $2,800 item has a question that is stopping them buying. That is the highest-value conversation you will have all week.
Cart and checkout, yes. LiveChat’s listing for its Shopify app says the widget appears on checkout pages, and names the concerns it is there to catch as shipping fees, missing payment options and technical problems interrupting the purchase. All three are recoverable if someone is there to answer and unrecoverable if not.
Blog posts, usually no. Informational traffic generates questions that are not about buying anything. You will spend your attention on people who were never going to purchase, and on Starter you will spend your visitor allowance on them too.
Policy and FAQ pages, your call. A person on your returns page is either a customer with a problem or a prospect checking you are legitimate. Both are worth talking to, so this one depends on whether you have the capacity.
Step Five: Set Up Greetings Deliberately
LiveChat’s pricing page counts these as recurring campaigns and its help centre calls them automatic invites. Either way they trigger a chat invitation based on what a visitor is doing. The Starter plan includes one, Team and Business allow unlimited.
One is enough to start, and the fact that Starter only gives you one is a useful constraint rather than a limitation. Spend it on the highest-value trigger you have, which for a high-ticket store is usually time spent on a product page. Someone who has been reading the same product for three minutes is deciding, and that is the moment where a question gets answered or a sale gets lost.
Resist the urge to trigger on arrival. A greeting that fires two seconds after someone lands reads as a popup, and it trains people to close the widget before they ever have a real question.
Step Six: Write Your Canned Responses Before You Need Them
The single highest-return part of the setup, and the one everybody postpones.
Sit down and write answers to the questions you already know are coming. For a high-ticket store that is usually shipping timelines, freight and delivery arrangements for large items, return policy and who pays return shipping, warranty terms, lead times on anything not in stock, and whether the item is in stock at all.
Doing this before launch rather than after has two benefits. The obvious one is speed. The less obvious one is that writing them forces you to notice which answers are bad. If your return policy is genuinely hard to explain in three sentences, the problem is the policy, and you have just found it before a customer did.
Step Seven: Set Hours You Will Actually Keep
Configure your availability to match reality, not ambition. A widget that shows offline outside your hours sets a clear expectation and keeps it. A widget that shows online while you sleep does the opposite.
If you are solo, pick a window you can genuinely defend and state it. Four reliable hours beats twelve unreliable ones, and on a high-ticket product a customer who gets a considered answer tomorrow morning converts better than one who gets a rushed answer at midnight.
If you have a VA, this is where the Team plan starts paying for itself, because two people covering different time zones is a materially better experience than one person pretending to be available.
What to Measure in the First Two Weeks
The trial is where the decision actually gets made, and most people waste it by installing the widget and waiting to see what happens.
Your visitor count against the tier gates. Starter tracks up to 100 visitors, Team up to 400, Business up to 1000. Two weeks of real traffic tells you which side of those lines you sit on, and that decides your plan more often than headcount does.
Conversations that led somewhere. Not total conversations. On a high-ticket item, two real ones a week justify the subscription comfortably. On a thin-margin catalogue the same volume may not. You need your own number here rather than a vendor case study.
Your actual response time. Whatever you promised yourself, measure what happened. This number tells you whether your chosen hours are honest.
Which pages the conversations came from. If most of them came from your blog, move the widget. If most came from product pages, you have configured it correctly and you should consider a second trigger.
What You Do Not Get Out of the Box
Worth knowing before you build a workflow on assumptions.
Ticketing is a separate product. LiveChat’s pricing page lists HelpDesk as an add-on starting at $29 a month if you want email turned into a ticketing system alongside chat.
A knowledge base is another one. KnowledgeBase is also sold separately, starting at $49 a month. If your plan is chat plus self-service content, the real monthly cost is $19 plus $49 rather than $19.
Reporting depth is gated. Starter has none to speak of, Team adds basic reporting, and the scheduling and forecasting tools live on Business. Work scheduler, staffing prediction and agent performance reporting are department features, and a two-person operation will not use them.
SMS and Apple Messages for Business are Business tier. If those channels matter to your customers, that is a $79 per person decision rather than a setting.
What the AI Layer Actually Changes
LiveChat lists Text Intelligence on every tier including Starter, and describes an AI agent that it says solves up to 80 percent of cases before handing off to a human. That figure is the vendor’s own claim and I would treat it as a ceiling rather than a plan.
The setup implication is real though. If automation handles the repetitive questions, the canned responses you wrote in step six become the training material rather than the thing you paste by hand. Writing them well pays twice.
My honest position on AI in a high-ticket context: use it for the questions that have one correct answer, like where an order is or what the return window is. Do not use it for the conversation where someone is deciding whether to spend $3,000 with a store they have never heard of. That conversation is the reason you installed live chat.
A Reasonable First Configuration
If you want a starting point rather than a set of principles, this is what I would set up on day one.
Start the 14-day trial on Team if a second person will ever answer chats, or on Starter if you are genuinely solo and under the visitor cap. Install through the platform integration rather than the snippet if your store is on Shopify or WordPress. Show the widget on product, cart and checkout pages only. Configure one greeting, triggered on time spent on a product page. Write eight to ten canned responses covering shipping, returns, warranty and stock. Set your hours to a window you can defend. Then leave it alone for two weeks and look at the four numbers above.
That configuration is deliberately modest. Live chat rewards doing a few things reliably far more than it rewards a clever setup nobody maintains.
Every Tier, Every Gate, Before You Commit a Year
The single-user cap, the visitor limits, the 60-day history, and what a team of three actually costs.
If the Setup Is Not Working
Three failure modes account for most of the disappointment with live chat, and none of them is a software problem.
No conversations at all. Usually the widget is on the wrong pages or your traffic is too low for chat to be the right tool yet. Live chat converts traffic you already have, and if the traffic is not there the widget cannot manufacture it.
Plenty of conversations, no sales. Usually the widget is on informational pages. Move it to product and checkout and watch the ratio change.
Conversations you cannot keep up with. A good problem, and the point at which the plan question comes back. Either the hours narrow, or a second person joins and you move to Team, or automation takes the repetitive half.
Whichever applies, do not solve it by paying for a higher tier first. Fix the configuration, then decide whether the tier is the constraint.
Where Live Chat Sits in the Build Order
Worth saying, because a chat widget is a popular early purchase and early is usually wrong.
Live chat converts traffic you already have. It does not create traffic and it will not rescue a store nobody is visiting. If you are pre-launch or in your first few months, this is not the setup to be perfecting.
What matters at that stage is what you sell, which the high-ticket niches list covers at no cost.
Supplier approval is the real bottleneck in this business and no software setup moves it. The whole process is in the supplier sourcing guide.
Distributors want a registered entity before they will discuss terms, which the business formation guide walks through. If the model itself is still an open question, read what high-ticket dropshipping actually is before configuring any software at all.
Common Questions
How do I install LiveChat on my website?
Open Settings, then Channels, then Website, copy the code, and paste it before the closing body tag. If your store runs on Shopify, WooCommerce, WordPress, Wix, BigCommerce or Magento, use the prebuilt integration instead, because it survives theme updates.
How long does setup take?
The install itself is about ten minutes either way. Configuring greetings, canned responses and hours properly takes an afternoon, and that afternoon is what decides whether the widget earns its subscription.
Do I need a credit card to try it?
No. Every LiveChat plan has a 14-day free trial with no card required. Take the trial on the plan you intend to buy, since the gates differ by tier.
Where should the widget appear?
Product pages, cart and checkout. Keep it off blog and informational pages unless you have spare capacity, because those conversations rarely lead to a sale and on Starter the visitors reading them consume your 100-visitor tracking allowance.
Can I add LiveChat to a Shopify store?
Yes, through the Shopify integration. LiveChat’s listing for the app says it does more than install the script: agents get order status, tracking numbers and delivery details during a chat, and can send product cards containing an image, a description and a link.
Does LiveChat include ticketing and a knowledge base?
No, both are separate products. HelpDesk starts at $29 a month and KnowledgeBase starts at $49, so a full support stack on the entry tier is $19 plus $29 plus $49 rather than $19.
What breaks first on the cheapest plan?
The 60-day chat history, usually before the visitor cap. If your buyers research for months before purchasing, the record of the first conversation disappears at exactly the point it becomes useful.
Related Articles
- LiveChat Pricing 2026: The $19 Plan Allows One Person
- LiveChat vs Tidio in 2026: One Charges Per Seat, One Per Answered Conversation
- LiveChat Alternatives 2026: One Competitor Gives You 10 Agents Free
- LiveChat Review 2026: The Best Live Chat Software for Ecommerce Stores?
- Best Live Chat Software for Small Business in 2026: 10 Top Picks
Trevor Fenner is an ecommerce entrepreneur and the founder of Ecommerce Paradise, a platform focused on helping entrepreneurs build and scale profitable high-ticket ecommerce and dropshipping businesses. With over a decade of hands-on experience, Trevor specializes in high-ticket dropshipping strategy, niche and product selection, supplier recruiting and onboarding, Google & Bing Shopping ads, ecommerce SEO, and systems-driven automation and scaling. Through Ecommerce Paradise, he provides free education via in-depth guides like How to Start High-Ticket Dropshipping, advanced training through the High-Ticket Dropshipping Masterclass, and fully done-for-you turnkey ecommerce services for entrepreneurs who want a faster, more hands-off path to growth. Trevor is known for emphasizing sustainable, real-world ecommerce models over hype-driven tactics, helping store owners build scalable, sellable, and location-independent brands.
Still deciding what to sell?
Grab the free list of 1,000+ niches that work for high-ticket dropshipping, sorted by category.
Free. Unsubscribe any time.
