The Infrastructure Layer for Conversations
Most organizations treat conversations as disposable — a message answered and forgotten. CII treats every conversation as a permanent, structured organizational asset: captured once, understood automatically, and available forever.
The core idea
Infrastructure, Not an App
CII is not a chatbot and not a CRM. A chatbot answers a single conversation and discards it. A CRM requires someone to manually type in what was discussed. CII sits underneath both: it captures the conversation exactly as it happened, structures it automatically, and keeps it queryable indefinitely — so any tool built on top, including a chatbot or a CRM, can draw on it.
- No forms — people communicate the way they already do, in chat
- No re-keying — structure is extracted, not manually entered
- No expiry — a conversation from a year ago is still queryable today
- No silos — one engine, shared across every domain-specific Pulse
In one sentence
CII is the layer that turns "what was said" into "what the organization knows" — automatically, continuously, and at the scale of everyday conversation.
Reference architecture
Seven Layers, One Engine
Every Pulse is an application built on the same seven-layer stack.
The lifecycle
From Conversation to Organizational Learning
Twelve stages, one continuous loop — explore each one below.
Conversation
A person messages naturally on WhatsApp, Telegram, or web chat — in their own words, with no forms to fill.
Common questions
FAQ
How is CII different from a chatbot?
A chatbot is a conversation interface. CII is what happens after the conversation: capturing it, structuring it, and making it a durable, searchable asset. A Pulse's chat experience can be built on any channel; CII is the infrastructure that makes every one of those conversations count afterward.
How is CII different from a CRM?
A CRM stores what a person chooses to type into a form, after the fact. CII extracts structure directly from the conversation itself, in real time, with no manual entry step — and keeps the original conversation alongside the structured record.
Do we need to build our own AI models?
No. CII uses OpenAI's models for understanding and extraction, combined with retrieval-augmented generation over your organization's own conversation history stored in Postgres/pgvector — so responses and structure are grounded in your data, not just general knowledge.
What happens to a conversation marked private?
Private conversations are captured and structured like any other, but are never surfaced outside the organization or Pulse that owns them — visibility (private, partners-only, public) is set explicitly, by the person or organization, at the point of conversation.
See CII Applied to Your Domain
Explore the Pulse ecosystem, or talk to us about building a new Pulse for your sector.