# 68 Rapid Response

**Philosophy and fit.** Put the next practical step within a thumb’s reach. Built for locksmith, emergency plumbing, restoration, urgent repair. The visitor’s next step is to request urgent help.

**Visual grammar.** Use a mobile-first navy and amber dispatch card with an immediate decision. Preserve the hierarchy of urgent or routine, service coverage, immediate contact; these patterns solve this business’s actual decision, rather than supplying interchangeable decoration.

**Sample and interaction.** NOW / Home repairs is a fictional demonstration. The entry page establishes a complete visual direction, with check coverage and request assistance as supporting states. Inputs use local deterministic fixtures; no request, order, application or payment is sent.

**Responsive behaviour.** On a phone, keep the primary decision first, stack facts with explicit labels, preserve the order of the workflow, and provide comfortably sized controls. Wide diagrams scale; tabular facts retain their labels.

**Adaptation.** Replace the fictional brand, prices, availability, qualifications and claims with verified client information. Preserve urgent or routine, service coverage, immediate contact. Use imagery to explain the place, people, work or product, with deliberate crops and honest captions. Do not turn this into a generic hero-and-card layout.

## Commercial and content patterns

- Urgent or routine
- Service coverage
- Immediate contact

## Routes

- Entry: /preview/68-rapid-response/start
- Check coverage: /preview/68-rapid-response/help
- Request assistance: /preview/68-rapid-response/request

## Reference and adaptation

- Page scope: One page.
- Distinct composition: mobile-first navy and amber dispatch card with an immediate decision.
- Typography: DM Sans.
- Tokens: page #f5f4ec, ink #233448, accent #ffcf58.
- Put the phone number and urgent-versus-routine decision within immediate reach. Avoid large images or promotional blocks before those actions; coverage and contact details belong directly in the request flow.
- Use the native inputs and labelled states in Demo.vue as interaction references. Replace local fixtures with real validation, availability and backend behaviour in the destination application.

## Assets

All brands and fixture data are fictional. Original SVG diagrams are source-native. Commercial photos are illustrative and are documented in [asset provenance](../../../docs/COMMERCIAL_ASSETS.md); do not present them as evidence of a real business or rename a stock subject as actual staff. See the public commercial asset manifest for URLs, checksums and cropping guidance.