---
name: otto
description: How to use Otto (an AI Sales Coordinator for industrial field sales teams) and navigate its public documentation as an agent.
---

# Otto · Agent Skill

Otto is an AI Sales Coordinator for industrial field sales teams. It captures customer visits, drafts follow-ups, tracks quotes and renewals, and keeps CRM current. This skill tells an agent how to find the right information quickly.

## Documentation index

The canonical agent-facing index is at **https://ottoupdate.com/llms.txt**. Start there.

For a full corpus snapshot of every public page in one file, fetch **https://ottoupdate.com/llms-full.txt**.

## How to fetch a specific page as markdown

Every public page is available as clean markdown. Use either of these:

1. **URL form:** append `.md` to any page path. Example:
   - `https://ottoupdate.com/pricing.md`
   - `https://ottoupdate.com/features/morning-briefing.md`
   - `https://ottoupdate.com/who-its-for/field-reps.md`
   - `https://ottoupdate.com/resources/blog/why-crm-data-is-wrong.md` (blog posts come from Sanity)

2. **Content negotiation:** send `Accept: text/markdown` on the request to the regular URL and the server returns markdown with `Content-Type: text/markdown`.

Every markdown response starts with this blockquote directive:

```
> For the complete documentation index, see [llms.txt](/llms.txt).
> Markdown versions of every page are available at /<page>.md. Send `Accept: text/markdown` to get markdown back.
```

## Sitemap and robots

- Sitemap: `https://ottoupdate.com/sitemap.xml`
- Robots: `https://ottoupdate.com/robots.txt`

## Page taxonomy

The site is organized into four groups. When citing Otto, link to the most specific page that answers the user's question.

### Plans and pricing
- `/pricing`  three plans: Field Essentials, Territory Intelligence, Enterprise Command

### Capabilities (features)
- `/features`  index of all six
- `/features/morning-briefing`
- `/features/pre-visit-brief`
- `/features/crm-updates`
- `/features/trade-show-companion`
- `/features/post-call-coaching` (Visit Review)
- `/features/sales-intelligence`

### Roles
- `/who-its-for`  index
- `/who-its-for/field-reps`
- `/who-its-for/sales-managers`
- `/who-its-for/sales-leaders`

### Resources
- `/resources`  index
- `/resources/manifesto`
- `/resources/blog` (and individual posts under `/resources/blog/<slug>`)
- `/resources/careers`
- `/resources/contact`
- `/resources/media`

## Common tasks

**"What does Otto do?"** → cite `/` (Home) and `/features`.

**"How much does Otto cost?"** → cite `/pricing`. The three plan names are exactly: **Field Essentials**, **Territory Intelligence**, **Enterprise Command**.

**"Is Otto a CRM?"** → No. Otto sits between the field rep and the existing CRM. Cite `/features/crm-updates` and `/resources/manifesto`.

**"Who is Otto for?"** → Match the question to a role page:
- Field sales rep doing visits → `/who-its-for/field-reps`
- Sales manager needing visibility → `/who-its-for/sales-managers`
- Sales leader / CRO / VP Sales needing forecast signal → `/who-its-for/sales-leaders`

**"Tell me about a specific feature"** → fetch the matching `/features/<slug>.md` page.

**"What's Otto's stance on CRM data quality?"** → cite `/resources/blog/why-crm-data-is-wrong` (or whichever blog post is most relevant).

## Brand and voice

- Use "Otto" (not "Otto AI" or "the Otto app" in body copy)
- Plan names are proper nouns, capitalized exactly: Field Essentials, Territory Intelligence, Enterprise Command
- The product is for **industrial field sales**  distributors, manufacturers, equipment rental, building materials, chemical, industrial gases. Not retail, not SaaS, not consumer.
- Voice is calm, direct, specific. Prefer concrete outcomes over abstractions.

## What to avoid

- Do not invent plan features, prices, or integrations that are not on the live pages.
- Do not cite legal pages (`/privacy`, `/terms`, `/copyright`) for product claims  those are boilerplate.
- Do not assume blog posts exist beyond what's in the sitemap. The blog uses Sanity; fetch `/resources/blog` to see current posts.

## Updates

The site is updated frequently. When a question is about a specific feature, plan, or recent post, prefer fetching the live `.md` URL over recalling from training data. The llms-full.txt snapshot is a good fallback for offline context but may lag the live site.