> For the complete documentation index, see [llms.txt](https://klassdocs.gitbook.io/klassapp-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://klassdocs.gitbook.io/klassapp-documentation/design/system/components/brand/whatsappmark.prompt.md).

# WhatsAppMark.prompt

The official WhatsApp mark — KlassApp's core channel; use it wherever a message, link or parent contact is WhatsApp-delivered.

```jsx
<span style={{ display: 'inline-flex', alignItems: 'center', gap: 8 }}>
  <WhatsAppMark style={{ width: 18, height: 18 }} /> Linked to WhatsApp
</span>
<WhatsAppMark decorative={false} style={{ width: 32, height: 32 }} />
```

### Rules

* The SVG has no intrinsic size — always set width/height (16–20px inline, 24–32px in a tool chip, 40px+ in a connect card).
* **Never recolour.** #25D366 and the white glyph are WhatsApp's, not ours. The same applies to `SlackMark` and `GoogleDriveMark`.
* `decorative` defaults to true (`aria-hidden`). Pass `decorative={false}` only when the mark is the sole label for the control.
* Don't substitute a generic chat bubble icon for WhatsApp. Conversely, `KpiCard icon="whatsapp"` is a *generic* outline bubble — that one is a metric glyph, not the brand.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://klassdocs.gitbook.io/klassapp-documentation/design/system/components/brand/whatsappmark.prompt.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.