> ## Documentation Index
> Fetch the complete documentation index at: https://docs.impellabs.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Channels

> Where conversations happen, and what each one can render.

## Available today

<CardGroup cols={2}>
  <Card title="WhatsApp" icon="whatsapp">
    Meta Cloud API. Text, images, documents, reply buttons, lists, CTA links,
    location, contacts, templates.
  </Card>

  <Card title="Website widget" icon="window">
    An embeddable panel. Renders structured blocks — cards, lists, options,
    checklists — rather than plain text.
  </Card>
</CardGroup>

Phone (voice) exists for outbound campaigns. **Instagram is not implemented**:
it appears in configuration but has no inbound or outbound path.

## What this means for your tools

Your tools are channel-agnostic — the same tool is called on every channel and
returns the same result. The platform decides how the reply is rendered.

<Warning>
  Do not return channel-specific formatting. WhatsApp has no Markdown links,
  a strict 1,024-character interactive body, and at most one interactive
  element per message. Return facts; let the platform compose.
</Warning>

## Delivery rules you inherit

<AccordionGroup>
  <Accordion title="The 24-hour window">
    Outside it, WhatsApp permits only approved templates. The platform checks
    before generating a reply — so a tool may be called in a conversation
    whose answer is then delivered late, or as a template.
  </Accordion>

  <Accordion title="Burst coalescing">
    Three quick messages become one turn, not three. Your tool sees the
    combined intent.
  </Accordion>

  <Accordion title="Human takeover">
    A person replying from the WhatsApp Business app switches the session to
    human control and the assistant stops. Tools are not called while a human
    holds the thread.
  </Accordion>
</AccordionGroup>

## Media

Voice notes are transcribed before the turn. **Images are not interpreted** —
there is no vision path, so a photo arrives as a note asking the customer to
describe what they need.

<Note>
  If your product can identify something from a photo, that is a strong case
  for a tool. Talk to us: it needs a media path on the platform side as well.
</Note>