YundaDeskChoose free AI customer service software by checking the plan allowance and testing a complete conversation on your own website. A hosted service is a practical starting point when your team does not want to maintain the support server itself.
For a small team, the immediate job is usually concrete: answer a visitor’s delivery question, bring a person into a conversation that needs judgment, and preserve enough context for the next colleague. A chat button or an automated greeting verifies only part of that journey. Use actual receipt, answers and handoff to decide whether the service fits.
The plan details below were checked on September 14, 2026. Use the current pricing page and the information in your workspace when making a purchase decision.
Separate a free plan, a trial and self-hosting
A free plan is a subscription tier priced at zero, subject to the vendor’s published conditions. A trial provides access for a defined evaluation period; check what happens to access and data afterwards. Self-hosted open-source software requires a deployment and maintenance arrangement, including servers, updates, security work and recovery.
For a team without dedicated operations staff, a hosted service lets the operator focus on preparing support knowledge, connecting the website and testing responses. “No self-hosting” refers to the support service. The website still needs its visitor-facing widget or plugin installed. Creating an account alone does not place a working chat entry on a website.
If your team has a clear reason to run its own infrastructure, compare that option using an ownership checklist: who updates the software, handles incidents and verifies recovery? Include those responsibilities in the decision. The right choice depends on the work the team can sustain, as well as the subscription price.
Check the allowance against a real workflow
Write down the people who will respond, the websites you want to connect, the recurring questions AI should answer, and the situations a person should handle. Then compare seats, channels, conversation volume, message volume and AI usage as separate items.
A plan’s channel allowance does not establish that a particular account has been connected. An application listing does not verify your store’s authorization. Start with one website and confirm a message travels in both directions before extending the setup. This makes configuration problems easier to isolate.
Also decide who maintains product information and service policies, who checks sample answers, and who handles questions that require judgment. An allowance determines capacity; clear ownership helps keep the workflow useful. A solo operator can begin with a small set of recurring questions supported by current business information and expand it as real conversations expose new needs.
What the current YundaDesk Free plan includes
The official pricing page lists Free at US$0, with no credit card required to get started. Seats, channels, conversations and messages are unlimited. Free includes 1,000 AI credits per month and the product’s full feature set, with YundaDesk branding removal available on paid plans.
Starter has a base price of US$20 per month and includes 10,000 AI credits per month. Pro has a base price of US$200 per month and includes 100,000 AI credits per month. Both include YundaDesk branding removal. Billing periods, discounts and upgrade adjustments can affect the amount due; the workspace order is the purchase reference.
Treat branding removal as that specific capability rather than inferring a broader service-delivery package. Likewise, an AI credit is a usage unit, not a promise that one message or conversation consumes one credit. Observe usage for your own set of questions before estimating the allowance you need.
The pricing page also describes a one-time registration grant, with the actual amount determined by the workspace. Keep a one-time grant separate from the recurring monthly allowance. A starting balance that includes a grant is not a reliable estimate of long-term monthly cost.
AI credits included each month
To evaluate the service, a small team can begin with Free, connect a website and test a set of actual questions. A decision to upgrade should reflect AI usage, branding requirements and current pricing. Adding a colleague does not by itself establish a need to upgrade under the current unlimited-seat allowance.
Choose the entry point for your website
For a regular website, follow the website widget installation guide. Check the project and domain, use the installation method provided there, and open the intended page as a visitor. Send a test message, confirm that the same message arrives in the workspace, reply, and verify that the visitor receives it. This checks both directions.
For WordPress, start with the WordPress/WooCommerce help entry. Install the plugin and connect the site to the intended YundaDesk workspace. Check the website address and project before testing the widget. Installation, workspace connection and reception settings each serve a different purpose; verify them individually.
For WooCommerce, the same WordPress plugin provides an optional store enhancement. When store information is needed, an administrator separately approves Read access using the WooCommerce enhancement guide. Check the initial synchronization and the selected store, then verify an order using the customer’s order email. A working chat window alone does not establish that the correct order can be retrieved.
Test answers, handoff and the visitor experience
First, choose several questions grounded in your current policies, such as delivery coverage, dispatch timing or product use. Record an acceptable answer and its source before asking AI. Review whether the reply reflects the current information, includes relevant conditions and stays consistent under follow-up questions. A generic company introduction is not enough to evaluate support answers.
Next, test a situation that calls for a person, such as an after-sales case requiring investigation. Carry out a handoff in the workspace. Check that the operator has the earlier context, can continue the conversation, and that the visitor receives the intended reply. Record the site, project and test conversation so an unexpected result can be investigated accurately.
Then open the widget on the pages visitors actually use, including product and cart pages where relevant. On a phone, check that the chat entry can be tapped, the input remains usable and important page controls remain accessible. A desktop homepage check cannot substitute for all page layouts. When using multiple sites, test each site separately.
If the widget is missing, compare the page, domain and installation location with the guide. If it opens but produces no reply, separate message delivery from reception configuration: did the visitor’s message arrive, was the correct workspace selected, and does the current reception setup match the test? For an order lookup issue, verify the store, email, authorization and synchronization. Change one relevant factor, then repeat the affected check so you can tell what changed the result.
Decide what to improve before adding more capacity
Separate three questions in your evaluation: did the feature work, did it reduce repeated handling for the team, and did it contribute to a traceable business action? Functional tests can establish the first. Real support work can help assess the second. The third needs visits, inquiries or registration records; installing AI alone does not establish a conversion increase.
Once recurring questions receive accurate answers and a person can take over reliably, expand the knowledge coverage or another verified entry point. Review actual AI usage when comparing plans. If the main difficulty is outdated information or an incorrect reception setting, fix that first. More credits do not by themselves make the underlying answer more accurate.
To start, open a free workspace, choose the installation guide for your website, and complete one end-to-end conversation: a visitor asks, the workspace receives it, an accurate reply returns, and a person takes over when needed. That is a useful basis for choosing a support tool your team can maintain.
