How it works
To connect Telegram and ruSender, you don't need a developer: a ready-made scenario links them in minutes.
- Starts when: Webhook Trigger (Live Chat)
- Then: Workflow Configuration
- Then: Normalize Payload
- Then: Conversation History Manager
- Check: New vs Existing Conversation
- If yes: Preprocess Query
- Then: RAG Support Agent
- Then: Sentiment Analysis
- Then: Confidence Scoring
- Check: Check Confidence Threshold
- If yes: Check Sentiment
- If yes: Check Message Scope
- If yes: Human Takeover Detection
- If yes: Channel Router
- If yes: Format Email Response
- Then: Send Email Reply
- Then: Auto-Categorization
- Then: Log Conversation to Sheets
- Then: Log Conversation to Zendesk
- If no: Format Webhook Response
- If no: Format WhatsApp Response
- If no: Format Discord Response
- If no: Format Slack Response
- If no: Escalation Needed?
- If yes: Escalation Reasoning
- Then: Prepare Ticket Object
- Check: Business Hours Check
- If yes: Create Zendesk Ticket
- Then: Escalation Alert to Support Team
- If no: Update Zendesk Ticket
- If no: Fetch Conversation History
- Check: Merge History with Query
- Then: Email Trigger (IMAP)
- Starts when: WhatsApp Trigger
- Starts when: Slack Trigger (Mentions)
- Starts when: Discord Webhook Trigger
- Then: OpenAI Chat Model (RAG)
- Then: OpenAI Chat Model (Sentiment)
- Then: OpenAI Chat Model (Escalation)
- Starts when: Weekly Maintenance Schedule
- Then: Fetch Weekly Metrics
- Then: Supabase Vector Insert
- Then: Send Weekly Summary
- Then: Prepare Metrics for Vector Insert
- Then: OpenAI Embeddings (Insert)
- Then: Chat Memory
- Then: Document Loader
- Then: Text Splitter
You can launch this Telegram + ruSender integration in Scriptera: describe the task in plain words — the scenario is built, launched and monitored for you.