For teams asked the same question a hundred times a day

Your docs, talking back.

IntelloWork reads the content you already wrote — Solr indexes, websites, files, APIs — and answers your team and your customers in seconds, with the citation, on web, WhatsApp, Slack, and Teams. Same brain, every channel.

Works onWeb widgetWhatsAppSlackMicrosoft Teams

0.0s

median answer latency

0.0M+

documents indexed

0.0%

retrieval-plane uptime

Live · Web + WhatsApp
Cited · 4 sources
intellowork.com/lab

In /admin/auth-providers, add an IdP and map your group attribute to a role. IntelloWork enforces the mapping on every login.

SSO setup guide·§2.1Roles & permissions·§4IdP onboarding·step 3
Ask anything…Send
The whole platform

Start from what you want to change.

Pick the outcome you care about and see only the parts that get you there. Nothing here is on a roadmap — it is what the platform does today.

Agentic

Action agents

It does the thing, instead of telling someone else to.

Looks up the order, raises the ticket, books the slot — in one reply.

Outbound

Campaigns

Start the conversation, don't just land in an inbox.

Send to a segment on WhatsApp, then let the assistant handle every reply.

Commerce

Transact in chat

Browse, choose and order without leaving the thread.

Your catalog, synced and shoppable on the channels people already use.

Omnichannel

One brain, every channel

Web, WhatsApp, Instagram, Slack, Teams and voice — one set of answers.

Configure once. Change a source and every channel changes with it.

Private

Your private GPT

The assistant your team wants, on the data you can't send outside.

Answers from your material, cited — and never used to train a public model.

Swipe for more →

21 capabilities, in production today.

It already knows your business on day one

Knowledge sources

Point it at websites, uploaded documents, a Solr index or your own API. Re-crawls on a schedule, so answers don't drift from the source.

Every answer can be checked, so people trust it

Cited answers

Responses are grounded in retrieved passages and cite the document and section they came from — not a confident paraphrase of nothing.

Live on your site in an afternoon

Web chat widget

One script tag. Styled to your brand in Widget Studio, with a welcome card that puts your primary call to action in front of every visitor.

Meet customers where they already message you

WhatsApp, Instagram and Messenger

The same brain answers on every channel. Route by phone number or page, and keep one set of sources behind all of them.

Staff stop interrupting each other for answers

Slack and Teams

The internal assistant reads the internal material, so HR policy and runbook questions resolve in the channel they were asked in.

Callers get answered without a queue

Voice

Speech in, speech out, over the same pipeline as chat — so the phone line and the website never disagree.

Nobody hits a dead end

Live agent handoff

When the bot is out of depth it hands the conversation to a human with the full transcript attached, so the customer never repeats themselves.

Interest becomes a named contact in your CRM

Lead capture forms

A short form inside the chat captures name, email, phone and intent, writes it straight to your CRM, and carries the conversation summary with it.

Fewer drop-offs between interest and a call

Book a meeting in chat

The calendar opens inside the conversation. No redirect to a booking page, no second tab, no lost visitor.

Reach a segment without exporting a list

WhatsApp campaigns

Send an approved template to an audience, then let the assistant handle every reply — so a campaign starts a conversation instead of ending in an inbox.

People can browse and buy inside the chat

Product catalog

Sync products from your own API, push them to a Meta catalog, and let the assistant show, recommend and take the order.

It can act, not just answer

Connections and skills

Give it a REST, SQL, SAP or MCP connection and it checks an order, raises a ticket or files a request — with the arguments validated before the call.

One platform, a different assistant per audience

Pipelines and prompt profiles

Compose sources, model, prompt and guardrails into a named configuration, and run several side by side without them bleeding into each other.

It stays on topic, in your words

Guardrail policies

Define what it must never claim and how it declines. Applied on the live path, not just in testing.

Confidential content stays confidential

Permission-aware retrieval

Source permissions travel into the index, so a reader cannot retrieve a restricted page — even by asking for it precisely.

Customer-specific answers, safely

Sign-in and roles

Gate a skill behind sign-in and connect your own identity provider — Google, Azure AD, Okta or generic OIDC — with groups mapped to roles.

ChatGPT that only knows your business

Your private GPT

The same ask-anything experience your team already expects, answering from your material instead of the open internet — and your content is never used to train anyone's model.

It finishes the job, not just the sentence

Multi-step agents

Chain several calls into one request — look the customer up, check stock, raise the ticket, confirm back — with each step validated before it runs.

No more "which system is right?"

Every source, one answer

Website, documents, a Solr index, a database and your own APIs answer as one assistant, so staff and customers stop getting two different versions of the truth.

You can see what people actually ask

Analytics and transcripts

Every conversation is searchable and every configuration change is logged, so you learn what to write next and can prove what happened.

Change it with confidence

Playground and testing

Try a prompt, a source or a skill against real questions before it reaches a customer, and compare against the version running today.

Why IntelloWork

Made for the people who own the answer.

You bring the content. We handle the chunking, embeddings, retrieval policy, citations, and the seven other things that decide whether your bot is trustworthy.

Citations, not hallucinations

Every answer is grounded in retrieved chunks. We cite the source document, the section, and the paragraph — never an opaque hand-wave.

ACLs that survive retrieval

Source-level groups travel into the index, so a guest never sees a confidential page even if their question phrases it perfectly.

Every channel, one answer

Web widget, WhatsApp, Slack, Teams — same brain, same sources, same answer. Configure once; route by phone number, channel, or pipeline.

Live demo

Click a question. Watch your bot answer.

Three real IntelloWork conversations — answers grounded in the source documents, every claim cited. No setup required, no fake content. This is what your users will see.

intellowork.com/your-workspace
 
