An AI recommendation can identify a suitable business without delivering a reservation. Between those two points, the customer may need to choose the correct experience, repeat their requirements, select a session, check who the booking covers and confirm what happens next. Every handoff can change the meaning of the original request.
For a business, the useful question is not simply whether an assistant mentions you. It is whether a customer following that mention can still book what they asked for. A prominent recommendation that opens a general homepage may be valuable discovery, but it leaves more work than a link to the appropriate class or service.
A small Dubai pottery example shows how to inspect that gap. On 5 November 2026, we asked Google AI Mode and Perplexity Search the same question about a beginner wheel class for two adults. Google produced an answer; Perplexity led to a sign-up screen. We followed one actual Google link into the studio's public website and checked the route toward a class selection. This is a limited handoff inspection, not a ranking of platforms or studios, and no reservation was made.
Write down the requirements that must survive the handoff
Before inspecting links, turn the customer's request into a short set of requirements. In this example, the customer wanted Dubai, two adults, a beginner pottery wheel class and a class booking rather than a gift voucher. Those details determine whether the destination is useful.
Do not add requirements that were never requested. Two adults does not necessarily mean an adults-only session. A class for two people does not necessarily mean private tuition. An interest in wheel throwing does not include every activity sold by a ceramics studio. Keeping the original request visible prevents both accidental narrowing and accidental substitution.
Use one row per requirement, with room to record its status at the recommendation, landing page and booking stages. The status can be confirmed, still to choose, unclear or contradicted. “Still to choose” is often a normal part of booking. It becomes a problem when the visitor cannot tell that the choice remains open.
For example, a homepage can correctly identify the studio while leaving the activity unresolved. A product page can establish the activity while leaving the date unresolved. Neither should be counted as a completed reservation. The assessment needs to say what the customer has gained and what they still need to do.
What the two search attempts actually returned
The exact question was:
Where can two adults book a beginner pottery wheel class in Dubai? Give studio names and official booking links, and distinguish a class from a gift voucher.
Google AI Mode returned a ready answer naming Bedia Pottery, Dubai Pottery Studio, Yadawei Ceramic Studio and The Mud House Studio. It separated class booking from gifting in its explanation and supplied website links. We did not adopt its descriptions of popularity, quality or ratings as verified facts.
In Perplexity, Search was selected and Computer was not selected. After the same question was submitted, the page displayed a sign-up screen. No usable answer was read, and we did not sign in. That is an observed access limit for this attempt, not evidence that Perplexity cannot answer the question or is unavailable throughout the UAE.
| Surface inspected | Result of this attempt | What it allows us to assess |
|---|---|---|
| Google consumer AI Mode | Ready answer with named studios and links | One recommendation-to-website route |
| Perplexity consumer Search | Sign-up screen after submission | The access handoff, with no answer-quality comparison |
| Studio website reached from Google | Public category and class pages | Offer choice and pre-booking information |
Google's consumer AI Mode help lists the UAE in its availability information and warns that responses can contain mistakes. That supports checking the source after receiving an answer; it does not certify a particular booking link or session.
Perplexity's Search versus Computer guide distinguishes cited answers from multi-step execution. Our attempt concerned Search. It should not be reported as a test of its Computer product or an autonomous reservation service.
Both attempts used the consumer web interface in the same desktop browser, with sign-in options visible. We did not independently verify the search-location basis, isolate cookies between products or repeat the question over time. The observed difference cannot establish a general success rate or a cause for the sign-up requirement.
Follow the actual link before calling it a booking link
We selected the Bedia Pottery link from the Google answer because it was a named studio with a displayed official-website link. The actual Google redirect was followed, rather than replacing it with a guessed address or a separately searched page.
It resolved to the studio homepage. That page offered separate adult, children's and family routes, with a separate gift-card link. It did not arrive with the requested party size or a session already selected. The answer had provided a route to the business, not a prepared reservation.
From there, the adult experience route opened a category page containing wheel, handbuilding, couple and other options, alongside a voucher option. The wheel experience was a further choice. A visitor who treats every “Book Now” label as the same product could leave the intended activity at this point.
This does not mean a homepage link is broken or inappropriate. A general destination can be the right choice for broad discovery. The reporting problem is calling it a direct booking link when the customer still has to identify the experience. Record the destination type: homepage, category, specific offer, scheduling page or enquiry channel.
For your own business, inspect the landing page before changing anything. Is the requested experience recognisable? Are the alternatives clearly named? Can someone return to the relevant information without losing their place? A recommendation mention and a usable next step deserve separate entries in the report.
Check the offer and the party size separately
The Bedia Pottery Wheel Experience page described a beginner session and provided clay, date, time and participant controls. We retained the default Air-Dry choice, selected 10 November and increased the participant display from 01 to 02. The displayed amount changed from AED 249 to AED 498, each marked with an additional 5% VAT. These were pre-checkout displays, not a final paid total.
We also clicked an afternoon time option, but the recorded evidence did not clearly confirm a retained selected-time state. We therefore do not report a complete scheduled selection. A visible option and a click are weaker evidence than a reviewable date-and-time summary.
The class FAQ described shared sessions and distinguished evening adults-only times from other sessions that may include children. That matters when interpreting “two adults”: party composition and the composition of the whole class are separate questions.
For any booking business, check quantities against the wording beside the selector. Does one unit mean one person, one pair, one table, one room or one session? A price that appears to cover two people may be a per-person amount. A product title mentioning couples may still need a clear explanation of what the quantity buys.
Keep these questions in the acceptance record even when the customer is using the site manually. An assistant can repeat the request accurately, but the website still needs to make the booking unit understandable. The customer should be able to review the chosen item and party size together before committing.
Distinguish a gift from a reserved session
The studio's separate gift-voucher page offered gift customisation rather than the same scheduling flow. Its instructions described email delivery, redemption using the voucher's instructions and a later choice of date and time. The inspected page stated one-year validity.
Those details support a distinction between buying the gift and reserving the eventual experience. They do not establish that every studio uses the same redemption process or that a recipient is guaranteed a preferred slot. The AI answer's general description should be checked against the particular voucher product.
For a business selling both, keep the two outcomes explicit. A gift purchase confirmation should tell the buyer what was delivered and what the recipient must do next. A class confirmation should identify the booked session. Avoid a shared success message that makes both look like attendance has already been scheduled.
The distinction also matters in reporting. A voucher sale is a real commercial outcome, but it is not the same event as a dated reservation. If the customer's stated goal was to attend together at a particular time, a voucher may leave that goal unfinished even though payment succeeded.
When reviewing an AI-assisted journey, ask what evidence would resolve the remaining task. It might be a session confirmation, a redemption instruction or an answer from staff. Do not convert uncertainty into an assurance merely because the business has a booking button somewhere on its website.
Treat a message invitation as another handoff
The studio's website linked to its public Instagram account. We checked an official Bedia Pottery reel whose canonical page timestamps were dated 2 November 2026. The profile grid carried a different date label, so the canonical post evidence governs the date recorded here.
The caption promoted a particular cup-making experience and invited a direct message using a booking keyword. The visible frame showed a decorated cup. We inspected the caption and a visible frame, without reviewing the full video or audio. That is evidence of a promoted message route, not evidence of a confirmed session or of the same offer as the standard wheel page.
A message-based route can work well when staff need to clarify the request. It should still tell customers what information to provide and what response confirms a reservation. An outgoing message, an automatic acknowledgement and a staff-confirmed appointment are different states.
For your own social campaigns, compare the promoted experience with the website route. Keep the product name, participant conditions and next step understandable across both. If the customer must quote an offer name or send a keyword, record that requirement rather than assuming an assistant can silently carry it into another channel.
We sent no message to the studio. Response time, staff handling and eventual booking quality remain outside this inspection.
Read the policy beyond the short FAQ answer
A concise answer about flexibility can omit conditions that matter to the customer. The studio's published cancellation and rescheduling policy contained more detail than its short class-page FAQ: written notice, availability, a limit on complimentary rescheduling and provisions for differences in workshop value. It also distinguished ordinary bookings from promotions that may carry additional conditions.
The business lesson is to connect a short summary to the governing published policy. “You can reschedule” is incomplete if the visitor needs to know when, how and subject to which restrictions. An AI summary should not turn a conditional process into a guaranteed option.
This is a description of the inspected business policy, not an interpretation of a customer's legal rights. Before purchasing, the customer needs the current terms for the actual product and booking circumstances. For a website owner, the practical task is to make those terms accessible at the point where the customer decides.
Record policy uncertainty as a separate issue from technical navigation. A link may work perfectly while leaving a material question unanswered. Conversely, a detailed policy page may exist but be difficult to find from the relevant offer. Those require different fixes.
Assign the gap to the right part of the journey
A useful review describes the gap precisely enough that someone can act on it. Avoid treating every unfinished booking as an AI error or every mention as a successful conversion.
| Handoff gap | Evidence needed | Likely work to investigate |
|---|---|---|
| Answer names a business but opens a broad homepage | Actual destination and remaining choices | Clearer experience routes and accurate reporting labels |
| Customer reaches the wrong activity | Requested activity and destination product | Offer naming, category structure and source accuracy |
| Party size is lost or ambiguous | Selector meaning and review summary | Quantity labels and booking-unit explanations |
| Date or time cannot be confirmed | Retained selected state or session summary | Scheduling feedback and test-method limitations |
| Voucher is mistaken for attendance | Purchase and redemption instructions | Distinct gift and reservation outcomes |
| Customer is moved to messages | Information requested and confirmation process | A clear staff handoff and enquiry status |
| Search product requires access | Observed account screen and test conditions | Separate access reporting, without invented answer results |
These are investigation categories, not measured failure rates. A broad homepage may be an intentional destination, a message route may be the appropriate service model, and an access screen may reflect account conditions. The review should identify what remains necessary for the customer's goal before deciding whether a change is warranted.
Give each issue an owner and a verification step. Content work should be checked by reading the revised explanation. Scheduling work should be checked by inspecting the selected state. Staff handoff work should be checked in an authorised test that follows the enquiry through to the promised response. A screenshot of a button alone cannot establish all three.
Report the remaining work as clearly as the recommendation
The most useful final note says what the customer can do next and what is still unconfirmed. “The studio offers a relevant class; choose the session and verify the party total” communicates more than “booking available.” It preserves the distinction between identifying an option and reserving it.
Keep the original question beside the destination and outcome in your internal record. Repeat the inspection after a booking-provider change, a renamed package, a new voucher process or a major campaign. If you test multiple assistants, retain inaccessible attempts and compare only the stages actually observed on each.
The Google AI Search overview remains the starting point for discovery work. Booking-handoff work adds the next question: can a customer carry the same requirements from the recommendation into the reservation process without silently changing the product, party or promise?
Checked 5 November 2026. One usable consumer AI answer, one access-limited attempt and one studio route were inspected. No cart addition, checkout, message, reservation or payment was completed. Displayed amounts were observed before checkout. AI Visibility is published by Lunasol, which offers related GEO and AEO services. This article was prepared with AI assistance and has no attributed human byline.



