For business
Knowledge infrastructure for your customers.
Your company has knowledge. Your customers have questions. Billuminate builds the bridge.
Positioning
The knowledge layer, and the agents that run on it.
Your support pages, FAQ and chat answer a subset of your customers' questions. The rest end up with your service desk, in Google, with the AI companies, or stay unanswered. Billuminate builds the knowledge layer your channels can lean on: your customer's own case when your systems are connected, your own content, structured, kept current, answering for you and nobody else, and the shared verified layer for everything around it that no single company publishes. In that order, every time.
We build the widget too, but the widget is not what makes the difference. We are the verified source of truth that a widget, a REST API, a voice assistant or your own customer-service system can pull answers from.
What you get
Four surfaces, one knowledge layer
Today
The agent, in your own branding
A chat on your own site that speaks as you, answers from your content and the verified layer, and shows the source next to the answer. Fifty languages from the same source.
- Chat on your site
- Your tone, your limits
- A source on every answer
Today
The portal, and the gap loop
Your team sees what was asked, in which language, and above all what we could not answer, every gap ranked by how often customers hit it. Closing one is a paragraph of work, not a project: add the missing answer, it goes through the same verify-and-index path as everything else, and starts answering. No release cycle, no ticket queue.
- Unanswered questions
- Ranked by frequency
- Closed with a paragraph
Coming
MCP
Other AI assistants will reach your verified knowledge directly, under the same answer order and the same limits as the chat. The protocol layer is thin because it calls the same pipeline; the work sits in per-organisation keys and access control.
- MCP access
- Same answer order
- Same limits
Coming
Email and voice
The same knowledge layer in outbound communication. Anyone can send a message. Handling the reply is the hard part, and it only works when the message and the answer come from the same source.
- Voice, in and out
- Human approval before sending
Answer order
Which source wins, every time
Three tiers are served and three are refused. The order is the same for every question, and it is agreed with you. Any tier you do not want is switched off.
Your content and the shared layer are indexed separately, per company. Another company's chat cannot retrieve your content.
- 1
This customer's own case
A document they shared, or your own systems
Primary
- 2
Your own content
Your site, your documents, what you gave us
Primary
- 3
The shared verified layer
Our verified articles first, authority sources after
Fallback
- 4
Another company's private content
Never shared
- 5
Unverified or expired content
Never served
- 6
The open internet
Never served
If none of the first three carries the answer, the agent says so. It does not fall through to the ones below.
Architecture
How it works
Three layers that turn your published knowledge into answers your customers actually get.
01 · You contribute
- Website
- Terms
- Product sheets
- Internal knowledge
02 · The knowledge layer
- Indexing
- Verification
- Structuring
- Sourcing
03 · Your channels
- Chat
- Portal
- MCP, email and voice, coming
- 01
You contribute the primary sources
The same two tiers the answer order calls primary. Your own content first: website, terms, product sheets, the internal knowledge you want customers to reach. Then your customer's own case, when you connect the systems that hold it. Billuminate indexes, verifies and structures both, and you see all of it in the portal.
- 02
Bill answers
your customers. In a widget on your own site, through the REST API, or embedded in your own interfaces. Always with a source.
- 03
You get insight
into which questions your customers actually ask, which answers are given, and where the knowledge comes from. Insights that are otherwise locked in customer service logs.
Admin portal
What the insight looks like
Admin portal
Demo, overview
Questions
1,284
+18%
Sourced answers
98%
+2 pp
Active languages
17
Most asked questions
CountHow long is the lock-in period on your mortgage?
Terms page42Can I repay early without a fee?
Published FAQ31What happens if I miss a payment?
Terms page28How do I transfer my savings account?
Help center22What interest applies after the lock-in?
Terms page18Sample view. Most asked questions, percentage of sourced answers, active languages. Each question links to full history and the source document.
Onboarding
Your company is probably already on Billuminate.
Our knowledge base already covers content from close to a hundred Swedish companies across banking, credit, debt collection and credit bureaus. Because we start from what is already public, a working instance of your knowledge exists before you have integrated anything or opened a ticket with IT.
01
See what we have
Get in touch, we'll show you what Billuminate's knowledge layer currently contains about your company. No commitment required to take a look.
02
Make it yours
Upload internal documentation, correct where we missed, connect customer-specific data if you want. You always have the final say over what is published to your customers.
03
Live in production
Widget on your own site, REST API, or embedded in your environment. What sets the pace is when you open your site to our crawler, not the length of our queue.
Integration
Built for integration
REST APIwith full documentationWidgetto embed on your site or in your appAdmin portalwith visibility into all data Billuminate holds about your companyWebhooksfor event-driven integration with your systemsSSOand role-based access to the admin portal
Business value
What Billuminate does for your business
Reduces operating cost
on your support organization as more questions get answered without scaling up your service team.
Reduces customer loss
by giving your customers answers when they need them, not after three hours in queue or an unread letter.
Raises customer satisfaction
through clarity and consistent answers regardless of channel.
Opens new customer segments
that have been hard to reach, for example customers who don't have Swedish as their first language.
Pricing
One fixed fee. No surprises.
You pay a fixed monthly fee based on the size of your organisation and which surfaces you use. Unlimited answers. All languages included.
The price is set before the agreement is signed and is not affected by how much your customers use the service. Heavy use is the goal, not a cost.
Start with a fixed-price pilot on clear measurement points. The pilot fee is credited against your first annual agreement.
Compliance
Built for a regulated industry
GDPRcompliance, data stored within the EUrobots.txtcompliance perRFC 9309- Takedown SLA: 48 hours for logos, 7 days for content, no negotiation
- Architecture prepared for
ISO 27001certification (not certified today) - Transparent source handling, you see exactly what we use about your company
FAQ
Common questions
- How long does it take to get started?
- Because we start from what is already public, a working instance of your knowledge exists before you have integrated anything. What sets the pace after that is when you open your site to our crawler, not the length of our queue.
- How do you handle sensitive information?
- We index only public data by default. Sensitive content, such as customer-specific data, is handled separately and under your control. You always decide what is used to generate answers.
- Can we try before deciding?
- Yes. A demo with your own data is included. You see exactly what knowledge Billuminate holds about your company and how answers look before signing any agreement.
- What happens if Bill doesn't have the answer?
- Bill doesn't answer when we don't have coverage. The user sees a clear 'we don't have the answer' instead of a guess. You see the unanswered questions in the admin portal, so you can fill the gaps over time.
- How do you handle AI hallucinations?
- Every answer is built on reviewed source material, not on training data. We prioritize 'don't answer' over 'guess wrong'. The answer always shows its source, so both you and the customer can verify. Without a reliable source, no answer.
- Does the customer see the sources?
- Yes, always. Every answer Bill gives has one or more source citations visible to the user. You see the same sources plus full history in the admin portal.
- How does multilingual support work?
- Bill supports 50 languages today. Your customers get answers in the language they ask in. The underlying knowledge layer is the same, so quality and sources don't change by language.
- SwedishEnglishArabicSpanishBosnianThaiSerbianCroatianPolishFrenchTurkishSomaliUkrainianPersianTigrinyaKurdishSoraniPashtoAmharicUrduBengaliNorwegianFinnishDanishIcelandicChineseVietnamesePortugueseGermanJapaneseDutchIndonesianItalianHindiGreekKoreanTamilRomanianHungarianAlbanianRussianTagalogLithuanianEstonianBulgarianMongolianCzechZuluGeorgianSlovak
- How fast are the answers?
- Under a second for cached answers, 2-4 seconds for new ones. Caching is based on content, not per company, so your customers get faster answers as the knowledge layer grows.
