Two parts of one experience
Your website displays the pages and chat widget. The separately hosted Zelvix API processes conversations and provides the business configuration. A background worker supports asynchronous features such as configured recovery.
The website can run on shared hosting. The repository’s Node API and worker need infrastructure that supports those services.
Connect the correct tenant
Use the deployed API’s HTTPS origin and the publishable key for the tenant representing your website. The widget script is served by that API at /widget.js. The key identifies the business; it is not a private AI credential.
Never place model API keys, database credentials, staff tokens, or email service secrets in your website JavaScript.
Prepare the business settings
Configure the profile, appearance, published knowledge, qualification questions, review rules, and any consent or recovery options. A script tag alone does not create the right sales behavior.
Choose a greeting that introduces what the agent can help with and matches your team’s workflow.
Verify on the actual domain
Check that the widget loads, accepts a message, returns an answer, records qualification details, and provides a useful handoff. Test a case where the agent cannot answer too.
This shared-hosting bundle’s contact form uses a PHP email handler. Confirm inbox receipt on the host; a local static preview cannot execute that handler.
Features depend on your connected services and tenant configuration. Ask our team about your setup.