Knowledge·production

IAM.Bot

Embeddable AI consultant with RAG, qualification funnel and lead delivery.

Landing Application

Key capabilities

  • One-line widget installation for external websites
  • Tenant-scoped prompt and knowledge profile
  • Durable lead capture and Telegram/email delivery

Step-by-step guides

Use cases

Start with the outcome: open a guide, prepare prerequisites, follow the steps and verify the success signals.

01 Register a website and install the IAM.Bot widgetThe widget opens only on the allowed domain and uses the correct tenant profile.
Audience
Site owner or frontend developer
Outcome
The widget opens only on the allowed domain and uses the correct tenant profile.

Before you start

  • Access to site HTML
  • Public HTTPS domain
  • IAM.Bot account

Steps

  1. Create a workspaceIn the console, add organization, assistant name and owner contact.
  2. Add the domainEnter the exact origin without a path and complete the ownership check.
  3. Copy the embed codeUse the issued data-slug/credential; the acme-corp landing example is not your key.
  4. Verify the production pageOpen the site in a private window, send a test question and verify session origin.
Verify the result

widget.js returns 200, chat creates a session in the intended workspace and foreign origins are rejected.

If it does not work

In-widget onboarding indicates invalid credentials, slug or an unverified origin.

02 Configure lead qualification and Telegram/email deliveryA qualified lead is persisted before delivery and reaches both configured channels.
Audience
Marketing or sales operations
Outcome
A qualified lead is persisted before delivery and reaches both configured channels.

Before you start

  • Lead fields
  • Telegram chat binding
  • Verified recipient email

Steps

  1. Configure qualificationSet required fields, consent text, MQL criteria and operator fallback.
  2. Connect channelsBind Telegram with a one-time code and verify email.
  3. Run a test conversationTest the happy path, consent refusal and incomplete contacts.
  4. Check the delivery ledgerConfirm lead saved precedes queued/sent and retries do not create duplicates.
Verify the result

One lead id appears in Conversations and is delivered to Telegram/email without duplicates.

If it does not work

On channel failure, check retry state and dead-letter; do not re-enter the lead manually.

Application sections

Open detailed manual

Every application screen has a separate page with controls, safe example values, CLI/API alternatives and status-specific recovery steps.

Open detailed manual →

Role in the ecosystem

IAM.Bot adds a dialog entry point to the site: responds according to allowed materials, clarifies the need and turns the conversation into a lead. Bot profile defines domains, prompt, knowledge scope, delivery channels and escalation rules.

Connecting a widget

<script src="https://cdn.iambot.ru/widget.js" data-slug="your-company" async></script>

The CDN script is loaded asynchronously. The origin of the page must be included in the allowlist profile. If slug or credentials are not yet configured, the widget runs a secure onboarding instead of a silent error.

Dialogue and lead

The bot first solves the question from the knowledge profile, then collects only the necessary ones contact details and consent to communication. The lead is fixed durable before being sent to Telegram and email. A failure on one delivery channel should not destroy the record; replay is performed idempotently.

Reliability inference

The model layer uses retry with bounded backoff and fallback between configured providers. Switching does not change the tenant scope and does not duplicates user message. If the AI ​​widget is completely unavailable, everything equally accepts the contact and reports subsequent communication.

Safety

The public client does not contain provider keys. CORS/origin policy, rate limiting, HTML sanitization and delivery auditing are checked separately for each tenant.