# Rocky Public Copy Guardrails

This guide applies to customer-facing copy in `app/` and `components/`.

## Voice

- Sound like a strong local vending company.
- Lead with customer outcomes: service, speed, support, placement, reliability.
- Keep it plainspoken, confident, and easy to scan.
- Write like Rocky Mountain Vending is talking to a business owner, property manager, school, or office admin.

## Do Say

- What we do
- Who it is for
- What happens next
- How quickly we respond
- Why businesses trust Rocky

Examples:

- `Tell us what you need and our team will follow up quickly.`
- `Need service, moving help, or machine sales support? We’re here to help.`
- `Share your location details and we’ll recommend the right machine mix.`

## Never Say

Do not let customer-facing copy explain the website, UI, or refactor work.

Avoid phrases like:

- `rest of the site`
- `design system`
- `presentation`
- `shell`
- `dedicated page`
- `intake`
- `handoff`
- `path`
- `popup`
- `embed`
- `this page now`
- `consistent service experience`
- `best next step`
- `fuller request`
- `fuller intake`

## Before / After

- Bad: `We built this page to feel like the rest of the site: clear, calm, and easy to scan.`
- Good: `See why Utah businesses trust Rocky Mountain Vending for dependable service and support.`

- Bad: `Open the Rocky placement popup and we’ll follow up within one business day.`
- Good: `Tell us about your location and we’ll follow up within one business day.`

- Bad: `This page now matches the rest of the site instead of feeling like a separate design system.`
- Good: `Browse the machines we use, the features we prioritize, and the support that comes with every installation.`

## Review Rule

If a sentence explains how the site is organized instead of why a customer should care, rewrite it.