The same questions return every day
Opening hours, parking, how a process works, who to contact. Someone on the team types the reply again.
Hours come back when the site can give that answer itself.
Website support for WordPress and standalone sites
Answer common questions. Keep enquiries in one inbox.
Answer visitors using your website pages and files. When a person is needed, your team gets the conversation and the contact details the visitor shares. No CRM needed.
14 days after setup - no bank card - a paid plan starts only after separate approval
Help on the website
See an answer, a contact form and a handoff
This illustrative example uses a public Bergen travel article. Explore an answer with images, contact capture and a ticket for the team.
SL
Bergen trip guide
Answers from this page
What would we actually see on a boat trip from Bergen?
The page describes three distinct views: Bergen and Bryggen from the harbour, the narrow Mostraumen passage with waterfalls, and a full-day arrival in the village of Modalen.
Ask about this experience
SendIllustrative support flow using a public NordCeremony article; route images are illustrations. View the source article
Where enquiries get lost
The answers are already on the site. Visitors still leave without them.
Visitors ask about hours, prices and services, including after closing. Answer common questions and pass other requests to your team with the conversation attached.
Capture enquiries after closing
A visitor who writes on Sunday should still find an explanation, or leave a request that the team sees on Monday.
Your team can pick up the request when they return.
Requests scatter across channels
Email, WhatsApp, Telegram and a contact form do not share a history. Someone has to rebuild what the visitor already said.
One inbox. A cleaner handoff. Less hunting.
Fits your website, including on mobile
Visitors can open help without leaving the page they are viewing.
Works on WordPress and standalone websites.
Who this is for
Answers for visitors. Context for your team.
Visitors get answers from your content. Your team receives requests with the history attached.
01For visitors
A clear answer without hunting through the site
- Ask in ordinary language, including after hours
- See photos, a short explanation and a link to the right page
- Leave a request when a person should reply
- Continue in WhatsApp or Telegram when that channel is connected
Fewer dead ends. A calmer first contact.
02For owners and administrators
Time back, and fewer lost contacts
- Everyday questions no longer wait for a person
- Every request lands in one inbox instead of three tools
- A ticket keeps the name, the question and the next step
- Customer notes stay attached to the person, not a forgotten chat
Less reconstruction work. A more reliable way to stay available.
03For designers
Help on the website you already built
- Compact on a phone, unobtrusive on a wide screen
- Readable text and links on small screens
- Does not compete with photography, type or brand colour
- The help lives on the site you already designed
Visitors stay on the page while they ask.
How a request moves
From a visitor question to a team request
Routine questions can finish inside the page. A request that needs availability, judgement or a personal reply keeps its context and moves into the team inbox.
- 01
The visitor asks in their own words
They ask from the page they are viewing instead of guessing which menu, form or email address to use.
- 02
The reply uses your pages, photos and files
The answer can combine a concise explanation, relevant photography and a link back to the approved source.
- 03
The panel captures the missing details
Name, preferred contact and the request are collected in context, without sending the visitor to a disconnected form.
- 04
A ticket reaches the right person
The inbox keeps the conversation, source page, contact and next action together, so a teammate can continue without asking the visitor to start again.
Help that uses your own material
Answers linked to your published information
Use your pages, files and images to explain an answer and link to the source.
Example knowledge source
Bergen from the Sea
Published route descriptions supply the example answers. The images illustrate the places described.
- Bergen harbour
- Mostraumen waterfalls
- Modalen day trip
- 01
Search across the live site
A visitor asks in ordinary language. The reply resolves the intent and points to the page that holds the detail.
- 02
Explain with pictures, not only text
A photograph, diagram or compact gallery appears only when it makes the answer easier to understand.
- 03
Send people to the right page
When a longer read is needed, the visitor gets a clear link instead of a wall of copied text.
- 04
The same help in more than one language
If you prepare the source material, the same explanation can be offered in the languages you enable.
One inbox for every request
Website, WhatsApp and Telegram land in the same place
A travel recommendation, an urgent support problem and a new service enquiry should not look like the same thread. Open each request to see its conversation, priority, captured details and next action.
Requests
Conversation
Sofia Martin
WebsiteRecommendation sentPriority: Low
We have one day in Bergen. Which private boat trip works best if waterfalls matter most?
I found 3 published options. Mostraumen is the clearest match because the page specifically describes narrow fjords and close waterfall views.
Recommended from the website
Best match · waterfalls
Private Mostraumen cruise
Narrow fjords, steep cliffs and waterfalls close to the water.
Shorter · city views
Private yacht around Bergen
Bryggen, the harbour and nearby islands from the water.
Full day · village stop
Full-day trip to Modalen
Mostraumen plus time ashore in the village of Modalen.
Pages this visitor used
Experiences → Boat trips → Bergen from the Sea
Captured contact
No contact requested. The visitor received the answer in their chosen channel.
Current outcome
The visitor compared 3 routes and opened the Mostraumen source section.
Next action
No team action unless Sofia asks about live availability.
Team note
Waterfalls matter more than city views. The visitor did not ask for a callback.
What this is not
A support desk, with a person still in control
The product is built to explain, collect and hand over. It does not try to sell through the conversation.
No shopping or basket automation
It can recommend a relevant page or service from approved material, but it does not rank catalogue products, track a cart or recover baskets. Those workflows belong to the online shop solution.
Answers come from your material
Pages, files, photos and notes you approve. It should not invent prices, legal terms or availability that are not there.
Channels depend on the connection
Website help can start first. WhatsApp, Telegram and other channels follow the provider, the account and the permissions you enable.
A person takes judgement calls
Complaints, exceptions, custom work and anything that needs a human decision wait for a teammate. The visitor does not start the story again.
Page context follows your consent settings
Where your site and consent settings allow it, the team can use page history to understand the enquiry.
Before connecting
Practical questions from website owners
Clear answers about the site, the inbox, languages, handoff and the first rollout.
It can take the questions that today wait in a form. Visitors still get an explanation immediately, and they can still leave a request when a person should reply. You can keep a contact page. The difference is that the visitor is not left without an answer while they wait.
Start with your common questions
Answer repeat questions. Give your team time back.
Choose the questions your team answers each week. We will agree the source pages and when a person should take over.
Discuss website support14 days after setup - no bank card - a paid plan starts only after separate approval