Aim for one complete conversation first
A working setup means a shopper can send a message, receive a reply, and reach a person when needed. A visible chat bubble is only the beginning. This guide is for Shopify merchants adding Tidio and considering Lyro afterward.
We did not install Tidio, send messages, or test billing in a merchant account for this article. The interface instructions are summaries of official documentation checked September 19, 2026. The acceptance tests are our editorial suggestions, not a record of actions we completed.
Before opening the trial, choose who will answer, how customers should contact you outside staffed hours, and which delivery and return pages contain current information. If you already use Tidio elsewhere, check the existing-account route before creating another project.
Understand what the trial is for
Tidio offers seven days without a credit card. If you do not choose a paid subscription, the account moves to Free. The trial includes features that may require payment to keep using afterward. Official trial information and trial guide (checked September 19, 2026).
Pick one primary goal: live replies, FAQ automation, or improving an existing handoff. Keep the current customer contact route available while testing. You do not need to move every channel on the first day.
The trial guide identifies paid features that are removed afterward, including operating-hours scheduling and native Shopify order actions. Write down which trial features your intended workflow actually needs. Our pricing guide explains how to budget for continued use.
Follow the documented Shopify installation route
The official guide directs new users to select their Shopify store, find Tidio in the App Store, install it, and complete Tidio's onboarding. Review the access requested during installation. Use the app or the JavaScript installation route, not both. Official Shopify installation guide (checked September 19, 2026).
The same guide describes a manual route for an existing Tidio account. Do not layer a new installation over an old one without checking how the current project is connected.
Our recommended preparation: record the store you are changing, identify any existing chat widget, and decide who will handle messages during the trial. These small decisions make it easier to diagnose duplicate widgets or messages arriving in the wrong place.
Enable the widget, then test a human reply
According to the official guide, activate Tidio Chat Widget in the theme's App embeds and save. It also says the widget needs activation after a theme change. Widget activation instructions (checked September 19, 2026).
For a first test, open the store as a visitor and ask a simple delivery question. Have the assigned staff member respond, then send a follow-up. Check the customer's side as well as the inbox: a received message is not proof of a completed exchange.
Repeat on a phone. Look for overlap with buying controls and verify what happens when nobody is available. Customers should understand whether they are waiting for a live reply or will receive a response later.
If the widget does not appear, check the selected theme, saved settings, and any previous installation. Adding a second installation method can make the problem harder to diagnose.
Add a narrow set of Lyro reference material
Start with questions that have clear, stable answers. Tidio's documentation covers adding pages and individual Q&As in Data sources and testing in Playground. Lyro knowledge-base guide (checked September 19, 2026).
Our suggested test set contains an ordinary question, an exception, and something the material does not answer. For example: standard shipping, delivery to an excluded region, and an unpublished discount. Check whether the answer stays within the policy rather than making a plausible promise.
Keep order actions separate from FAQ testing. The Shopify listing describes order and cart context for staff and order operations through Lyro, but the applicable settings, permissions, and subscription still need checking in your account. Official app listing (checked September 19, 2026).
Test a request to speak to a person before expanding automation. Can the staff member understand the earlier exchange, or must the shopper repeat everything? Our Lyro overview covers the division of work.
Check language and ongoing usage
Lyro lists Japanese as a supported language, with language configuration described under Configure → General. We have not tested Japanese accuracy, Japanese admin-interface availability, Japanese human support, or yen billing. Language documentation (checked September 19, 2026).
For a multilingual store, test the same policy across the languages you serve. Make sure the receiving team can handle an escalated conversation. Fluent wording alone does not establish a correct delivery deadline or return exception.
Review human billable conversations, Lyro conversations, and Flows visitor usage separately. Avoid extrapolating a handful of test messages into a monthly bill without considering handoffs and which features you will keep. Record the chosen allowances and who will review usage after launch.
Decide whether to continue
Will the trial automatically become paid?
The public offer says the account moves to Free unless you choose a paid subscription. If you upgrade during the trial, check the terms of that purchase. Also check whether the customer-facing experience still makes sense when trial-only features end.
How do you cancel a paid subscription?
The documented route is Billing → Subscription → Cancel subscription. Some custom subscriptions require the dedicated team. Widget removal and subscription cancellation are separate; confirm the ended status through your billing route. We have not tested Shopify-billed cancellation. Subscription management (checked September 19, 2026).
When is the setup ready for wider use?
Our suggested threshold is practical: a person can receive and answer messages, unanswered questions reach the right person, and the ongoing feature set and cost are understood. Begin with the workflow that passed, then expand. The trial should produce a clear operating decision, not just a configured widget.
