Getting started guide

Public safe

This page proves the future task-guide and reference-page pattern with fields from the PRD template.

Audience: All roles
Current limits: The guide is static review content. It does not launch a walkthrough, inspect your account, or answer with AI.

Support request boundary

Use Sev4 for documentation shape feedback; future support cases can attach page and role context. This panel does not submit a support case.

Sev1: Critical outage or data-risk emergency

Target: 1-hour response, 24/7 paging during pilot

Sev2: Major workflow blocked

Target: 4 business hours

Sev3: Standard product question or non-urgent issue

Target: 1 business day

Sev4: How-to, cosmetic, or future enhancement

Target: 2 business days

These preview controls are placeholders. Real AI answers, search, walkthroughs, and support submission come in later tickets.

Task guide placeholder

Open the Otto Guide and understand this page

A static task guide and reference-page pattern that proves how future Otto Guide articles should be structured.

Who can do it

All roles

Surface

Web and mobile

Time needed

3 minutes

Before you start

Use a local proof page such as Settings, App shell, or Marketing.
Remember that this guide is a placeholder and does not perform production search.

Steps

Step 1

Open What is this page?

Use the Help or What is this page control in the page header to see the purpose, intended audience, proof boundary, and related guide links.

Placeholder screenshot showing the contextual help panel opened from a proof page header.

Step 2

Review the related guides

Follow the local Guide links to see the future task-guide and reference-page pattern for that area.

Placeholder screenshot showing related Otto Guide links in the panel.

Step 3

Use support severity as a reference only

The support targets show the intended pilot expectation, but this proof does not submit a support request or collect school data.

Placeholder screenshot showing support severity targets without a submit action.

What happens next

Later tickets can connect real guide search, guided walkthroughs, support request submission, and AI answers grounded only in approved guides.

If something looks wrong

Treat the content as review copy. Ask Otto to update the guide data or page wiring before any production support workflow exists.

Reference page placeholder

What is this page? reference pattern

Future reference pages should explain what the screen is for, who can use it, the fields or controls on the page, permission boundaries, related tasks, and release-specific caveats.