Retail

Answer store questions before the visit, not after it

A customer planning a trip to your store wants to know it is open, that the thing they want is likely there, and what happens if it is wrong.

Start free See how it works

No credit card. Live in an afternoon.

“Are you open on the bank holiday?”

“Can I return something bought in store?”

“Is there parking nearby?”

“Do you have this in stock at the Leeds branch?”

What a shop actually gets asked

Both columns matter. The right-hand one is what a reader is really checking for, so it is on the page rather than in a footnote.

Answered from your own pages

The reply is the answer, with a link to the page it came from.

“Are you open on the bank holiday?”
“Can I return something bought in store?”
“Is there parking nearby?”
“Is the shop step-free?”
“How does click and collect work?”

Handed to a person

Declined plainly, then routed with the whole conversation attached.

“Do you have this in stock at the Leeds branch?”
“Can you hold one for me until Saturday?”

Each of these arrives with the whole conversation attached, so whoever picks it up starts from what the customer already said rather than from a one-line message.

The glazed door of an independent shop at dusk, interior dark but for one display lamp, the street reflected across the glass.

Store questions arrive on the way to the store

Opening hours over a bank holiday, whether click-and-collect is ready, the returns window, parking and accessibility. These are asked in the half hour before a visit, which is precisely when a phone call will not be answered.

Holiday opening hours generate a wave of identical calls
Customers arrive expecting a returns policy you do not have
Click-and-collect questions tie up staff who are serving customers
Accessibility and parking questions have no obvious place on the site

You have already written most of it

Point the crawler at these four and the assistant has what it needs. There is nothing to re-author, and nothing to keep in sync afterwards.

01
Store pages
Hours, address, parking, access — per location.
02
Returns and exchanges
The in-store policy, which is often not the online one.
03
Click and collect
How it works and how long it takes.
04
Seasonal notices
Bank holidays and changed hours, published once.

The pre-visit questions

Hours including holidays, location and parking, accessibility, returns and exchange terms, and how collection works. Answered instantly with a citation, so the customer arrives with correct expectations.

Hours and holidays: From your published information, including the dates that generate calls.
Returns and exchanges: The real window and conditions, cited, before the customer travels.
Access and parking: Practical detail that is rarely easy to find and frequently needed.
Collection process: How click-and-collect works, so staff are not explaining it by phone.

Multi-site without merged answers

Chains get this wrong by answering from a merged pool, so a customer is told the hours of a different branch. Running a bot per site, domain-locked and indexed on that location's pages, keeps the answer specific to the store being asked about.

Consistent with what is on the door

Because answers come from your published pages and cite them, the assistant cannot state a policy that contradicts your signage — and a policy page update reaches it on the next crawl.

Answered on the way in

Store questions are asked from a phone, in transit, before the visit.

The same answer as the door

Opening hours come from the page you already keep current.

Staff stay with customers

The phone stops interrupting the person being served.

Per-branch, not merged

Each location can run its own bot so answers do not blur together.

Where the line is

It cannot see what is on the shelf

Live stock is the boundary in retail. The assistant answers from your published pages, so it can explain click and collect and your returns policy, but it does not know whether the Leeds branch has one left — and pretending otherwise sends somebody on a wasted journey.

Hours, policies, access and collection: answered from your pages
Stock at a specific branch: routed to that branch
Holds and reservations are a person's job
Multi-site works best as one bot per location, not one merged index

Holiday hours are the recurring win. Publish them once on the page the assistant already reads and the wave of identical calls stops arriving.

A shop stockroom of metal shelving stacked with plain boxes, one pulled half out with tissue paper spilling from it.

What a shop asks first

Short answers. If yours is not here, the assistant on this page will try it — and tell you honestly if it cannot.

Can it check whether an item is in stock?

Only to the extent your website publishes stock information. Live inventory lives in your EPOS rather than on your site, so stock questions are best escalated to the store.

Can it handle different hours per branch?

Yes, by running a bot per location indexed on that location's pages. A single bot fed every branch's hours will sometimes answer with the wrong branch, which is worse than not answering.

How quickly do updated hours reach it?

It re-crawls on a schedule and re-indexes what changed, so updating your published hours page is enough. For a known date like a bank holiday, publish ahead of time as you would anyway.

All solutions