Skip to main content
Explanation

WebChat Channel Constraints and Multi-Queue Architecture

Table of Contents​

1. Overview​

The WebChat element is UltraCart's real-time chat widget, embedded in your storefront for customer interactions. It operates within specific placement and queue constraints that affect how you can deploy AI Agents across different areas of your storefront.

This document explains those constraints and describes how to architect multi-context support using UltraCart's available communication channels.

2. WebChat Element Placement​

The WebChat element renders in the storefront footer only. This is a platform constraint, not a configuration option.

Consequences of this constraint:

  • Only one WebChat widget instance exists per storefront.

  • The widget cannot be embedded in specific pages (such as the My Account portal), custom sections, or non-footer locations.

  • You cannot create independent WebChat instances for different areas of your storefront.

If you need chat-like support in a specific page context (such as My Account), the available alternatives are the Tickets channel or a link to the WebChat widget.

3. Queue Assignment​

The WebChat element routes to a single queue. This means:

  • All conversations initiated through the WebChat widget enter the same queue.

  • You cannot split WebChat traffic between two queues based on the page the customer is viewing.

  • Only one AI Agent configuration (personality, instructions, capabilities) governs the WebChat channel at a time, though multiple AI Agent users can be assigned to the same queue for workload distribution.

Note: Multiple AI Agents assigned to the same queue share the queue's conversation load via round-robin distribution. They do not operate as separate, independently routed agents within WebChat.

4. Multi-Channel Queue Architecture​

Multiple queues with independent AI Agent configurations are only achievable by deploying multiple communication channels. Each channel can have its own AI Agent, instruction set, and queue.

ChannelEntry PointSupports Separate Queue?
WebChatStorefront footer widget (one instance)No -- single queue only
SMSCustomer-initiated text to your numberYes
VoiceInbound phone callsYes
TicketsEmail, UltraCart Task, or Zoho DeskYes

To assign different AI Agents with different instruction sets to different customer entry points, configure a separate channel for each context.

5. Workarounds for Multi-Context Support​

Option A: Single WebChat queue with context-aware agent instructions​

If your primary goal is to give storefront customers a different AI experience than My Account customers, configure one AI Agent with Chat Instructions that adapt based on conversational context. When a logged-in customer's session is established, the agent has access to their order history, subscription data, and past conversations -- which can inform how it responds without requiring a separate queue.

This approach works well when the behavioral difference between contexts is primarily about tone or content rather than queue routing or escalation paths.

Option B: WebChat for storefront + Tickets for My Account​

Set up a separate AI Agent assigned to the Tickets channel with instructions tailored to account-level inquiries. In the My Account portal, surface a prompt or link that directs customers to open a support ticket. The Tickets-channel AI Agent picks up those submissions with its own personality, instructions, and capabilities.

This provides:

  • Independent AI Agent configurations per context

  • Separate queue routing

  • Independent instruction sets and capability scopes

The trade-off is that My Account users interact via an asynchronous ticket rather than real-time chat.

Option C: Multi-channel deployment​

Deploy WebChat, SMS, or Voice in combination to serve different customer segments. Each channel supports its own AI Agent and queue, enabling differentiated support experiences.

6. Troubleshooting​

Merchant wants two WebChat chat windows on one storefront​

Symptoms: Merchant wants one WebChat widget on the main storefront and a second in the My Account portal, each with its own AI Agent.

Root Cause: The WebChat element is a single footer-embedded widget. The platform does not support multiple WebChat instances or page-scoped WebChat placement.

Solution: Use the Tickets channel or a secondary communication channel (SMS, Voice) to serve the My Account context with a separately configured AI Agent. See Option B above.

Merchant wants separate AI Agents with different capabilities per storefront area​

Symptoms: Merchant wants AI Agent A to handle general storefront questions and AI Agent B to handle account management, each with a different capability set.

Root Cause: Capabilities in UltraCart are configured globally under Workforce > Settings > AI Capabilities and apply to all AI Agents on the account. You cannot grant different capability scopes to different agents.

Solution: Use per-channel instruction sets to constrain what each agent discusses, even if capabilities are shared. Alternatively, evaluate whether the use case can be served by a single well-instructed agent.

Was this page helpful?