How It Works

RogerIQ turns support inputs into conversations, enriches them with customer and page context, searches knowledge, optionally drafts or sends AI replies, and keeps the support team in the inbox.

Flow

1

A customer reaches out

A conversation can start from inbound email, the widget, chat, a public form, Slack, Discord, Telegram, or the API.

2

RogerIQ resolves identity

RogerIQ links the message to a contact when email, secure widget identity, external ID, or existing conversation context is available.

3

Knowledge is searched

The platform searches published knowledge, crawled pages, synced docs, and relevant conversation memory.

4

The agent decides what to do

In Assist mode it suggests. In Copilot mode it drafts. In Autopilot mode it can reply automatically when confidence and guardrails allow it.

5

The team keeps control

Inbox status, assignment, tags, internal notes, saved replies, workflows, analytics, and webhooks keep the operational layer explicit.

Core Runtime Surfaces

SurfaceRuntime path
Dashboard apphttps://rogeriq.com/dashboard
API hosthttps://api.rogeriq.com
Public APIhttps://api.rogeriq.com/api/v1
Widget scripthttps://api.rogeriq.com/widget/v1/rogeriq.js
Widget APIhttps://api.rogeriq.com/api/widget/:projectId/widget/*
Hosted formhttps://rogeriq.com/forms/:formId
Short form routehttps://rogeriq.com/f/:slugOrId
Public docs sitehttps://rogeriq.com/docs/:siteSlug

AI Modes

ModeBehavior
AssistThe AI suggests answers and supporting context. A human writes the reply.
CopilotThe AI drafts replies for a human to review and send.
AutopilotThe AI can respond automatically when confidence, citations, and guardrails pass.

Most teams should start in Copilot. It gives real value immediately without hiding weak knowledge, missing guardrails, or unclear escalation rules.

Ask a question... ⌘I