Website AI assistant

An assistant helps visitors choose a service and make an enquiry. Rupor on INTO demonstrates this flow: reference answers work without external AI, while model-based conversation requires a separate choice.

When to use it

Suitable for service websites with frequent questions and multiple offerings. The assistant explains differences, finds relevant pages and helps shape a brief. Questions outside its knowledge should go to the team rather than receive invented answers.

Deliverables

We agree topics, knowledge, design, languages, server AI integration and the form. Implementation includes request limits, server-only keys, consent checks and evaluation conversations. CRM, analytics and maintenance are estimated separately.

What to prepare for an estimate

Share the website, service list, frequent questions, contacts and desired lead workflow. Specify hosting and technical constraints. Before launch, we check that public content and bot answers agree.

Terms and limitations

The bot should not take payment, promise contract terms or send contacts to a model without a separate basis. Flood protection limits abuse; provider-side spending caps are also needed.

Common questions

What happens if the model is unavailable?

We provide reference answers and a route to the form or a person. INTO’s reference mode runs in the browser without sending questions to an external model.

Can visitors see API keys?

Keys remain server-side. The browser uses only the website’s protected API; visitors cannot choose the model, limits or notification recipients.

Related practical guide →

Tell us what you want to make. We will clarify the scope, rights and schedule before work starts.

Send an enquiry