AI support across chat, email, voice, Slack, and the IDE

Your knowledge.
Everywhere. Instantly.

AI that answers questions across your website, Slack, email, social channels, phone calls, and developer tools — grounded entirely in your own documentation.

pernoex.comBuilt on ClaudeUK-headquarteredGlobal
The problem

Your knowledge exists.
Your customers just can’t reach it.

~60%
of support tickets are repeat questions
2.5 hrs
per engineer per week on docs Q&A
~20%
of work time spent searching for information

The information exists. The problem is access. Pernoex closes the gap.

Who it hurts

Three audiences. The same broken loop.

Customers & users

Ask the same questions repeatedly. Wait hours for an email reply. Call a support line and hear hold music. Leave because they couldn’t find an answer.

Developers & partners

Dig through static docs pages. File GitHub issues for questions already answered in a README. Message your team on Slack at midnight waiting for a reply by morning.

Your own team

Search three different tools to find the right policy. Ask four colleagues where the onboarding doc lives. Get different answers each time.

The solution

Train once. Deploy everywhere.

Connect your existing knowledge — docs, PDFs, Confluence, Notion, GitHub, Google Docs — once. Pernoex syncs automatically when you update. Your AI is always current, always accurate, always citing its source.

1

Connect

Point Pernoex at your existing docs — Confluence, Notion, GitHub, PDFs, or your website.

2

Sync

Scheduled re-crawls keep knowledge current. Update a doc; the AI knows immediately.

3

Deploy

Activate any surface in minutes. One knowledge base powers all six simultaneously.

Six surfaces · One knowledge base

One platform. Wherever your users are.

Chat widget

Embedded on your site or product

Email

AI agent replies to support emails

Socials

X · Instagram

Slack

Community & internal workspaces

Voice

Real phone numbers · 60+ countries

MCP / IDE

VS Code · Cursor · Claude Code & more

Use cases

One platform. Four high-impact use cases.

Customer support

Head of CX · COO

Developer & API docs

Head of DevRel · CTO

Internal knowledge

COO · Head of People · IT

Sales & product-led growth

VP Sales · CPO · Head of Growth

Use case · Customer support
Head of CX · COO

Instant, cited answers — 24/7, in 50+ languages.

Deploy a chat widget on your site and a real phone number for voice calls. Customers get instant, cited answers 24/7. The AI resolves common queries end-to-end using Custom Actions to look up live data (order status, account details). When it can’t help, it hands off to your team via Intercom, Front, or any helpdesk — with the full conversation attached.

ChatVoiceCustom ActionsHuman handoff
Deflect 40–60% of L1 volume · Save $48K–$80K per avoided agent hire
Use case · Developer & API docs
Head of DevRel · CTO

Make your API documentation interactive.

Developers ask questions in natural language and get cited, accurate answers — inside their IDE via MCP, in your developer community Slack workspace, or on your docs site. The Slack bot auto-responds to community questions and tags the right team member when human help is needed. Content gap detection surfaces unanswered questions so you know what to document next.

MCP / IDECommunity Slack botChat widgetContent gap detection
Reduce developer time-to-first-integration · Free DevRel from repetitive FAQ
Why Pernoex

Others added AI to their product.
Pernoex was built as AI from day one.

Six reasons teams pick Pernoex over single-surface tools or bolted-on assistants.

Why Pernoex · 1 of 2

Reach, voice, trust.

REACH

Six surfaces, one knowledge base

Intercom lives in your support inbox. ReadMe lives in your docs. Pernoex lives everywhere your users are — chat, email, social, Slack, phone, and IDE — powered by a single knowledge base you only maintain once.

VOICE

Voice built in — 60+ countries

Real phone numbers in 60+ countries, including African markets. Your AI picks up the call, uses the same knowledge base as your chat widget, and transfers to a human when needed. Not a third-party add-on — native to the platform.

TRUST

Cited answers — no hallucinations

Every answer links to its source document. If Pernoex doesn’t know, it asks a clarifying question instead of guessing. For regulated industries — fintech, healthcare, legal — this is a compliance requirement, not a nice-to-have.

Why Pernoex · 2 of 2

Sync, dev, route.

SYNC

Syncs automatically — always current

Update a Confluence page and your AI knows immediately. Scheduled re-crawls mean you never manually re-upload content. Your knowledge base and your AI stay in perfect sync.

