Clear by design.
Dental by nature.

# Alta Voice — website design prompt

Use the approved September 2026 Alta Voice website and its /brand guide as the design reference. Extend this direction consistently; preserve the selected homepage composition and existing product resources.

Design for practice owners and hygiene teams. Make Alta Voice immediately recognizable as a dedicated voice assistant platform for dental practices. Show the work: a chairside conversation becoming a structured clinical note, spoken measurements entering a perio chart, and findings becoming easier to discuss with a patient. Lead with a clear benefit, demonstrate the actual workflow, answer practical questions, then offer a demo.

Always call the company and platform Alta Voice. Keep the established product names Alta Notes, Alta Voice Perio, and 3D Perio Index. Use plain, specific language. Explain customized note formats and the review/edit/copy workflow; describe perio transfer for the relevant practice software and version. Preserve exact customer quotations and attribution. Do not invent rankings, performance numbers, clinical outcomes, integrations, testimonials, or automatic transfers.

Use white #FFFFFF, Ink #0B1020, secondary text #3D4A5C, Mist #F5F7FB, and borders #E2E8F0. Glacier #99FFFF is light and emphasis, never body text. Reserve the 135-degree #6C8CFF to #2DD4BF gradient for restrained underlines, button edges, and ambient light. Keep letterforms solid Ink. Preserve the original colors within product recordings and screenshots.

Use the production system font stack: -apple-system, BlinkMacSystemFont, "Segoe UI", "Inter", Roboto, Helvetica, Arial, sans-serif. Do not introduce a font download. Display weight is 450, with close tracking and natural line breaks. Use fluid desktop H1 sizes around 52–82px, section headings around 37–60px, and body copy around 17px. On phones, adapt display type to 45–53px and body copy to 15–17px. Keep long-form readers comfortably readable at 18–19px.

Work within a 1184px content width, with generous 48px desktop and 20px mobile gutters. Give sections approximately 120px desktop, 85px tablet, and 68px mobile vertical space. Alternate spacious editorial compositions, readable product frames, and human proof. Avoid a repetitive wall of cards. Product frames use restrained borders, soft shadows, and roughly 11–18px corners. Primary calls to action are Ink pills with white text, a 550ms gradient edge sweep, and a subtle arrow shift. Supporting links are quiet and explicit.

Preserve the subtle hero dot grid and quiet alpine atmosphere. Use slow, low-contrast Glacier light around the 3D Perio Index. Keep closing sections calm. Do not add decorative waveform divider strips. Motion should clarify a state or focus attention on the product: no competing loops, scroll hijacking, or moving text. Honor reduced-motion and data-saving preferences. Product clips are silent, play once on visibility, pause offscreen, and offer controls. Sound starts only after a deliberate action.

Use real, readable product captures and permissioned customer material. Label edited recordings and demo data accurately. Never label prerecorded material as live. Do not fabricate software UI or imply separate chart/model/report examples are the same clinical case. Use enlargement for dense captures. Human photography should feel candid, bright, and clinically credible; landscape imagery supplies atmosphere rather than product evidence.

Carry the same typography, spacing, palette, navigation, and footer through Home, Notes, Perio, Demo, Blog, article readers, Partners, profiles, Contact, Webinars, episode readers, legal pages, and Brand. Use semantic headings, keyboard access, visible focus, clear errors, responsive layouts, and stable image dimensions. Treat 44px touch targets and WCAG AA contrast as delivery targets, and verify them rather than claiming compliance from appearance.

For the demo journey, aim for choosing a time, entering details once, and confirming one booking on the page. Do not add a separate lead form without a specific business requirement. Preserve routing, partner attribution, consent, CRM ownership, and confirmation behavior when the chosen booking configuration is implemented. Keep the approved design distinct from unresolved integration decisions.

Deliver responsive implementation and a concise record of changes, validation, and remaining launch dependencies. Keep prior versions available. Premium means clear hierarchy, credible product proof, deliberate spacing, and reliable interactions.