> For the complete documentation index, see [llms.txt](https://docs.quickreply.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quickreply.ai/product-modules/templates/rcs-templates/concepts/card-actions-and-suggestions-chips.md).
# Card Actions and Suggestions (Chips)
RCS templates support two kinds of interactive buttons: Card Actions and Suggestions (also called suggestion chips). Both let customers act directly from the message — reply, call, open a link, view a location, or save an event — without leaving their messaging app.
### Card Actions vs. Suggestions
Both support the same five button types with identical settings. The difference is where they appear and how many you can add:
|
| Card Actions | Suggestions (Chips) |
| ------------ | ---------------------------------------------------- | ----------------------------------------------- |
| Placement | Stacked full-width buttons at the bottom of the card | Rounded chips floating below the message bubble |
| Maximum | 4 per card | 11 per message |
| Attached to | A specific card | The whole message |
| Available on | Single Rich Card, Carousel Rich Card | Single Rich Card, Carousel Rich Card |
On a Carousel Rich Card, Card Actions belong to each individual card, while Suggestion chips are applied to the message and are not tied to any specific card — customers see them below the carousel regardless of which card they are viewing.
### Adding and Managing Buttons
Click + Add button (Card Actions) or + Add Suggestion (Suggestions) and choose one of the five button types from the dropdown:
* Quick Reply
* Website
* Call Phone
* View Location
* Create Calendar Event
Every button requires a Button Text — the label the customer sees — with a maximum of 25 characters. Buttons can be reordered using the up/down arrow controls, or removed with the delete icon.
### Button Types
#### Quick Reply
Sends a predefined reply text back to your business when tapped. Useful for capturing customer intent ("I'm interested", "Yes / No / Maybe") without the customer typing anything.
Fields:
* Reply text (required): The text sent back when tapped (max. 25 characters). Supports variables.
#### Website
Opens a URL in the customer's browser.
Fields:
* Website button text (required): Button label (max. 25 characters).
* Link Tracking: Enabled by default — tracks every click on the button.
* URL Type:
* Static — a fixed URL (max. 2,000 characters), the same for every recipient. With Static URLs, you can optionally enable Add UTM parameter to track links.
* Dynamic — the URL is personalized per recipient. The URL is prefixed with a btn\_{{1}} variable whose value is provided for each contact — for example, a unique tracking link or a personalized landing page.
Disabling Link Tracking will prompt a confirmation dialog. Turning it off also disables UTM tracking, and no click data will be recorded for that button.
#### Call Phone
Lets the customer call your business in one tap.
Fields:
* Button text (required): Button label (max. 25 characters).
* Phone Number (required): The number to dial, including country code.
#### View Location
Opens a location on the map. Once valid coordinates are entered, a Map Preview appears in the editor so you can verify the pin before submitting the template.
Fields:
* Button Text (required): Button label (max. 25 characters).
* Location Source:
* Static — a fixed location, the same for every recipient:
* Label (optional): Location name shown on the pin (e.g., "Office", "Bakery").
* Latitude (required): −90 to 90.
* Longitude (required): −180 to 180.
* Dynamic — the location is personalized per recipient, with coordinate values provided for each contact. Only the button text is configured in the template.
\
#### Create Calendar Event
Adds an event to the customer's calendar in one tap — ideal for bookings, webinars, or appointment reminders.
Fields:
* Button Text (required): Button label (max. 25 characters).
* Calendar Source:
* Static — a fixed event, the same for every recipient:
* Event Title (required)
* Description (required)
* Start Time (required): Selected via a date-and-time picker.
* End Time (required): Selected via a date-and-time picker.
* Dynamic — the event details are personalized per recipient. Only the button text is configured in the template.
\
### Static vs. Dynamic Values
Three button types — Website, View Location, and Create Calendar Event — follow the same pattern:
* Static: Values are defined once in the template and are identical for all recipients.
* Dynamic: Values are filled per recipient when the message is sent — useful for personalized links, nearest-store locations, or individual appointment times.
### How Buttons Appear to the Customer
In the delivered message:
* Card Actions render as full-width buttons stacked at the bottom of the card.
* Suggestions render as rounded chips floating below the message bubble.