Frequently asked questions about live chat plugin implementation
These are the practical questions teams ask before switching from a basic widget to a hybrid AI chat operation.
How quickly can I install this live chat plugin?
Most teams can complete initial deployment in a single working session. Setup includes account creation, initial workflow design, embedding the script, and reviewing your first routing outcomes.
Does the plugin support RAG instead of generic chatbot replies?
Yes. RAG capability allows responses to draw from your approved content context so answers stay aligned with your products, support policies, and service boundaries.
Can I route conversations into different departments?
Yes. You can design routing rules based on intent, urgency, topic, and availability so sales, support, and specialist teams receive relevant chats without queue confusion.
What happens when AI is not confident in the answer?
You can define fallback thresholds that transfer to human operators with full conversation history. This protects experience quality and avoids unhelpful or repetitive replies.
Can this plugin work for both lead generation and support?
Yes. Workflows can branch by visitor intent so discovery and qualification paths serve commercial conversations while separate flows resolve account and support needs.
Do you support migration from another chat plugin?
Yes. A staged migration approach lets you mirror key flows, run side-by-side checks, validate department performance, and switch over with low risk.
Are pricing options available for different team sizes?
Yes. Solo, Business, and Bespoke options are available. Plan selection depends on volume, operational complexity, and workflow sophistication.
Where can I learn more about the core platform?
You can visit IMSupporting to review platform information, implementation context, and current product updates.