FOR FOUNDERS RUNNING SEVERAL PRODUCTS

An AI chatbot for every website you run. One inbox for all of them.

If you run more than one product, you probably have a different chat tool on each, or a support bot you meant to build and never shipped. JIVIQ gives each website its own AI assistant that answers from that product's docs. You sign in once and answer every conversation from one inbox, and each chat stays tied to the product it came from.

check_circle A knowledge base per website check_circle One login, one inbox check_circle Answers only from your docs check_circle Unlimited teammates check_circle No card for the trial

Ask JIVIQ's own assistant

This is the same widget you'd install. It answers from jiviq.com's docs, the way yours would answer from your product's.

Your question opens the chat in the corner of this page.

THE PROBLEM

What support looks like when you run three products

Each new product tends to get its own support setup. By the third one, you spend more time switching tools than answering customers.

apps

A different chat tool on each site

One product uses a live chat tool, another has a docs chatbot, and the side project has an email link. Each has its own login, settings and bill.

inbox

Several inboxes to check

You check the tool for your main product and forget the others. Questions on the smaller products wait until you remember to look.

construction

The bot you meant to build

Pointing a language model at your docs takes a weekend. Checking its answers, handing off to a person, a widget and an inbox take much longer, and you maintain all of it for every product.

update

Answers that go out of date

When a product changes, a bot trained on last month's docs keeps giving last month's answers. With several products, something is always out of date.

person_search

The same customer, twice

Someone who uses two of your products looks like two strangers when their chats live in two different tools.

group_work

Seats for occasional helpers

A co-founder or contractor who helps on one product still needs a paid seat in per-seat tools.

HOW IT WORKS

One workspace per website, one place to answer

Each website or domain is a workspace. More in Understanding workspaces.

1

Add a workspace per website

Each website gets its own workspace, with its own chat widget and a standalone chat link you can share anywhere.

2

Give each product its docs

Import that product's pages from its sitemap or llms.txt, or upload files. Each assistant answers from its own product's knowledge base.

3

Paste one script tag

Install the widget on each site with one script tag. Set each assistant's name, tone and AI mode separately.

4

Answer from one inbox

Sign in once. Conversations from every website arrive in one inbox, each tied to its product, and all of them feed one shared customer record.

SEPARATE AND SHARED

What each website gets, and what you share

Each product keeps its own voice and knowledge. You keep one place to work.

language

Separate for each website

  • check Its own chat widget and chat link
  • check Its own knowledge base
  • check Its own assistant name, branding and tone
  • check Its own AI mode: Autopilot, Copilot or Off
hub

Shared across all of them

  • check One login
  • check One inbox, with each chat tied to its product
  • check One customer record across products
  • check Unlimited teammates on every plan
BUILD OR USE JIVIQ

What a support bot needs beyond the first weekend

Answering from your docs is one part of support. This is the rest, for every product you run.

What you need Build it yourself JIVIQ
Answers from your docs Retrieval and prompts you write and tune Included. Each reply is checked against your docs before it's sent
Keeping answers current Re-index whenever the docs change Scheduled re-sync of imported pages, or Sync Now
When the AI doesn't know Build a fallback and a way to reach you Says so, offers a person, and alerts your team by email and push
A chat widget on each site Build, style and host it One script tag per site
Replying as a person Build an inbox or forward to email One inbox for every website
Adding another product Repeat the setup Add a workspace
Ongoing cost Your time, plus model and hosting costs From $9/mo per website
PRICING

What it costs for several products

Each website is billed at its plan price, with unlimited teammates and unlimited human conversations. Annual billing saves up to 20%.

Plan 1 website 3 websites AI conversations
Chat (you answer) $9/mo $27/mo 3 trial credits
Co-Pilot (AI drafts, you send) $19/mo $57/mo 100 a month per website
Auto-Pilot (AI answers) $49/mo $147/mo 500 a month per website

Use the websites selector on the pricing page to see your total.

FAQ

Frequently asked questions

Can I use one JIVIQ account for several websites?

Yes. Each website or domain is its own workspace, with its own chat widget, knowledge base and AI assistant. You sign in once and answer conversations from every website in one inbox, and each conversation stays tied to the product it came from.

Does each website get its own knowledge base?

Yes. Each workspace has its own knowledge base, so each assistant answers from that product's pages and files. You can import pages from a sitemap (up to 1,000 per job) or llms.txt, or upload PDF, DOCX, TXT, CSV or MD files up to 25 MB.

Can the AI behave differently on each product?

Yes. You set the AI mode per workspace: Autopilot (the AI answers), Copilot (the AI drafts and you send) or Off (your team answers). Each assistant also has its own name, branding and tone, and you can override the mode on any single conversation.

How is JIVIQ priced for multiple websites?

Each website is billed at its plan price: Chat $9, Co-Pilot $19 or Auto-Pilot $49 a month. Three websites on Co-Pilot cost $57 a month. Every plan includes unlimited teammates and unlimited human conversations, and the 14-day trial needs no card.

Will a customer who uses two of my products have one history?

Yes. Conversations from every workspace feed one shared customer record, so when someone writes in you can see what they asked before, whichever product they asked about.

Should I build my own support bot instead?

If you want full control and have time to maintain it, building is reasonable. Retrieval over your docs is the quick part. Checking answers against the docs, handing off to a person, a chat widget per site, an inbox and keeping content current take longer, and you repeat that work for each product. JIVIQ includes all of it.

Put an AI assistant on every product this week

The 14-day trial includes Auto-Pilot features and needs no credit card. Add a workspace for each website and answer everything from one inbox.

Start 14-Day Free Trial