Skip to content

Buttons, forms and cards

Send quick replies, short forms and product or link cards in the chat, from your team, GiovBot and Copilot, and see how they appear on each channel.

On this page

Messages in the chat can carry more than text. Under a reply, visitors can see:

BlockWhat the visitor does
Quick repliesTaps a button instead of typing. The button's text is sent as their message.
FormFills in a few fields, such as their name, email or an order number, and sends them once.
CardSees a product, offer or page with its image, title and price, and opens it. Several cards show as a row they can scroll.
SourcesOpens the help page an answer came from.

The text of the message always stays readable on its own. Wherever buttons or cards can't be shown, the visitor gets that text and a plain version of the blocks instead.

Buttons, links and highlights take your widget colour from Settings → Chat widget. On light colours, such as yellow, the text on them turns dark so it stays readable.

Send them from the inbox

In a conversation, choose Insert in the reply box, then:

  • Quick replies: add 2 to 6 short options.
  • Form: start from Contact details, Order lookup or Booking, or build a Custom form. Each field has a type (text, email, phone, number, date, long text or a choice list) and can be required.
  • Card: paste a link. The title, description and image are filled in from the page, and you can change them or add a price.

What you insert appears above the reply box. A message with buttons, a form or a card needs some text too, so a short line is filled in for you to edit.

Forms work in the website chat only, so Form appears only in website conversations.

Forms and answers

A visitor answers a form once. Their answers appear in the conversation as their message, and the form shows as Answered. Name, email and phone answers from the Contact details form are also saved to the visitor and their contact, like details they type. GiovBot's forms save them the same way when it asks for contact details.

GiovBot

GiovBot uses these blocks on its own when they help. Each one is a switch in GiovBot → your agent → Tools → System tools, and all four are on for every agent until you turn them off:

SwitchWhat GiovBot does
Suggested repliesShows 2 to 6 buttons when the visitor has to pick one of a few clear options, such as a size or a plan.
Forms in chatAsks for details it needs, such as contact details or an order number, with a short form in the website chat instead of in a message.
Result cardsShows the products, orders or bookings one of your tools returned as cards.
Show sourcesLinks the pages of your website the answer came from.

GiovBot never makes up what goes on a card. A card keeps only the titles, prices, links and images that appear in your tool's result. Sources link only pages from your own website knowledge that matched the question well, never documents or external references.

Your content guardrails check the text of buttons and forms as well as the message.

GiovCopilot

In your product, Copilot can also offer a few tappable follow-ups when you need to choose, and show the records an action returned as cards. These come from the same checks: cards hold only what the action returned.

On other channels

ChannelQuick repliesCardsForms
Website chatButtonsCards and rows of cardsForm
WhatsAppUp to 3 buttons, or a list of up to 10An image with its details as the caption, or text when the card has no imageThe questions, as text
Messenger and InstagramQuick replies (up to 13)Swipeable cards (up to 10)The questions, as text
TelegramA numbered listA photo with its details as the caption, or text when the card has no imageThe questions, as text
EmailA numbered listTitle, price and linkThe questions, as text

A link on its own becomes a button where the app supports one. When a visitor taps a button in WhatsApp, Messenger or Instagram, its text reaches the conversation as their message, and GiovBot answers it like any other.

Note

The mobile SDKs show the message text for now. Buttons, forms and cards will follow in a later SDK release.

Loading…