Skip to main content
Message blocks are how your Flow talks to contacts. Choose the right interactive pattern, keep media inside channel limits, and prefer Omnichannel content when you can.

​
Message blocks

Prefer Omnichannel message types for multi-channel Flows. Switch to channel-specific content only when you need a native control (lists, product cards, etc.).

​
Interactive patterns

Best for menus and short decisions. Keep labels short. Each option should continue to a clear next block. After the contact taps, quick replies typically disappear from the thread.
Use for richer choices with imagery or multiple CTAs. Respect per-channel button caps (often up to 3 buttons per card on Meta channels). Link buttons can open URLs; postback-style buttons continue the Flow.
If the channel or context has no buttons (for example SMS), ask numbered replies (Reply 1 for Sales) and branch with a Condition.

​
Send a business location

On WhatsApp, Telegram, and Viber you can send a location card with your business coordinates so contacts can open maps.
  1. Add the location / map message type for that channel (or Omnichannel where supported).
  2. Set latitude, longitude, and an optional label.
  3. Publish and test on a real device.
To collect the contact’s location instead, see Request location.

​
Media formats and sizes

Fliqr AI also enforces a general 25MB upload ceiling in many surfaces. Channel networks may be stricter.
Large gallery or video files often fail above 25MB. Host oversized media on HTTPS and send the link instead of uploading the file into the Flow.

​
Personalization in messages

Use {{field_name}} placeholders. Example: Thanks {{first_name}} — we booked you for {{appointment_slot}}. Guard empty fields with a Condition, or set field defaults under Contacts.

​
Next

Collect data

Ask questions and store answers.

Dynamic choices

Build multiple-choice options from an API or sheet.