The Same Questions Keep Coming
Hours, price range, service area, or how to start. An assistant that answers from your pages saves the buyer a hunt and saves you a repeat WhatsApp.
Answer. Don't Decorate.
AI on a website should answer a buyer or save staff time. We design assistants, structured content, and integrations in the same plan as the pages — so the site still works when the widget is quiet.
The Assistant Behind the Page
You need AI on the site when the same questions keep landing on WhatsApp, or when staff copy the same answer from a PDF. The site already has the knowledge. The assistant should use it.
We name the job first: answer a buyer, route an enquiry, or draft from your pages. Copy, schema, and the integration sit in the same plan. SEO, AEO, and GEO still matter — a useful assistant is not a substitute for pages Google and ChatGPT can read.
If the visitor needs a full page to decide, write the page. If they need a short answer from those pages, we can put an assistant on that path.
Four starting points we see in Malaysia. If the visitor already has a page, do not hide it behind a guessing chat.
Hours, price range, service area, or how to start. An assistant that answers from your pages saves the buyer a hunt and saves you a repeat WhatsApp.
A PDF, a price list, or a spec sheet that someone types out again. We wire that knowledge to the site so staff start from a draft, not a blank chat.
Too many SKUs or services to scan on a phone. A search that understands the question can land them on the right product page.
The enquiry form asks for everything. A short path that names the job first can route the enquiry before they abandon the page.
The same decisions as a full site, plus the assistant. Nothing decorative without a job.
Answer, route, or draft. We write the job before we pick a tool. An assistant without a job is a spinner with a smile.
The source of truth is the site you already built — copy, FAQs, and specs. We do not invent a second voice that fights the page.
If the assistant can read it, search and AI answers can too. Titles, headings, and schema stay in the HTML so AEO and GEO still work.
Enquire, book, or WhatsApp. The assistant should hand the buyer a next step, not a longer chat.
Compressed media, clean HTML, no third-party font CDNs. A slow assistant spends the visit on a wait state.
We name the task and how you will see it. An assistant without a count is decoration with a prompt box.
A shorter path than a full site rebuild. Still a dated plan. Still no widget before the job is named.
The questions, the source of truth, and the one action after the answer. We write the assistant job before we draw a block.
The pages, the prompts, and the handoff on real copy. Mobile first. You sign off on a phone, not only a wide screen.
Fast HTML, schema, and a task you can count. Launch is a date. Care stays available if the questions change.
Short answers on when you need an assistant, how long it takes, and how this differs from AI search optimisation.
Tell us the questions that keep coming and where the answers already live. We reply with the assistant job, a dated plan, and whether AI on the site is the right work.