DEV

MCP: your docs inside the IDE

No other AI support tool puts your documentation natively inside VS Code, Cursor, Claude Code, and other AI coding tools. Developers stay in flow; you get fewer GitHub issues and Slack messages.

ROUTE

Smart Slack routing — not just Q&A

In developer community workspaces, Pernoex doesn’t just answer — it tags the right team member when escalation is needed, based on the type of question. Configured once, it works like a trained first-responder.

The business case

Better support. Fewer agents.
Lower operating costs.

Support agent$48K–$80Kfully loaded · per year
vs
Pernoex starts at$149per month

Conservative pitch: “avoid the next N hires as you grow” — same results, without touching existing headcount.

Where the savings come from

Four lines of cost. One platform replaces them.

Headcount & people

  • Avoid the next 1–5 agent hires as volume grows
  • No recruitment or onboarding cost ($8–15K/hire)
  • Management overhead eliminated for that team
Typical saving · 40–60% of L1 agent cost

Tooling consolidation

  • Fewer Intercom / Zendesk agent seat licences
  • Replace separate knowledge base tools (Guru, Notion AI)
  • Reduce translation & localisation spend (50+ languages native)
Typical saving · $1,200 per agent seat saved

Facilities & infrastructure

  • Office / contact centre floor space per seat
  • Hardware, IT licensing, security per employee
  • Telephony & IVR platform costs (voice replaces them)
Typical saving · $6K–$15K per seat per year

Engineering productivity

  • Engineers spend ~2.5h/wk on docs Q&A
  • At $120K/yr, that’s $8K per engineer annually
  • DevRel bandwidth returned to building, not answering FAQ
Typical saving · $60–$90/hr reclaimed
Pricing

Start free. Scale as you grow.

Starter

$149/month

Get started with AI support

  • 4M tokens included
  • 1 project · 1 seat · 1 domain
  • Chat widget
  • Basic analytics
  • Voice not included
  • MCP not included
Most popular

Growth

$399/month

Most popular for scaling teams

  • 20M tokens included
  • 3 projects · 3 seats · 5 domains
  • Chat widget + MCP integration
  • Slack (1 workspace / 3 channels)
  • Custom Actions (5 per project)
Voice add-on available (+$349–499)

Scale

$999/month

For high-volume, enterprise-ready teams

  • 60M tokens included
  • 10 projects · 10 seats · unlimited domains
  • Custom Slack bot (whitelabelled)
  • Conversation handoff to helpdesk
  • Activity audit log + RBAC
  • Server-side REST API + Webhooks
  • Whitelabel removal
Voice add-on available (+$1,049–1,499)

Voice · Standard from $499/mo (1,500 min · 1 number) · BYOC from $349/mo · Additional numbers available.

Plan comparison

Every feature, clearly mapped.

FeatureStarter $149/moGrowth $399/moScale $999/mo
Chat widget
Whitelabel removal
MCP / IDE integration
Slack integration1 workspace3 workspaces
Custom Slack bot (whitelabel)
Voice supportAdd-onAdd-on
Custom Actions5/project10/project
Conversation handoff
Scheduled re-crawls
Activity audit log
Analytics export (CSV)
Server-side REST API
Role-based access (RBAC)
Webhooks
Trusted by teams that move fast

Processing $22B+/month in transactions.
They chose Pernoex.

Africa’s leading payments infrastructure · $3B+ valuation · 34 countries

Pernoex powers Flutterwave’s developer support — giving 300,000+ merchant developers instant, cited answers to API and integration questions across chat, Slack, and IDE. Documentation questions that previously reached the DevRel team are now resolved in seconds.

Get started

Up and running in under 30 minutes.

1

Connect your knowledge

Point Pernoex at your docs, Confluence, Notion, GitHub, or PDFs. Or paste a URL. We handle the indexing.

2

Pick your surfaces

Activate chat, Slack, MCP, voice, email, or social — one at a time or all at once. Start with what matters most.

3

Go live

Embed a script tag. Share your phone number. Add the Slack bot. Your AI is live and answering questions the same day.

Your knowledge.
Everywhere it needs to be.

Book a 30-minute demo. We’ll show you Pernoex live on your own documentation — so you can see exactly what your customers, developers, and team would experience.

pernoex.comUK-headquarteredBuilt on ClaudeGlobal