Getting help — the help center, in-app tips and support

Every feature in Clavoz has a guide, and every guide ships inside the app, in the same repository as the code it describes. That is deliberate: when a button moves, the guide that names it moves with it. This page is about finding those guides, using the question-mark hints scattered around the app, and getting a human answer when a guide does not settle it.

The help center

Open Help Center in the left sidebar. It lists every guide the app has, grouped by category — Why Clavoz, Getting Started, Account & Billing, Estimates & Claims, Proposals & Closing, Pricing & Margins, Financing, Troubleshooting, Reference and Legal & Policies — with a card per guide showing its title and a one-line summary of what it covers. The line under the heading counts the guides, and beside it the app shows when the guides were last synced from the repository, with the short commit they came from. If that date looks older than a feature you can see on screen, the guide set is stale rather than the feature being undocumented.

The guides are public: the Help Center opens without signing in, on purpose, because it is what a person reads before they have an account. A guide's link can be sent to a client or a prospective customer, and reading one never touches your workspace's data.

Reading a guide

A guide opens with a breadcrumb (Help › category › title), a On this page box listing its headings so you can jump straight to the part you need, and a sidebar carrying every category and every guide, so you can move between them without going back to the list. On a phone the sidebar moves above the article and the article takes the full width.

At the foot of every guide is the rule the guides live by: they are files in the repository's docs/ directory, so fixing a guide is part of fixing the feature it describes. If you find one that contradicts what the app does, that is a bug worth reporting.

Searching the guides

The search box at the top of the Help Center filters the cards as you type — no page reload, no waiting. Ctrl+K (or Cmd+K on a Mac) puts the cursor in the box from anywhere on the page, and the same shortcut is printed in the placeholder so it is discoverable.

The filter matches each guide's title, summary and keywords — not the body text. So search the way the guide is titled: deductible, tiers, margin, walkthrough. A phrase that only appears halfway down an article will not find it; a shorter, more distinctive word will. The note under the list tells you how many guides are currently being filtered out, and clearing the box brings the whole list back. If the app tells you no guides are installed in that environment, the docs directory is empty on that install rather than your search failing.

The question-mark icons inside the app

In a few places a small question mark sits beside a label. Tap it and a panel opens with a plain-language answer and a Read Guide link into the full article behind it. Today you will find them on the quote builder (How tiers are selected, Gross margin vs markup) and in Settings (Your financing portal). The tap target is a full 44 pixels even though the icon is small, because a thumb on a jobsite does not aim, and the panel closes on Escape or a tap outside.

They are documentation links, not a chat window — no one is reading the other end of them.

The ? button in the top bar

The round question-mark button next to the theme toggle in the top bar is labelled Help & Feedback. As the app stands, it opens the Pricing page in a new tab rather than the guide library. For the guides, use Help Center in the sidebar; treat that top-bar button as the route to prices.

Emailing support

Clavoz support runs on email at hello@clavoz.com — the address published on clavoz.com, and the same address Clavoz itself sends from. One reply can usually fix something that would otherwise take three, so include:

• Where you were. The page you were on when it happened, and the quote's reference (#Q-1234, the number printed at the top of the proposal) if it is about one quote.
• What you did, in order. "Opened the quote, hit Send to Client, chose email" beats "sending is broken", because it points at one step.
• What you expected and what you got. Include the exact wording of any error, and a screenshot if the problem is visual — on a phone a screenshot of the screen beats a description of it.
• Which device and browser. A 375-pixel phone and a desktop Chrome window fail in different places.
• The document itself, if the problem is with reading one. A carrier estimate that parsed badly is worth attaching, because the parser can be run against it.
• If a number looks wrong, say which number and where you read it — the quote total, a payment stage, a margin figure. Figures come from different places in the app, and naming the one that looks wrong is most of the diagnosis.

For the handful of problems that already have an answer written down — an upload that refuses, a parser flag, a proposal nobody can sign, a billing warning — start with Troubleshooting and Common Issues.