|
HELPDESK INTEGRATIONS
Our AI Shopping Assistant connects to your helpdesk.
When a shopper escalates from your AI assistant to a human agent, the context doesn’t travel with them. Your agent opens a blank ticket. The shopper starts over.
Ticket data and conversation context now flow in from Gorgias and Zendesk. The assistant has the full picture before it speaks.
|
|
|
Q&A GROUNDING
Every answer now cites its source
The agent points back to the exact line in the product copy that backs up the response. If it can’t find a source, it doesn’t answer. Display count is configurable from 1 to 10 questions per page. A compact PDP widget runs 1. A full Q&A panel runs all 10.
|
|
|
GORGIAS INTEGRATION LIVE
Helpdesk-to-Assistant, end to end
Merchants on Gorgias connect their helpdesk directly to AI Shopping Assistant workflows. Support tickets and customer records sync in automatically. First helpdesk integration beyond Freshdesk and Zendesk.
|
|
|
ZENDESK DEPTH
Smarter ticket context
Deeper ticket data and richer node behavior. Support replies land with more of the right history attached.
|
|
|
SEARCH TUNING
Per-merchant boost knobs
New category and product-type boost controls in the DSL builder. Search relevance tuned to each catalog, not a generalized model.
|
|
|
LIVE STATUS
“Working on it” visible to shoppers
Shoppers see assistant activity as it happens. “Searching products” or “checking inventory” instead of a blank screen. Refreshes every second. Slow steps feel responsive.
|
|
SEARCH RESILIENCE
Query understanding fails over cleanly
Query understanding now fails over to a secondary AI provider. A Gemini outage no longer surfaces an empty results page. Per-merchant intent overrides also ship in this release. As an example, “puppy” routes to small-breed filters for a pet retailer.
|
CATALOG ENRICHMENT
Resumable runs, per-storefront vocabularies
Large enrichment runs resume from where they left off instead of restarting at product zero. Per-storefront vocabularies are now live. “Tee” in a fashion catalog is not the same lookup as “tee” in home goods.
|
|
| |
AGENTIC COMMERCE
~8 min read
Agentic Commerce OS for engineers.
What changes, what doesn’t.
Adrian Luna · May 19, 2026
The first question engineering teams ask when evaluating Agentic Commerce OS is what breaks. The answer: your application architecture stays identical. The delivery layer in front of it changes. Adrian maps the full handoff, what your team owns and what Webscale owns, the 2ms to 8ms added to the request path, and exactly what acting on personalization signals requires from your codebase.
Read the post →
|
|
|
QUICK REFERENCE
Your agent health review. Prompt-tuning edition.
| ✓ Set brand voice instructions across all active agents |
| ✓ Add domain terminology blocks for any specialized product categories |
| ✓ Update business rule blocks with current promotions and policies |
| ✓ Check Gorgias or Zendesk routing if either helpdesk is live on your storefront |
| ✓ Review per-merchant search boost settings against current catalog priorities |
| ✓ Confirm live status messages are rendering correctly in your storefront environment |
Do this before the sprint closes, not after a merchant files a support ticket.
|
|
Track what ships.Follow infrastructure updates, deployment tooling improvements, and release notes as they go live. | |
|
|
|
Webscale Networks, 35111F Newark Blvd, Unit #2025, Newark, CA 94560, United States
|
|
