Zendesk — AI-Powered Customer Service Platform

# Build brief — an original marketing website in the taste of Zendesk

> Reference: https://www.zendesk.com · UIDiscovery: https://uidiscovery.com/sites/zendesk · captured 2026-09-21 at a 1440px desktop viewport (+ 390px iPhone shots) · [full page](https://uidiscovery.com/media/captures/zendesk/full.webp) · [scroll video](https://uidiscovery.com/media/captures/zendesk/preview.mp4)

## 1. Goal
Build an original marketing website for **[the user's brand]** that feels as considered as Zendesk — same structure, rhythm and polish, entirely new identity and content.

## 2. Originality rules
- Build an ORIGINAL design for the user's own brand in the same *taste* as Zendesk: structure, rhythm, hierarchy, palette mood and type pairing.
- Never reuse Zendesk's logo, name, product imagery, illustrations, icons, screenshots or copy. Write new copy for the user's product.
- If the user hasn't said what their product is, ask first (or use clearly marked placeholders like [Brand], [Product], [Audience]).
- Reference screenshots are for looking at, not for embedding or tracing.

## 3. The taste, in short
- Zendesk (zendesk.com): AI marketing website, light.
- 12 sections: Logo cloud → Features → Content → Features → Blog → Content → Call to action → Footer.
- Spacing: about a screen per idea (median section ≈692px).
- Type: one family (Vanilla Sans). Imagery: mostly typography with little or no imagery.

## 4. Page structure (top to bottom)

### 1. Logo cloud — borrow trust from recognisable customers or partners.
- Layout: a single row or wall of monochrome marks with a one-line lead-in. Compact band (224px at 1440), page background; 8 images/icons (a set of cards or a small gallery); no interactive controls.
- Slots: One-line lead-in (e.g. “Trusted by…”); 6–10 monochrome customer/partner marks (your own, with permission).
- Topic (tone/length only — never reuse): “22,000+ SERVICE TEAMS TRUST ZENDESK AI”
- [Screenshot](https://uidiscovery.com/media/captures/zendesk/s-01.webp)

### 2. Features — explain the key benefits, grouped so each can be scanned in seconds.
- Layout: section title over a grid or alternating rows of benefit items. Tall, ≈1.9 screens (1700px at 1440), page background; 1 image/graphic; 1 text link instead of buttons; 4 headings → ~3 items under a title.
- Slots: Section title (~7 words, like the reference); 3 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “AI that gets smarter with every resolution.”
- [Screenshot](https://uidiscovery.com/media/captures/zendesk/s-02.webp)

### 3. Features — explain the key benefits, grouped so each can be scanned in seconds.
- Layout: section title over a grid or alternating rows of benefit items. Half to one screen (580px at 1440), page background; 3 image/graphics; 2 text links instead of buttons.
- Slots: Section title (~6 words, like the reference); 3 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “Self‑improving AI Agents on any platform”
- [Screenshot](https://uidiscovery.com/media/captures/zendesk/s-03.webp) · imagery: slot 1

### 4. Features — explain the key benefits, grouped so each can be scanned in seconds.
- Layout: section title over a grid or alternating rows of benefit items. Half to one screen (448px at 1440), page background; 3 image/graphics; 1 text link instead of buttons.
- Slots: Section title (~14 words, like the reference); 3 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “Zendesk’s partnership with the Golden State Warriors, Valkyries, and Chase…”
- [Screenshot](https://uidiscovery.com/media/captures/zendesk/s-04.webp) · imagery: slot 1

### 5. Features — explain the key benefits, grouped so each can be scanned in seconds.
- Layout: section title over a grid or alternating rows of benefit items. About one full screen (1023px at 1440), page background; 22 image elements (icons, logos, product UI — not 22 photos); 5 buttons (tabs, toggles or per-card actions); 6 headings → ~5 items under a title.
- Slots: Section title (~5 words, like the reference); 5 items: icon or visual + short title + 1–2 line description; Primary + secondary action.
- Topic (tone/length only — never reuse): “Designed for AI-first customer service”
- [Screenshot](https://uidiscovery.com/media/captures/zendesk/s-05.webp) · imagery: slot 1

### 6. Features — explain the key benefits, grouped so each can be scanned in seconds.
- Layout: section title over a grid or alternating rows of benefit items. About one full screen (926px at 1440), page background; 2 image/graphics; 4 text links instead of buttons; 3 headings → ~2 items under a title.
- Slots: Section title (~10 words, like the reference); 2 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “Extend the power of AI-first service across your entire organization.”
- [Screenshot](https://uidiscovery.com/media/captures/zendesk/s-06.webp)

### 7. Content — supporting content that deepens one idea.
- Layout: text + media block. About one full screen (885px at 1440), page background; 29 image elements (icons, logos, product UI — not 29 photos); 6 buttons (tabs, toggles or per-card actions).
- Slots: Heading (~6 words, like the reference); Body copy; Supporting visual (see image plan); Primary + secondary action.
- Topic (tone/length only — never reuse): “Built for businesses of all sizes”
- [Screenshot](https://uidiscovery.com/media/captures/zendesk/s-07.webp)

### 8. Features — explain the key benefits, grouped so each can be scanned in seconds.
- Layout: section title over a grid or alternating rows of benefit items. Half to one screen (536px at 1440), page background; 2 image/graphics; 1 text link instead of buttons.
- Slots: Section title (~5 words, like the reference); 2 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “Connect your ecosystem. Your way.”
- [Screenshot](https://uidiscovery.com/media/captures/zendesk/s-08.webp)

### 9. Blog — signal an active, credible team through recent writing.
- Layout: 3-up card grid: image, title, meta. Half to one screen (692px at 1440), page background; 15 images/icons (a set of cards or a small gallery); primary + secondary button.
- Slots: Title + “All posts” link; 3 post cards: cover image, title, date/author.
- Topic (tone/length only — never reuse): “Additional resources”
- [Screenshot](https://uidiscovery.com/media/captures/zendesk/s-09.webp)

### 10. Content — supporting content that deepens one idea.
- Layout: text + media block. Half to one screen (423px at 1440), page background; no images (type-led); 2 text links instead of buttons.
- Slots: Heading (~5 words, like the reference); Body copy; Text link action.
- Topic (tone/length only — never reuse): “Pricing built for your success”
- [Screenshot](https://uidiscovery.com/media/captures/zendesk/s-10.webp)

### 11. Call to action — close the page with one clear next step.
- Layout: short headline + one primary action on a contrasting band. Compact band (296px at 1440), own dark band #203524; no images (type-led); 2 text links instead of buttons.
- Slots: Headline (~6 words, like the reference); One sentence of support; Text link action.
- Topic (tone/length only — never reuse): “Launch your first AI agent today”
- [Screenshot](https://uidiscovery.com/media/captures/zendesk/s-11.webp)

### 12. Footer — navigation, legal and contact — the page's index.
- Layout: multi-column link groups, brand line, legal row. Half to one screen (735px at 1440), own dark band #11110d; 40 image elements (icons, logos, product UI — not 40 photos); 6 buttons (tabs, toggles or per-card actions), 133 links (link lists / navigation).
- Slots: Brand mark + one-line description; 3–5 link columns; Newsletter or contact (optional); Legal row + social icons.
- Topic (tone/length only — never reuse): “Footer”
- [Screenshot](https://uidiscovery.com/media/captures/zendesk/s-12.webp)

Inner pages also captured (Pricing, Product, Customers, About, Sign up, Log in, Blog, Enterprise, Contact, Security): https://uidiscovery.com/sites/zendesk?view=pages

## 5. Design system
### Colour
| Role | Hex | Use | Contrast on background |
|---|---|---|---|
| background | `#ffffff` | page background | — |
| foreground | `#11110d` | body text, headings | 18.9:1 |
| accent | `#203524` | primary buttons, links, highlights — sparingly | 13.2:1 |
| surface | `#f5f5f2` | cards, inputs, alternate bands | text on it 17.3:1 |
| muted | `#d1f470` | secondary text, borders | 1.2:1 — borders / large text only |

Captured palette: `#ffffff` `#11110d` `#d1f470` `#f5f5f2` `#203524`. Section bands top→bottom: `#ffffff` → `#203524` → `#11110d`. Roles are assigned automatically — sanity-check them against the screenshot. Keep the palette's *mood* (light, natural, earthy) and proportions; swap the accent for the user's brand colour.

### Tokens
```css
:root {
  --background: #ffffff;
  --foreground: #11110d;
  --accent: #203524;
  --surface: #f5f5f2;
  --muted: #d1f470;
  --font-heading: "Inter", ui-sans-serif, system-ui, sans-serif;
  --font-body: "Inter", ui-sans-serif, system-ui, sans-serif;
  --radius: 12px; /* calibrate from the screenshot */
}

/* Tailwind v4 — in globals.css after @import "tailwindcss"; */
@theme {
  --color-background: var(--background);
  --color-foreground: var(--foreground);
  --color-accent: var(--accent);
  --color-surface: var(--surface);
  --color-muted: var(--muted);
  --font-heading: var(--font-heading);
  --font-sans: var(--font-body);
}
```

### Typography
- Headings: **Inter** (Google Fonts) — reference uses Vanilla Sans. “Vanilla Sans” is likely a custom or licensed face. Inter is a neutral stand-in — pick a closer free match by eye from the screenshot.
- Body: same family — a single-family system; create contrast with size and weight, not a second face.
- Scale (starting point, sizes weren't measured — calibrate against the 1440px screenshot): display clamp(2.5rem, 5vw, 4.25rem), h2 clamp(1.75rem, 3vw, 2.5rem), h3 1.25rem, body 1rem–1.125rem / 1.6, small 0.875rem. Headings: tight tracking (-0.02em), line-height 1.05–1.15.

### Spacing & rhythm
Sections run ≈692px tall at 1440 (median; range 224–1700px, captures cap at 1700px) — roughly a screen per idea. Start with 96–120px vertical padding per section on desktop and about two-thirds of that on mobile. The background changes 2 times down the page — use band changes to mark chapters. 8px spacing grid, 1200–1280px max content width, 24px (mobile) / 32–48px (desktop) gutters.

### Shape, depth & theme
Radii and shadows weren't measured. Read exact corner radius, border and shadow treatment from the screenshots. Light-first; for a dark mode use a near-black (not #000) background, ~90% white text, lift surfaces with lightness not shadow, re-check the accent.

## 6. Imagery plan

Measured from 6 section screenshots: mostly **typography with little or no imagery** (light, natural, earthy, AI). Still glance at the linked screenshots to match the exact mood.

### Slot 1 · 3. Features, 4. Features, 5. Features → product UI (uncertain)
- AI sections with many image elements — most likely product UI screenshots/mockups plus icons. Count: one consistent treatment across these sections. Aspect: 4:3. Look first: [ref 1](https://uidiscovery.com/media/captures/zendesk/s-03.webp) [ref 2](https://uidiscovery.com/media/captures/zendesk/s-04.webp) [ref 3](https://uidiscovery.com/media/captures/zendesk/s-05.webp)
- **Stock** — “laptop blank screen minimal desk”: [Unsplash](https://unsplash.com/s/photos/laptop-blank-screen-minimal-desk?orientation=landscape) · [Pexels](https://www.pexels.com/search/laptop%20blank%20screen%20minimal%20desk/?orientation=landscape) · [Pixabay](https://pixabay.com/images/search/laptop%20blank%20screen%20minimal%20desk/?orientation=horizontal)
- **Generate** — `Product-shot backdrop for a UI screenshot: smooth light gradient from #ffffff to #f5f5f2 with a soft #203524 glow behind the centre, subtle floor shadow, empty centre area where a screenshot will be placed. Lighting: soft natural daylight, airy and high-key. Aspect ratio 4:3. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people. No UI elements.`
- Build the UI itself in HTML/CSS with realistic sample data from YOUR product (or screenshot your real app). Don't generate UI as an image and don't reuse the reference's screenshots. Stock/AI is only for the backdrop or device frame.

- **Logos** — 1. Logo cloud: Never generate or stock-source logos. Use your real customers'/partners' marks with permission (monochrome, equal height), or neutral wordmark placeholders until you have them. Integration icons: each tool's official brand kit (Simple Icons is a quick start; trademarks still apply).
- **No imagery (type-led)** — 2. Features, 6. Features, 7. Content, 8. Features, 9. Blog, 10. Content, 11. Call to action: No imagery needed — type, spacing and colour do the work. If the screenshot shows a background graphic, rebuild it in CSS (gradient, grid, noise) or a short muted video, not a stock photo.
- **Icons** — 12. Footer: Use one open-source icon set at one stroke weight — Lucide, Phosphor or Heroicons (MIT) — tinted with the text or accent token. Social icons: Simple Icons.

### If the screenshots show a different style
Open the refs first and name what you actually see (photo / product UI / illustration / abstract gradient or 3D / type only). If it differs from the guess, switch routes — UI is built in code, type-only needs no image, otherwise:
- **photography** — generate `Photograph: abstract gradient mesh. Composition: wide shot, subject off-centre to one side, generous clean negative space for the headline. Lighting: soft natural daylight, airy and high-key. Natural, earthy colour grade that sits on #ffffff, #203524, #f5f5f2. Photorealistic, natural textures, shallow depth of field, 35mm lens. Aspect ratio 3:2. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.` · stock: [“abstract gradient mesh” on Unsplash](https://unsplash.com/s/photos/abstract-gradient-mesh?orientation=landscape) (same query works on Pexels/Pixabay)
- **abstract 3D / gradient** — generate `Abstract 3D render: soft, matte clay shapes and a smooth gradient in #203524 and #d1f470 on a #ffffff background. Lighting: soft natural daylight, airy and high-key; natural, earthy tone. Minimal and calm, generous negative space on one side for text. Aspect ratio 3:2. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.` · stock: [“abstract gradient 3d” on Unsplash](https://unsplash.com/s/photos/abstract-gradient-3d?orientation=landscape) (same query works on Pexels/Pixabay)
- **illustration** — generate `Flat vector illustration: abstract gradient mesh, friendly simplified shapes, limited palette of #ffffff, #203524, #f5f5f2 plus one soft neutral, plenty of empty background, consistent line weight, natural, earthy mood. Aspect ratio 3:2. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.` · stock: [“technology flat illustration” on Unsplash](https://unsplash.com/s/photos/technology-flat-illustration?orientation=landscape) (same query works on Pexels/Pixabay)

- **Licences:** Unsplash and Pexels images are free for commercial use under their own licences; Pixabay under the Pixabay Content License. Check each image's page before use, credit the photographer when asked (good practice anyway), and skip images showing logos, trademarks, branded products or identifiable people without a release.
- **AI generation:** the prompts work with any image model (GPT Image, Imagen, Flux, Midjourney, Firefly, SDXL…) — check its commercial-use terms. Never put the reference brand's name or “in the style of <brand>” in a prompt.
- **Never** download, trace or re-host the reference's own images, illustrations, product shots or logos.

## 7. Build steps
1. Confirm brand, product, audience and the primary action with the user.
2. Set up the tokens (CSS variables / Tailwind @theme) and load the fonts.
3. Build the sections in order, mobile-first, with each reference screenshot open.
4. Write original copy for every slot — match length and tone, never the words.
5. Source every image via the imagery plan (stock or generated); compress it and record credits.
6. Run the checklist at 390 / 768 / 1440px and fix what fails.

## 8. Acceptance checklist
- [ ] Responsive at 390px, 768px and 1440px — no horizontal scroll, tap targets ≥ 44px on mobile.
- [ ] Colour contrast WCAG AA: 4.5:1 body text, 3:1 large text and UI; visible focus states; full keyboard navigation.
- [ ] Semantic HTML: one <h1>, ordered headings, landmarks (header/nav/main/footer), labelled form fields, alt text on meaningful images.
- [ ] Performance: modern image formats with width/height set, lazy-load below the fold, ≤ 2 font families with font-display: swap, LCP < 2.5s.
- [ ] prefers-reduced-motion respected; animations under ~300ms and never blocking content.
- [ ] Originality: no copied logos, images, illustrations or copy from the reference; every image licensed or generated; credits recorded.

## 9. If you use Next.js + Tailwind
Paste the @theme block into globals.css, load fonts with next/font/google, make each section a server component in components/sections/, use next/image with explicit sizes, and keep client components for interactive bits only (menus, toggles, accordions).

---
More: tokens https://uidiscovery.com/api/v1/sites/zendesk/tokens · kit https://uidiscovery.com/api/v1/sites/zendesk/kit · MCP `get_design_brief({ slug: "zendesk" })`, `get_image_plan({ slug: "zendesk" })`. Cite the reference as https://uidiscovery.com/sites/zendesk.