Search, contact, chat, feedback, a demo, an offer and cookie settings can all help someone on a website. They cannot all be the first thing a visitor sees on a phone. When a team calls each one “important”, the word stops helping it choose.
An action deserves persistent visibility when it remains useful while the visitor moves through a page or journey, is hard to find at the moment of need without that placement, and does not make the main task harder. Persistent means it stays available as the page scrolls; it does not mean the action should appear on every page, for every visitor, forever.
The choice is about actions, before it is about toolbars, bars or pop-ups. First decide which few routes earn ongoing access. Then choose the visual pattern. The pattern comparison covers that second decision.
Begin with the moment someone would need the action
“Book a demo” is valuable to sales. That tells you little about where it belongs. On a product comparison page, a visitor who has understood the choices may welcome a conversation. On the first paragraph of an educational article, the same request may be early. On a short landing page with a visible booking form, a duplicate floating demo button may add nothing.
Write one plain sentence for each candidate: “A visitor needs this action when…” Be specific enough that a colleague could point to the relevant page or task. “A visitor needs search when they cannot find the right help article” is useful. “A visitor needs search so we improve engagement” is a target without a visitor problem.
Then ask how far that need travels. Search can be useful across a large resource library. Feedback may be useful after a guide or support answer. An event registration link matters for a particular campaign and should have an end date. A one-time confirmation belongs at that moment, not in a permanent bar.
The best candidate is not always the most commercially valuable in isolation. It is the one whose continued availability helps the visitor most without taking away more valuable page space.
Use five checks before giving an action a fixed place
The existing Barrava article called this the PLACE decision aid. It is a team-made way to remember five questions, not an industry score or benchmark. Keep the letters only if they help the conversation:
| Check | Question to answer | A weak answer sounds like… |
|---|---|---|
| Purpose | What visitor job does the action help complete? | “We need more clicks.” |
| Location | On which pages and points in the journey is it still useful? | “Everywhere, because it is easy to install.” |
| Audience | Who needs it, and does that change by device or state? | “All traffic is the same.” |
| Consequence | What happens if the action is not persistent, and what does its placement cover or displace? | “It might be missed,” without checking the page. |
| Evidence | Which outcome and experience checks would keep or remove it? | “The button got clicks.” |
An action does not need five perfect scores. It needs credible answers. If its purpose is clear but its location is narrow, put it in the relevant content. If its reach is wide but it covers a form control on mobile, change the placement or remove another action. If no one knows whether it helps, try a smaller scope and set a review date.
For the Consequence check, look at both sides. What does the visitor lose if the route is tucked away? What do they lose if it follows them around? Google Search Central warns about promotional overlays that obstruct access to content. A persistent action need not be a full-screen overlay to cause a problem: a small control can sit over the final link or a consent choice on a narrow phone.
Shortlist actions on a real page
Here is an illustrative scenario, not a Barrava customer result. A software company has a long help article on connecting a data source. The visitor's main job is to finish the connection. The page already has normal site navigation. Teams propose five persistent actions: search, chat, “Book a demo”, feedback and cookie settings.
The team walks the article as a visitor would. Search is useful if the connection guide is the wrong answer, and it is needed on many help pages. Feedback is relevant after the visitor has tried the steps, especially if the article is incomplete. Chat can help a person stuck on an error, but the open panel may cover the instructions. “Book a demo” serves a different, earlier sales journey and has no obvious job here. Cookie settings must remain findable under the site's consent design, but that does not automatically mean they need to share the article's main action space at every moment.
| Candidate | Decision on this help journey | Reason and condition |
|---|---|---|
| Search | Keep easy to reach | It provides another route when the answer is wrong; check whether existing navigation already does this well. |
| Feedback | Offer near the end, or keep a modest route if evidence supports it | The visitor can judge the answer after trying it; measure usable reports, not button presses alone. |
| Chat | Make available as help, but test the open state | An error may justify it; it must not cover the step or error message. |
| Book a demo | Return to product or commercial content | It does not help complete this support task. |
| Cookie settings | Keep an accessible route under the site's consent setup | The route must work; its exact placement is a separate privacy and design decision. |
Suppose the first mobile layout puts search, chat, feedback and demo in one bottom row. Labels shrink and the feedback form opens over the final instruction. The team removes demo from this page, leaves feedback in an inline “Did this solve it?” section, and tests search and help as the continuing routes. It then checks the page with chat open, a keyboard raised and the last link focused. WCAG 2.2 says a keyboard-focused control must not be entirely hidden by author-created content. The target-size guidance also explains why squeezing many small controls together creates an accessibility problem.
This is a decision, not a reported result. If the site's own data shows that help search is rarely used and the normal navigation works, it may leave the persistent slot empty. If error-related chat use genuinely helps people finish the connection, it may give chat more prominence. The action set should change when the evidence or visitor task changes.
Check the route, then the outcome
For each chosen action, record what someone does after selecting it. A search click is not a found answer. Opening chat is not a resolved issue. Starting a demo form is not a completed or qualified request. Google Analytics events can record the steps; your team must define the meaningful completion for each route.
Pair that outcome with an experience check. Can people still reach the last control on mobile? Does an open panel cover instructions? Does a returning visitor see a dismissed campaign again? Are labels legible and controls easy to activate? Review the same page with the other real site tools present. The newest action does not get to pretend chat, consent and browser controls have vanished.
Set a date to revisit the shortlist. A temporary offer ends with its campaign. A recurring support action can be reviewed when the site structure or traffic mix changes. The decision should be renewed with evidence, not inherited indefinitely because removing a widget feels risky.
Give the selected actions a deliberate place
Barrava's current toolbar makes this shortlist concrete. Its modules are ordered, and that order is placement. CTA buttons are modules rather than a separate lane; a second CTA can form a dual-CTA result on Starter or a higher plan. Teams can hide a module or the whole bar by device and choose docked or floating presentation. These are ways to express a decision; they do not automatically decide which action matters or create page-specific relevance from device settings alone. On eligible accounts, chat and cookie-settings modules can open supported providers already installed and tested on the site. Barrava does not supply those services, and the integration and plan need checking for the particular site.
Use Barrava's website toolbar when several actions genuinely need one consistent access layer. Keep page-specific answers in the page. Before asking for one more persistent slot, name the visitor moment it serves, the route it improves and the content it could cover. If you cannot answer all three, the action has not earned the space yet.
