How to Add an AI Assistant to a SaaS Website
Install Niwa on a WordPress SaaS website, prepare product knowledge, set visitor permissions and test plan questions and the demo booking route.
Add an AI assistant to a SaaS website by connecting it to current product information, enabling a visitor-facing chat and testing the tasks buyers should complete. On WordPress, Niwa provides that customer assistant alongside a separate owner assistant. Your SaaS application can keep its existing login, infrastructure and billing system.
Begin with one useful acquisition task: explaining a plan, answering a documented integration question or helping a buyer reach a demo booking. Installing a plugin is only the first part. The answer needs accurate information and the next step needs a working destination.
Decide where the assistant belongs
Separate your public marketing website from the signed-in product. This guide covers the website where buyers read about features, prices and demonstrations. It does not grant the assistant access to a customer's workspace, invoices or subscription.
An existing WordPress website can use the standalone Niwa AI plugin. If the marketing site uses another platform, decide whether to retain it with an assistant that supports that platform or migrate the website to WordPress. Niwa Business is USD 150 for a custom WordPress website or migration, hosting, maintenance and AI adaptation. Moving the website does not mean rebuilding the SaaS application.
Prepare a small, current knowledge set
Collect the material needed for your chosen task. For plan questions, include the feature table, seat definition, usage allowances, add-ons and billing options. For integrations, include supported connections, plan requirements and setup instructions. A demo needs a description, duration and current availability.
Remove contradictory descriptions before indexing. If a help page says every plan includes API access but the pricing table reserves it for one tier, the assistant needs an agreed answer from your team.
Use public product guidance rather than customer exports or private account records. Give each important page an owner who will update it when the product changes. Start with information you can maintain instead of importing every document you have.
Install and activate Niwa
Have your Niwa ZIP, license key and access to the license email address ready. In WordPress, open Plugins > Add Plugin > Upload Plugin, select the ZIP and install it. Activate the plugin, then open Niwa AI and activate the license with the complete key. Complete email confirmation if the activation screen requests it.
WordPress documents uploading a plugin ZIP through the administration screen. Niwa's installation guide covers its license and account screens. Keep the ZIP from the supplied license route rather than using an unofficial download.
Confirm that Niwa settings open and activation has finished. An installed file and a pending confirmation email are different states.
Connect the model and index the website
In Niwa's Main Settings, choose a supported authentication connection and complete its authorization. Select an available chat model, save the general settings and run the website indexing operation. Check the progress and result before testing answers.
A supported own-subscription connection has no added Niwa AI usage fees or Niwa-imposed usage caps. The provider's terms and limits still apply. An API connection has separate provider billing. Choose the connection appropriate to your account rather than assuming every subscription supports every route.
The owner assistant has separate connection and model settings. A successful owner conversation does not prove that the public visitor assistant is connected correctly.
Enable visitor chat and define its boundaries
Under UI Settings > Frontend Chathead, enable flyout chat and save. Review hidden-page rules and desktop, tablet and mobile positions. Set a useful greeting that invites a product question rather than asking for contact details immediately.
In Frontend Agent Rules, provide your company information, product guidance, policies and human contact route. For example, instruct the assistant to explain documented plans, clarify missing requirements and direct negotiated pricing requests to sales. Keep administrative instructions separate. Niwa's safety guidance explains the distinction between visitor help and owner access.
If demos are part of the workflow, configure the schedule and test the connected booking process. Niwa can answer product questions, offer business availability and book a demonstration from website or WhatsApp conversations. Verify the saved appointment and confirmation, including any website booking route you also offer.
Test as a buyer before inviting customers
Open a private browser window on desktop and mobile. Ask a known plan question, an ambiguous question and one the product documentation cannot answer. Check whether answers use current facts, ask useful follow-up questions and provide a human route when needed.
Then complete the intended next step. For a demo, inspect the saved appointment and confirmation. For a contact form, use a test address you control and verify its destination. These checks establish the whole workflow, not just a visible chat bubble.
If the widget is missing, check the flyout switch, page visibility rules, saved settings and caches. If it appears but cannot answer, inspect the model connection, index and business guidance. When a reply is wrong, correct the underlying information and repeat that case.
Bring a defined task to your setup discussion
Send your marketing website URL, its platform and two real product questions. Explain what a visitor should do afterward and whether you need website chat alone or WhatsApp and demo booking too. Discuss your SaaS assistant setup with Niwa. We can review the standalone plugin or Niwa Business route for that website.
