RapiDesq Documentation

Everything you need to set up, configure, and get the most out of the RapiDesq contact center platform that carries the work through.

About these guides

These guides cover setup and configuration of RapiDesq — a contact center platform that starts at customer contact and carries the work through, unifying live chat, email, and web forms with an AI bot, smart routing, supervisor dashboards, file attachments, and multi-region data residency. If you're new to RapiDesq, start with About RapiDesq or the FAQ.

AI & Automation

AI Bot Configuration

Create and configure AI bots for customer support. Write instructions, scope to knowledge base collections, set topic restrictions and guardrails, define escalation conditions, and run multiple bots for different teams or use cases.

AI Agent Integration (MCP)

Connect an AI agent — Claude Code, your own agent, or an RPA bot — to read and act on tickets through a governed set of tools over MCP. Issue scoped, revocable agent tokens, configure workflow Definition-of-Done gates, and audit every action.

Ticket Automation Rules

Automate ticket work two ways: AI lanes, where an AI worker carries a ticket from one status toward another, and traditional rules that apply fixed actions on a trigger. Templates, conditions, budgets, a run log for every execution, and built-in loop safety.

Knowledge Base

Upload, organize, and maintain the content your AI bots and agents rely on. Collections, direct authoring, file upload, bulk import, API sync, scoping content to specific bots, and quality review workflows.

Conversation Flows

Master the visual flow builder: send messages, ask questions, collect structured data, run AI bot conversations, branch on conditions, check business hours, call external systems, analyze with AI, generate ticket descriptions, and route to teams.

AI Credits & Billing

How AI usage is metered in credits, included allotment per plan, one-month rollover of unused credits, top-up purchases, auto-refill with a monthly cap, depletion behavior, and the real-time usage dashboard.

Management

Team Management

Create teams with five user selection strategies and four ticket queue strategies. Configure custom ticket prefixes, capacity limits, user statuses with custom labels, permission sets, and business hour schedules.

Skill-Based Routing

Build a skill catalog by category, give each user their skills and a 1–5 proficiency, and write rules that decide which tickets require which skill. Mandatory requirements hold a ticket in the queue rather than handing it to someone unqualified.

Permissions & Access Control

Permission-based authorization model with built-in roles and custom permission sets. Grant fine-grained capabilities without changing roles, scope access by team, and follow least-privilege patterns.

Ticket Management

Manage tickets through a clear lifecycle with four priority levels. Configure custom fields, tags, and team-specific ID prefixes. Leverage AI sentiment analysis, key point extraction, urgency scoring, first response tracking, and internal notes.

Contact Management

Contacts auto-created from every source with email-based deduplication. Merge duplicates with full history transfer, add custom fields, verify identities with signed tokens, and view unified interaction history across all channels.

Custom Fields & Custom Data

Define custom fields on tickets and contacts — text, email, phone, dropdown, number, text area, checkbox, and file types with validation and conditional display rules. Populate from web forms, conversation flows, or manual entry.

Tags

A tenant-wide tag library for categorizing and filtering tickets. Create color-coded tags, track usage, merge duplicates, and apply tags manually or automatically from conversation flows.

Quick Replies

Canned responses users insert with a slash command or from the composer. Scope replies account-wide or to a specific team, and control the order they appear in.

Business Hours & Schedules

Create timezone-aware schedules with day-of-week time windows. Attach schedules to teams and use schedule condition steps in conversation flows for differentiated in-hours vs. after-hours experiences.