Demo answers are scripted. Your live bot streams from your indexed sources.Try with your own content
How it works

Three planes. One workspace. Zero glue code.

IntelloWork separates content, retrieval, and surface so each can evolve independently. The dashboard shows you exactly which plane is healthy at any given moment.

01 · Content plane

Connect your content

confidencecitationsrerank

01 · Content plane

Connect your content

Solr indexes, generic JSON APIs, websites, file uploads. Each connector self-describes; we sample your schema, suggest field maps, and warn you about the fields that look like ACLs.

  • Auto-detect content type, title, URL, body fields
  • Field-level no-summary rules for compliance docs
  • Per-source ACL on `groupname_ss` (or your equivalent)

02 · Retrieval plane

Compose retrieval pipelines

confidencecitationsrerank

02 · Retrieval plane

Compose retrieval pipelines

Vector + keyword hybrid by default. Tune top-k, rerank, and confidence thresholds in the Configurations editor — or use the workspace defaults that ship from day one.

  • Vector + lexical hybrid out of the box
  • Confidence-aware: low-confidence answers carry a disclaimer
  • Named prompts let you reuse a prompt across pipelines

03 · Surface plane

Ship to every channel

confidencecitationsrerank

03 · Surface plane

Ship to every channel

One pipeline powers a website widget, a WhatsApp number, a Slack workspace — all from the same retrieval policy. Per-channel branding, per-channel feature flags.

  • Embed snippet for any website, mobile-ready
  • WhatsApp Cloud API with signed-webhook delivery
  • Audit log on every conversation, every channel
Who IntelloWork is for

Three teams. One platform. Same governance.

IntelloWork lands fastest where there's already a lot of content and a lot of repeated questions. If that's your team, it'll feel obvious in week one.

Customer Support

Teams running Zendesk, Intercom, or in-house ticketing.

  • Self-serve refunds & cancellations
  • Deflect L1 tickets with citations
  • WhatsApp + web widget, same answers

Cuts ticket volume 40-60% on common queries.

Product Documentation

Doc teams maintaining a public knowledge base or developer hub.

  • Conversational doc search
  • Cite the section, not just the page
  • Embed on every docs page in 5 minutes

Search-to-answer in under 3 seconds, with sources.

Internal Helpdesk

IT, HR, and ops teams handling employee questions.

  • Slack / Teams native answers
  • Role-aware replies (IT sees IT)
  • ACL-respecting; HR docs stay HR-only

L1 questions resolved before they hit a person.

Channels

One pipeline. Every channel your users live in.

Configure retrieval once. Route messages by channel, phone number, or workspace. Each surface gets the same governance — ACLs, audit log, citation policy — so a bot in one place can't leak content from another.

Web Widget

Live

Embed-script chat for any site. White-label branding, ACLs, citation chips.

WhatsApp

Live

Meta Cloud API. Verified webhooks, voice-note transcription, multi-number routing.

Slack

Beta

Bot user with thread-aware replies. ACL-respecting; honors workspace roles.

Microsoft Teams

Coming soon

Native Teams app with adaptive cards. SSO via the existing tenant IdP.

Voice

Beta

Speech-in / speech-out for the widget. Whisper transcription, low-latency streaming.

API

Live

Direct chat API for custom surfaces — mobile apps, in-product help, agents.

Built for enterprise

The boring safety stuff, done right.

We'd rather your security team approve us in week one than have you discover the compliance gap in week six. Here's what's already in the box.

SOC 2-aligned

Tenant isolation, encryption at rest + in transit, change management.

GDPR-ready

Data residency, right-to-erasure, retention policy, DPA on request.

Bring your own LLM

OpenAI, Bedrock, Anthropic, or self-hosted Whisper. Your keys, your providers.

Source-level ACLs

Document permissions travel into the index. Guests can't read staff content.

Audit log on every action

Every config change, every reset, every conversation. Queryable, exportable.

SSO & RBAC

Keycloak, Google, Azure AD, Okta, generic OIDC. Group-to-role mapping built-in.

FAQ

Questions buyers actually ask.

We left out the marketing-y ones. If something below isn't covered, email us — we'll answer same day during business hours.

How is pricing structured?
Per-workspace, with usage-based add-ons for high-volume tenants. We invoice monthly. Custom enterprise contracts available — talk to us about volume + multi-year terms.
Where does my data live? Who can read it?
Your indexed content stays in the workspace you control. Embeddings live in your tenant's vector partition. IntelloWork staff never read tenant content; the only access path is admin tooling that's audit-logged. Data residency: ap-south-1 by default; EU/US options on request.
What's the answer latency in production?
Median is 2.1–2.8s end-to-end (retrieval + LLM). 95th percentile under 5s. The chat is streamed, so the first token typically lands in 800ms — the bot feels live before the full answer arrives.
Can I use my own LLM provider?
Yes. OpenAI, Anthropic, AWS Bedrock, Azure OpenAI, or self-hosted models that speak the OpenAI API. Bring your own keys; we never see them after configuration. You can mix providers per pipeline.
How many channels can a single bot serve?
Unlimited on enterprise. Starter and team plans cap at 2 and 5 channels respectively. A 'channel' is one Web widget, one WhatsApp number, one Slack workspace, etc. Same pipeline can answer across all of them.
What happens if the bot gets a question wrong?
/conversations surfaces every Q&A with citations and confidence. The 'Debug in Lab' link replays the failing query with full retrieval trace so you can see whether retrieval, the prompt, or the model misfired. Most fixes are content-side: better mappings, a missing source, an out-of-date doc.

Let your docs do the talking.

Access is invite-only while we onboard customers carefully. Tell us about your use case and we'll get you into a workspace within a day.