E-commerce
August 19, 2026
“Alby Review: AI Customer Experience Agent for Retail” (address /apps/alby/) describes a single agent deployed on product pages, search, and support channels, which responds with a merchandising context rather than generic chatbot replies. Trained on the catalog, reviews, and brand voice, to align with how customers truly evaluate products. Buyer: retail and direct-to-consumer, high-consideration products, pre-purchase friction, repetitive tickets to deflect without passing the conversation to a separate helpdesk. Display tagline: “The Customer Experience Agent for Retail”. Index tagline (schema): a single agent on product pages, search, and support, responding with merchandising context. No "from $" badge. No Offer schema. Schema.org SoftwareApplication: name alby, url to seller homepage (not cited). No "get it". No "look elsewhere". No "used by". No reviews. No GDPR. No $ grid. No alternatives. No comparable listings. What it does: pre-purchase questions on the product page; unifying sales assistance and post-purchase support in one agent; training on catalog, reviews, policies; sending intent signals to merchandising teams; deflecting repetitive tickets without separate helpdesk routing. Index sentence: collapses pre-purchase assistance and post-purchase support into one agent instead of separate PDP widget and helpdesk bot. Placing Alby into an "AI shopping agent" indicator means budgeting UCP. It is an on-site merchant CX agent. A widget that answers a sizing question does not open a delegated payment funnel.
The App Store listing (alby: AI Agent & Chatbot, developer alby by Bluecore) currently states that the application is not currently available, and to write to Bluecore support. No pricing grid. No "Free to install" held here. The "Free" cards around it are other applications. The help article "Assisted conversion pricing" (modified on July 14, 2025, thread Launch on Shopify) publishes a performance-based model: 100 assisted conversions for $1 / month, then $1 each, monthly cap, widget turned off until the 1st of the month, enterprise on a custom plan. Assisted conversion: recommendation or answer about a product, purchase of that product within 30 days, counted by SKU. Tracking: catalog, JavaScript snippet, Purchase Pixel. Not UCP. Not ACP. Not Magic. The "deploys" listing is not an App Store installation. The $1 is not an Offer 0. We do not detail the pixel.
If the concept of a software buyer is new: what agentic commerce is. The 2026 calendar: what was delivered. Shopping surfaces: AI shopping agents. Official totals remain human funnels: 2026 e-commerce statistics.
Summary
A showcase CX agent, zero agent payment funnels
Alby, according to the publisher, is a retail customer experience agent (product questions, recommendations, order support). The directory lists it as a Customer Experience Agent. It is not a buyer agent on the consumer side. It is not ChatGPT shopping. A buyer asks about a size. A model answers. A purchasing LLM compares a price. Two different jobs. One word: agent.
Layer | Directory Listing | App Store + Help |
|---|---|---|
Price | No Offer, no "from $" | App Store closed. Help: $1 / 100 then $1, cap, enterprise custom |
Subject | Product sheet, search, support, an agent | Shopify widget documented. Unavailable for installation in App Store |
Tools | Retail and direct sales, high consideration | Shopify self-service versus fixed enterprise. Bluecore |
Proof | No reviews, no "used by", no gross merchandise value (GMV) | No case study. 30-day attribution, not an audit |
The listing is correct about the job: a thread before purchase plus after purchase, not an Operator. The listing is wrong if "deploy" means Install App Store, if "high consideration" is a $0 tier, if merchandising signals are measured, or if CX agent is Gemini / UCP. Tool framework: what platforms need to change. Alby does not change the application firewall or the delegated payment. It can answer on a product sheet. A buyer agent does not buy just because a widget summarized a review.
Vocabulary (merchant assistant, not mandate): glossary of agentic commerce. The flow the machine compares: What a purchasing machine needs is not a chat round. After the click: readable storefront. Rails: how protocols differ. Neighboring layer: ConversionBox. Search: AI Search-TM. In-session ranking: Albatross. Magic: Magic / Sidekick. Parent sheet: AI app index. MCP: MCP versus API is not this widget. Alby talks. Search-TM searches. Albatross reorders. ConversionBox overlays. Do not merge them. Perplexity does not call your Purchase Pixel.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
App Store: no longer available, not a self-service installation
The App Store listing is the installation contract, not the Customer Experience Agent hook.
Unavailable: This app is not currently available on the Shopify App Store. Support questions: contact alby by Bluecore directly. The directory listing still says deploy. Two clocks. A directory listing is not an Install button.
Name: alby: AI Agent & Chatbot. Developer alby by Bluecore. Support provided by the same label. Privacy, Tutorial, App Documentation: page links, not an audit. No rating. No review count. No Built for Shopify badge held here.
No grid: no Free to install for Alby on this page. The visible Free plan / Free to install are cards for neighboring apps (other IDs). Do not attribute them to Alby.
Shopify anyway: the help pricing lives under Launch on Shopify. The App Store installation channel is closed. Two readings of the same publisher. Ask Bluecore for the current path. Do not invent a live ID.
A merchant opening the App Store from the ecommerceguide listing lands on a removed app. The listing does not say so. This is the first discrepancy. Strong direct sales consideration of a directory targets a retail buyer. The App Store targeted Shopify. The self-service help did too. Three customer profiles, one slug. A widget whose listing has disappeared remains a widget, or nothing at all. CSV-first is not Alby, but a SKU without a GTIN remains blind to a buying agent, even if well-answered in the chat. Breaks of a buying agent: elsewhere. Here, the break is a business Install 404, or a $1 directory.
Claim this listing: the listing is not claimed in the extracted hook. Own this listing. This is not proof of publisher ownership. Contact sales is not on the App Store. Contact Bluecore support, yes.
Help: $1 / 100, then $1, the widget turns off
The Assisted conversion pricing article is the self-service commercial contract, not "The Customer Experience Agent" hook.
Self-service vs. enterprise: brands self-serve, pricing outcome-based tied to assisted conversions. Enterprise: custom plans with fixed rates. Two contracts. The listing shows neither. No Offer 0. No from $.
Definition: an assisted conversion is Alby recommending a product or answering a question about that product, and the customer purchasing that product within 30 days. Counting is per product. A cart with three assisted SKUs = three conversions. Ski example: click on July 8, purchase the next day, credit. Boots example: fit questions, purchase same session, credit. Gloves example: recommendation, purchase two months later, no credit.
Pricing: each month, 100 assisted conversions for $1. Beyond that, $1 per assisted conversion. You set a monthly cap. If the cap is reached without an increase, the alby widget will automatically turn off until the beginning of each calendar month. Reactivation: increase the cap. A CX that turns off in the middle of the month is not an agent channel. It is a counter.
Tracking: catalog, JavaScript snippet, Purchase Pixel. Usage in Settings, Usage: month total, daily cost (assisted conversions times cost per purchase) over 30 days. support@alby.com. We do not detail implementation. Information security owner for the pixel. Finance owner for the cap.
Last Modified July 14, 2025. The 2026 App Store says unavailable. A help doc does not install a removed application. A $1 for the first 100 is not a high-consideration mattress total cost of ownership if you serve thousands of assisted. After 100, it is $1 per SKU. A 4-line cart can cost $4 in attribution. This is not gross merchandise value (GMV). This is not a 5x increase. Do not invent the 5x. Do not invent 6,000 questions. None of this is on the two pages cited.
The directory does not say $. A mid-sized CX manager budgeting a chatbot app at $49 does not have this pricing grid. An enterprise fixed rate is not the $1. Ask for a quote. Do not invent an unlimited tier. USD help. Directory schema without Offer.
At your home: a ceiling, a pixel, not an Agentic channel
At your place, Alby places a widget and an attribution, not an agentic Shopify sales button. Three elements. None of them are UCP.
The installation path: listing deploys against App Store not currently available. Help still self-service Shopify. Decide with Bluecore before a theme sprint. No live identifier here.
The $ contract: $1 / 100 then $1, or enterprise custom. Cap. Widget off. 30 days. Per SKU. This is not a $49 search subscription. This is not an Offer 0.
The pixel: snippet plus Purchase Pixel plus catalog. Confidentiality / logs: information security owner. Not a UCP agent purchase pixel. Not a procedure here.
No gross merchandise value (GMV) scenarios on the listing: do not invent them. No reviews. No "used by". No "take it": write it down (high consideration, one sales plus support thread, not 200 text SKUs). No "go look elsewhere": write it down (App Store closed, non-UCP, non-LLM text, non-Albatross ranking). Homepage schema: tracking. Widget plus helpdesk collapses: capability, not a measured ticket.
Owner: CX / e-commerce plus support (ticket deflection) plus merchandising (intent signals) plus finance ($1 cap) plus legal / information security (pixel, conversations). Not a UCP owner. Not a listings owner. A fake product listing title remains fake in a response. Catalog first, chat second.
High directory consideration: a mattress, a bike, a technical pair. The $1 per assisted SKU can be cheap compared to a commission. It can also hit the cap in three days on heavy traffic. The help says: widget off. Set the cap before going live, or accept a CX gap. This is not a service commitment. This is the seller's phrase.
Not Magic, not UCP, not a $0 chatbot
Do not merge ChatGPT shopping, Magic, ConversionBox, Search-TM, Albatross, and Alby. Six contracts. One thin product page. CX agent is not a seventh consumer buyer.
Surface | Contract | On your site |
|---|---|---|
Directory body | Product page, search, support, one agent, no $ | On-site CX. No "take it". No reviews |
App Store | Not currently available. Bluecore | No install. Support, not a grid |
Help pricing | $1 / 100, $1 thereafter, cap, pixel, 30 days | Result. Widget off. Enterprise custom |
UCP / ACP / Magic / ranking | Checkout tunnel / product pages / top-K | Outside widget. A response is not an Offer |
An "AI e-commerce agent" pitch can sell a product page overlay, a helpdesk, a ranking, or an agent channel. Four deliverables. Our two URLs: App Store and Help pricing. Neither UCP, ACP, nor Magic. No home schema as a payment provider. Reporting Alby is not reporting Merchant Center. After a response, it is your product page, your stock, your checkout tunnel. A purchasing agent reads an Offer. Your on-site conversation is not in any UCP protocol.
What this sheet does not measure
This sheet does not measure a conversion lift, gross merchandise value (GMV), or ticket deflection rate. Public totals remain human funnels. Collapses is not yours. 30 days is not an audited attribution service commitment.
No Offer / no $ from vs $1 / 100: two directory readings of "no price".
Deploys vs unavailable App Store: hook vs install. Help Shopify still alive.
Self-service $1 vs flat enterprise: two quotes. The sheet does not open either.
One agent vs widget plus helpdesk: index phrase. Not a single ticket measured.
Used by / reviews / GDPR / take it / alternatives: absent.
Merchandising signals: what it does. Not a dataset published here.
High consideration: directory customer profile. Not a named vertical on either page.
Widget off at ceiling: help phrase. Not availability.
30-day attribution / by SKU: seller rule. Not gross merchandise value (GMV).
Purchase Pixel: named. Not a cited compliance.
Do not budget a $49 chatbot like Alby. Do not budget Alby like ConversionBox. Do not budget Alby like UCP. Last Modified July 2025 is not a 2026 audit. Bluecore Contact is not Install. Home schema is not a single agent connection. Catalog plus reviews plus brand voice: directory ingestion, not a PIM.
Three tickets, not a CX $0 tier
This week, by installation path and by cap, not by UCP.
To install, or not?: App Store closed. Help Shopify. Listing deploys. Only one real one: the path that Bluecore opens for you today. If it's zero, pull out the theme sprint.
$1 / 100, or enterprise?: self-service versus fixed. Count the assisted after 100. Set the cap. Accept the widget off, or not. High consideration does not cancel the $1.
CX on-site, or purchasing agent?: widget versus Offer. Postpone UCP. If you wanted a $0 / 100 SKU overlay: another slug (ConversionBox). If you wanted in-session ranking: Albatross.
The single test: if the index removed "deploys" tomorrow, would the work remain? A Bluecore quote, possibly. An Install App Store goal, no. If the index added $1 / 100, would your RFP change? If yes, the listing was too thin. If the index removed post-purchase support, would your helpdesk brief change? If yes, you had the collapses header. If the index pasted UCP, would your payment provider change? If yes, you had the wrong word agent.
Owners: CX / e-commerce, support, merchandising, finance, information security, not a UCP owner. One hour: no Offer, App Store closed, $1 / 100, named pixel without procedure, 30 days. Ignore all gross merchandise volume (GMV). Paste "CX widget plus outcome attribution" into the user guide. Data Processing Agreement (DPA): no GDPR listing. Do not invent compliance. Buyer conversations: logs. Legal.
You are not turning on this widget as an AI sales channel
You don't turn on Alby in agentic Shopify sales channels. You place a widget, a catalog, a pixel. A buyer asks ChatGPT a question. Not this platform as a payment provider. A buying agent doesn't pay because a product sheet answered. It reads an Offer. Your conversation on the site is not in any UCP protocol. Your $1 is not a mandate. Your ticket deflection is not a channel. Your merchandising signal does not open a delegated payment funnel.
If a seller promises "the customer experience agent for retail", ask: product sheet overlay, search, helpdesk, email, or delegated payment funnel. The sheet names three (product sheet, search, support). Our two URLs no longer install one on the App Store. The rest is a thin sheet. UCP and ACP elsewhere. Carrying over Alby is not carrying over Merchant Center. After an answer, it is your product sheet, your stock, your payment funnel. The directory has not measured an increase. Do not attribute a gross merchandise value (GMV) to it. The CX hook closes the generic chatbot misunderstanding: the body speaks of merchandising context, the help of a $1, the schema of a homepage.
ConversionBox is another overlay. Search-TM a search. Albatross a ranking infra. Magic product sheets. Alby a CX agent (when the installation path exists). Five lines if you hold five real ones. A single owner who mixes UCP, high consideration, and $1 / SKU buys an agent channel and receives a widget that turns off at the ceiling. Separate the paths. Browse our apps is not Contact Bluecore.
The application firewall, the feed, the delegated payment funnel remain your platform tickets. A chat replaces none of them. If Gemini ignores a SKU, your widget on the site does not repair the machine catalog. If an agent compares two items, it reads price and stock, not your question history. A false title remains false. A false stock remains a false answer. Safeguards: absent from the sheet and the two cited pages. Do not invent a measured anti-hallucination.
Bluecore on the App Store: holding company, not a Wayfair study. Do not invent Wayfair. Do not invent 400 retailers. These names are not on the two URLs. Directory "used by": empty. Keep the void. A missing logo is not a client.
An index without $, a closed App Store, a $1
The product sheet fragments: intro an agent product sheet / search / support, retail CX hook, home schema without Offer, high consideration, five bullets "what it does", zero price, zero reviews. Starting point: CX on the site first, buying agent never. Index: which element (widget, helpdesk, attribution), who clicks (CX / e-commerce), what proof (none: 0 reviews). Not a chatbot ranking. ConversionBox / Search-TM / Albatross: filter, not three audits. Write go elsewhere: closed App Store, below a $0 chatbot tier, excluding UCP, excluding LLM text, excluding ranking.
You can ignore the product sheet and stick to the $1 help. You can choose enterprise custom and refuse self-service. You can use another layer (not mentioned outside of internal ConversionBox). The directory does not decide. Your object (product sheet versus delegated payment tunnel) does. Open Magic and buying agents. Put down the contract, not the hook. If the committee wants a single figure, refuse. 30 days, $1, high consideration, collapses, deploys: five sentences. None of them is gross merchandise value (GMV). None of them is a UCP. None of them is an Install.
The missing badge is not a $0 customer profile. A high consideration manager is not 100 assisted at $1. A fixed enterprise is not a listed Shopify app. Three sizes, one slug. What it does speaks of tickets. Help speaks of assisted conversions. App Store speaks of a dead app. Three personas. If you are the fourth (UCP owner), you are not on any line. This is the signal. Leave the product sheet. Go back to protocols and the flow.
Do not classify this address as an "agentic payment tunnel application". Do not classify this address as Magic. Do not classify $1 as optional. Do not classify closed App Store as a detail. Directory name Alby, Customer Experience Agent hook, AI Agent & Chatbot App Store: three hooks. One publisher Bluecore.
One CX owner, one pixel owner, not a CPU
The owner is not "growth, AI application." It is CX plus support, along with merchandising and finance. A single owner mixes UCP, high consideration, and a pixel. This is how a committee buys an agent channel and receives a widget in the end. Name the owner before the quote. If no one accepts the closed App Store, remove self-service Shopify from the RFP as long as Bluecore does not have a path. If no one accepts the widget off, remove the cap. If no one accepts the absence of reviews, demand a signed pilot. One job will remain: product questions, on your catalog.
Buyers see a chat, sometimes. Not this listing. You hold a home schema, a CX intro, a $1 help, a dead App Store page. The buyer sees none of the four. They see a bubble, or native search, or nothing if the cap cut off. Your stock, your price, your checkout funnel. If the committee wants a figure: collapses is not yours. 30 days is not gross merchandise value (GMV). $1 is not Offer schema (there is none). A tool is budgeted on assisted conversions and a cap, not on a JSON-LD. The unmentioned home page is not a single sign-on. The pages mentioned are App Store and Help pricing.
Test of the following week: an installation question against listing deploys, a $1 question against high consideration, a CX question against UCP. Otherwise, you have a directory address. If all three hold without gross merchandise value (GMV) and without a delegated checkout funnel, you have a contract. If one relies on merchandising context as proof of an increase, you have a brief. If one relies on Customer Experience Agent as a payment provider, you have a slogan. Come back Monday with an installation path, a cap, a pixel owner. Not with a slug.
The discipline that survives: up-to-date catalog, true return policies, reviews you have the right to serve, a human on the conversations the widget invents, a cap that finance has signed. That is CX and data work. An agent accelerates it. A thin listing photographs it poorly. A dead App Store photographs it worse. Do the work. Buy then, or don't.
If Bluecore reopens installation tomorrow, reread the help: the $1 will not have moved on its own. If Bluecore does not reopen, the directory listing will remain a hook. Do not budget a hook. Budget a pixel, a cap, and an owner. Or remove the line.
Frequently Asked Questions
Is it a buying agent?
No. A CX agent on the site (product page, search, support). ChatGPT / Gemini shopping: consumer surfaces. Not UCP. An answer is not a mandate.
Why no price on the page?
No Offer, no badge. Help: 100 assisted conversions for $1 / month, then $1 each, cap, custom enterprise. Quote. Widget turned off at cap.
Can I install it on Shopify?
The App Store says "not currently available". The pricing help remains under Launch on Shopify. Ask Bluecore for the current path. Do not invent an Install button.
Is it a helpdesk, or sales?
The page: both, an agent. Index: collapses pre-purchase and post-purchase. Help: attribution on a SKU purchase. Three readings. Keep them separate.
Does it replace Magic / a PIM?
No. Catalog, reviews, policies as sources. A false title remains false. Magic writes product pages. Alby answers. Two different jobs.
Is the 30-day attribution gross merchandise volume (GMV)?
No. Seller rule, per product, examples: skis / boots / gloves. Not an audit. Not an increase published here.
Are there reviews / "used by"?
Not on the page. Not on the two mentioned pages. Do not invent a case study. Do not attribute ratings from neighboring App Store applications.
What to do this week?
Check the installation. Read $1 / 100. Set a cap. Address information security for the pixel. Postpone UCP. Do not budget a widget like an agent channel.
Sources
Enzo
August 19, 2026
