Skip to content
Independent travel website owner answering visitor questions from a Bergen office

Website support for WordPress and standalone sites

Your website answers the question. Your team gets the request.

A discreet help panel answers from approved pages and files, shows the useful image or link, captures contact details and opens a ticket when human judgement is needed. No CRM is required to start.

14 days after setup - no bank card - a paid plan starts only after separate approval

What this closes

The answers are already on the site. Visitors still leave without them.

You published hours, process, prices and a contact page. People still ask the same questions, wait until Monday, or give up. The team then reconstructs the story from email, messengers and leftover notes.

01

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.

02

Silence after hours is a lost thread

A visitor who writes on Sunday should still find an explanation, or leave a request that the team sees on Monday.

Fewer people disappear between the question and the working day.

03

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.

04

An awkward overlay will not survive design review

The help panel has to sit on a contemporary site without shouting over the brand, the photography or the layout.

Designers can accept it. Owners can actually put it live.

Who this is for

Built for the people who own, run and design the site

The visitor gets a clear explanation. The owner gets time back. The team keeps the conversation, the contact details and the notes in one place.

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

A quiet panel that belongs on a modern website

  • Compact on a phone, unobtrusive on a wide screen
  • Rounded, calm and readable without visual noise
  • Does not compete with photography, type or brand colour
  • The help lives on the site you already designed

The site stays the main object. Help does not look like an afterthought.

How a request moves

Answer now. Capture what matters. Keep the next step visible.

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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 on the website

Let the answer show the experience, not just describe it

This example uses a real public article about boat trips from Bergen. Switch between a visual answer, an in-chat contact form and a ticket ready for a person.

Grounded in the page

The answer uses the article's facts and points back to the source instead of improvising availability.

Images carry meaning

A compact gallery lets a visitor compare the harbour, waterfall route and village without leaving the chat.

The form stays in context

Contact details, the question and the source page arrive together when the team needs to reply.

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.

Private yacht leaving Bergen harbour beside the colourful Bryggen waterfront
Small yacht passing a tall waterfall in the narrow Mostraumen fjord
Quiet fjord village of Modalen seen from a boat in warm evening light

Ask about this experience

Send

Illustrative support flow using a public NordCeremony article. View the source article

Help that uses your own material

The best answer is assembled from the page the visitor is viewing

Instead of a generic reply, the visitor gets the relevant passage, the right photography and a direct route back to the source. The website remains the authority.

Private yacht leaving Bergen harbour beside the colourful Bryggen waterfront
Small yacht passing a tall waterfall in the narrow Mostraumen fjord
Quiet fjord village of Modalen seen from a boat in warm evening light

Example knowledge source

Bergen from the Sea

One published article supplies the places, route descriptions, season guidance and imagery used in the answer.

  • Bergen harbour
  • Mostraumen waterfalls
  • Modalen day trip
  1. 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.

  2. 02

    Explain with pictures, not only text

    A photograph, diagram or compact gallery appears only when it makes the answer easier to understand.

  3. 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.

  4. 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

Website
Recommendation 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.

View recommendation

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.

Visitor path is not a surveillance claim

The team can see the pages a visitor used where the site and consent allow it. That context helps a reply. It is not a promise to track every movement.

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.

A calmer way to be available

Give visitors a clear answer. Give the team the rest of the day back.

Start with the questions you already answer every week. Put a quiet help panel on the site, keep every request in one inbox, and let a person join when it matters.

Discuss this setup

14 days after setup - no bank card - a paid plan starts only after separate approval