Prostir

Illustrative example

An informational insurance assistant for WhatsApp and Telegram

This is an illustrative workflow, not a customer deployment. A Prostir agent can answer low-risk informational questions from approved agency documents and offer a documented route to a person. WhatsApp, Telegram, an optional CRM connector, and remote MCP each require the right account, connector, credentials, authentication, transport, and testing.

01

The safe job for this assistant

  • Answer office hours, contact, document-list, and general process questions from approved sources.
  • Show the source and say when the approved material does not contain an answer.
  • Send coverage, eligibility, pricing, claim, and advice questions to a documented human contact path.
02

Illustrative setup—not a live deployment

Each dependency must be available, authorized, configured, and tested before the channel is offered.

  1. 01
    Approve the information boundary.

    Choose low-risk questions and the exact documents or data the agent may use.

  2. 02
    Prepare an optional CRM connection.

    Use only a compatible connector or owner-approved tool with the required scopes and authentication; do not assume every CRM works.

  3. 03
    Configure one channel at a time.

    WhatsApp and Telegram require their own accounts, credentials, connector setup, transport, policy compliance, and end-to-end tests.

  4. 04
    Document the human contact path.

    Provide office hours, phone, form, or queue instructions. Do not call the handoff automatic until that exact integration is verified.

  5. 05
    Publish only after validation.

    The non-live URL pattern is https://{slug}.ai.prostir.build with https://{slug}.ai.prostir.build/mcp; the actual saved slug and access policy control the real endpoint.

03

What the illustrative configuration contains

These are proposed resources, not evidence of a customer deployment.

docapproved-faq.mdLow-risk answers approved by the agency.
docsource-register.mdOwner, version, and review date for every allowed source.
dochuman-contact-path.mdWhen and how the visitor contacts an authorized person.
datachannel-readiness.mdAccount, connector, authentication, transport, consent, and test status per channel.
04

Illustrative conversation

Constructed example—not a customer transcript or verified live call.

Prostir Studio

Which documents does the agency ask me to bring for an introductory appointment?

The approved appointment guide lists identification and the documents named on your invitation. I can show that checklist and the agency contact. I cannot decide coverage, eligibility, price, or a claim.

05

Boundaries before launch

  • Do not present general information as insurance advice or a coverage decision.
  • Do not promise reminders, automatic escalation, or complete logging until each exact dependency has passed an end-to-end test.
  • Keep a visible human contact route and review source changes before they reach the agent.
  • Treat channel availability and CRM access as configuration-dependent, not universal.

What gets published

Illustrative outcome, not a live customer result: after prerequisites and channel testing, the same approved-information agent may be exposed through WhatsApp, Telegram, and the non-live placeholder https://{slug}.ai.prostir.build with https://{slug}.ai.prostir.build/mcp. It gives sourced general information and a documented human contact path; it makes no insurance decision and promises no automatic handoff, reminder delivery, or complete conversation record.

Solutions

Multichannel AI agent with one controlled identity

Configure one published Agent with an explicit channel model, then connect only the channels whose credentials, policies, and customer identity rules you can support.

Solutions

Pick the channels that matter first

Tell us where customers ask, how they identify themselves, and what the Agent should handle. We will map supported channels and the setup each one requires.