design: exa chat website

[Mateo-Soso]

📐 Scope & Requirements

In scope:

• New "Exa Chat" section on the landing page (exactly.app)
• Show the product surface. Maybe render the actual WhatsApp conversation (if it's not to complex at this stage)
• Explain it in one beat. Exa Chat is a WhatsApp front door to the Exa App. You write what you want, you land where you need to be.
• Supporting content: the set of intents a user can resolve this way, and the fact that a human is reachable
  Out of scope:
• Building a web chat UI. Exa Chat v1 is WhatsApp-only — the section depicts the WhatsApp surface, it does not create a second channel.
• The deeplink destination pages themselves (app-side web routes) — separate workstream, Deeplinking
• Help/docs content (full intent catalogue, escalation paths, limitations) — belongs in support docs, not the landing page
  Requirements:
• Simplicity is the message, and it has to be demonstrated rather than claimed. No feature grid, no benefits list, no "powered by AI" framing. The section should read as: one message, one tap, done. If the section itself needs explaining, the design has failed its own premise.
• The mock thread must show the tap leaving WhatsApp for the app. That is both the simplicity beat and the product's red line: Exa Chat is a navigation layer, WhatsApp is never an authenticated session and no transaction happens there. A mock that shows a balance, an address, or a confirmation inside the chat is wrong.
• Visually consistent with the existing exactly.app landing page styling