Chat on product pages: each message a shopper sends makes a request. If Olvio needs to look through your catalog for another product to answer, that message makes a second request.

Product cards: when a shopper's message names products from your catalog other than the one on the page, and the answer didn't already show them as cards, a short extra request checks which of them the answer actually recommends before their cards are shown.

Unanswered questions: when the AI can't answer a question and other products were part of the conversation, a short request in the background may work out which product the question is about, so it's listed under the right product on the Unanswered tab of Conversations.

Olvio Advisor (Growth and Scale): each message in an Advisor conversation makes a request, including the chip label sent as the shopper's first message when an Advisor link starts a new conversation. A message that needs a catalog search makes a second request.

Suggested questions: when a shopper opens a product page and no suggested questions are stored for that product in the language the widget uses on that page, Olvio makes a request to write its 2 suggested questions. Once shoppers have asked enough questions about a product, Olvio refreshes its suggested questions from what they asked, up to about once a day per language. Stored suggested questions are also refreshed regularly, which makes a new request on the next visit.

Your own questions: if you set both questions for a product on the Questions page, shoppers browsing in your store's default language see them without any request. When one of the two is still AI-generated, the first visit with nothing stored for that product in that language makes a request to generate suggested questions. In another language Olvio serves for your store, that first visit makes two requests, even when both questions are yours: one to translate your questions into that language and one to generate suggested questions for that product. The result is then stored and refreshed like any suggested questions. Saving a product on the Questions page doesn't send a request, but it clears that product's stored suggested questions in every language Olvio serves for your store. The next visit in each language then makes requests as described above, except in your default language when both questions are yours.

Saving your key or model: when you save a new key or change the Claude model on the API Key page, Olvio sends a very small test request with the selected model to check that your key can use it. Delete key doesn't send a request.

Widget text translation: when your widget serves a language other than your default language and that language is English, French, German, Spanish, Italian or Portuguese, saving a changed Expert name or Hook question on Widget → Product Detail Page translates them into your served languages among these six. The same translation runs when you save the page and a translation is missing, for example after you add a language, and when the number of languages your plan serves grows, for example after an upgrade.

Contact block translation: saving the expert name, hook question or questions on Widget → Contact translates them into the other languages your widget serves. Missing translations are also filled in when you add a language or your plan serves more languages.

Customer question map: Olvio rebuilds the map every night once your store has enough recent shopper questions, and when you click Build map now or Rebuild. Each build sends a request that names its themes.

Unanswered questions: if your storefront publishes more than one language, each time Olvio groups the list on the Unanswered tab of Conversations, overnight or when you click Reorganize, one request translates the grouped questions into your store's default language (into English if that language isn't English, French, German, Spanish, Italian or Portuguese). See Find and fix knowledge gaps on the Unanswered tab.

Overnight suggested questions: each night, Olvio looks at the active products imported or updated during the last day, including every product after a full catalog import, such as the first import after you choose a plan or when you click Resync now. For each language it serves for your store, it writes new suggested questions for these products, with two exceptions. It usually makes no request for a product that already has suggested questions in that language when Olvio recently confirmed that its content, such as its title, description, tags or metafields, hasn't changed. And it doesn't generate suggested questions for a product whose two questions you set on the Questions page: in your default language it stores your questions without a request, and in another language it only sends a request to translate them. The night after a full catalog import can therefore send many requests with your key.

Importing and indexing your products, store pages, blog articles and policies so Olvio can search them. Imported or updated products can still get new suggested questions the following night, as described above.

The catalog search itself, when Olvio looks for products that match a shopper's question.

Grouping questions into themes on the Customer question map, and grouping near-duplicate questions on the Unanswered tab of Conversations.

Saving your settings on the AI Setup and Advisor pages, including reading your knowledge files and external web pages.

Your dashboard and your conversations list.

Choose Claude Haiku 4.5 — fastest, lowest cost (recommended) on the API Key page unless you need more answer quality. Compare the models on Anthropic's pricing page and see Choose your Claude model.

Set a spend limit in the Claude Console: open Settings → Billing, then in the Spend limits section click Adjust limit (or Set limit). Once the limit is reached, Anthropic refuses new requests until you raise the limit or access resumes. During that time, Olvio's chat and Advisor stop answering, and a product page whose suggested questions need a new request shows none.

Serve only the languages you need: every language Olvio serves for your store gets its own suggested questions, and your widget text and your own questions are only translated when it serves more than one. Translating the Unanswered list doesn't depend on this: it runs when your storefront publishes more than one language. On Growth, if your storefront publishes at least one language Olvio supports besides your default language, you can uncheck your second language in the Languages card on the Advanced tab of Appearance and save to serve your default language only. On Scale, there's no language choice: the widget serves every published language Olvio supports. The exception is a store that unchecked its second language on Growth and saved: it keeps serving its default language only on Scale, so check the language again and save before you upgrade. If you've already upgraded, contact us: see Contact us and support hours. See Multi-language: choose which languages your widget serves.

Set both suggested questions for your most visited products on the Questions page. Shoppers browsing in your default language then see them without a request. In other languages Olvio serves, those products still make requests to translate your questions and generate suggested questions, so this saves the most when your widget serves only your default language. See Customize the suggested questions on your product pages.

Keep your knowledge base focused. The requests that write chat and Advisor answers include your AI Setup information, your most recent knowledge files and web pages, product details and the recent messages of the conversation, so longer content can make those requests larger.

Click Resync now only when you need it. The night after a full catalog import, Olvio can write new suggested questions for all your products, in each language it serves. See Resync your product catalog.