> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chatsyncs.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Quick Actions
> Quick Actions is a settings hub in Chatbot Manager → Automation that lists ChatSyncs's 9 System Default Action Buttons — built-in triggers tied to system events (a customer tapping WhatsApp's own Get Started button, sharing a location, sending an unrecognized message) or to buttons you place yourself (Unsubscribe, Chat with Human, and others). Instead of building automation from scratch, you wire a flow to the event ChatSyncs already recognizes.
**Chatbot Manager → Automation → Quick Actions** opens all 9 System Default Action Buttons as tiles:
**Get-started**, **No Match**, **Location Reply**, **Un-subscribe**, **Re-subscribe**, **Chat
with Human**, **Chat with Bot**, **Confirm Order**, and **Cancel Order**.
**Get-started**, **No Match**, and **Location Reply** fire automatically from a system event —
click their tile to build the flow that runs when that event happens. The other 6
(**Un-subscribe**, **Re-subscribe**, **Chat with Human**, **Chat with Bot**, **Confirm Order**,
**Cancel Order**) only run when you add them as the action on a button **inside an Interactive
Message block** — they can't be added to a Text, Image, or other message block.
## General Settings
To use the **Get-started** and **No Match** actions, first go to **Bot Settings → Settings →
General** and turn their **Enable** toggle **ON**. **Chat with Human** doesn't have a toggle —
it works as soon as you fill in the **Chat with Human Email** field below.
If the **Enable** toggle for Get Started Message or No Match Reply is turned **OFF**, the
matching action button will not work.
Click the **Bot Settings** button.
Open the **Settings** page.
It's the first tab, selected by default.
See the table below.
Click **Publish Changes** — a confirmation banner confirms it.
| Field | What it does |
| ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| **Chat with Human Email** | The email address notified whenever a customer requests **Chat with Human**. |
| **No Match Reply** | Enable/disable the bot's automatic reply when it can't match the customer's message to any automation. |
| **No Match Response Frequency Limit** | How often the No Match reply is sent to the same customer: **Every Time**, **Once a Day**, **Once a Month**, or **Once a Year**. |
| **Bot Replies While Agent on Mobile App** | Whether the bot keeps replying while a live agent is handling the chat from the mobile app. |
| **Get Started Message** | Enable/disable the **Get-started** action button. Must be **on** before the Get-started flow will run. |
| **Get Started Message Frequency Limit** | How often the Get Started message is sent to the same customer: **Every Time** or **Once a Day**. |
Disable **Bot Replies While Agent on Mobile App** so the bot and a live agent don't reply to the
same customer at the same time.
## Get-started
When someone opens a chat with your WhatsApp number for the very first time — say, they found
your number on your website and tapped it to open WhatsApp — they haven't sent you a message
yet, so WhatsApp shows a green **Get Started** button on the chat screen instead of a normal
text box. This button is built into WhatsApp itself, not something ChatSyncs adds. The
**Get-started** action fires the moment that customer taps it.
**Get Started Message** must be enabled in General Settings (above) before this button will
trigger anything.
In **Quick Actions**, click **Get-started** to open its **Configure Reference** panel.
e.g. `Get-started` — just for your own reference in the flow list.
Add/remove a [label](/learn/whatsapp-subscriber-manager#create-a-label), subscribe/unsubscribe
the contact from a [Follow-up Sequence](/learn/whatsapp-sequence), or assign the conversation
to a team or team member.
Click **Save** — this opens the flow canvas, with a **Start Bot Flow** block already set to fire on Get-started.
Connect a Text Message (or any other block) after **Start Bot Flow**.
Click **Save** to publish it.
**Example** — a welcome message personalized with a custom-field variable:
| | |
| -------- | ---------------------------------------------------------------------------------------------------------------------------- |
| Customer | *opens a chat with your number for the first time and taps the green Get Started button* |
| Bot | "Hi #LEAD\_USER\_FIRST\_NAME#, We are delighted to have you on board for your interest. If you have a question, we will do…" |
Type `#` inside a Text Message to insert a custom field as a variable — `#LEAD_USER_FIRST_NAME#`
inserts the customer's first name automatically.
## No Match
The **No Match** button fires whenever a customer's message doesn't match any keyword, intent,
or automation. Click its tile, then build the fallback reply the same way:
It's already connected to the No Match trigger.
Replace the default text with something specific to your business, e.g. "Hello! We
couldn't understand your request. Please select one of the available options below or
rephrase your question."
e.g. Interactive Message, AI Reply, Human Support, or any other automation block.
Click **Save** to publish the flow.
The **No Match Response Frequency Limit** (in General Settings above) controls how often
the same customer receives this fallback — pick **Once a Day** or longer to avoid sending it
repeatedly to someone who keeps sending unrecognized messages.
## Location Reply
The **Location Reply** button fires automatically whenever a customer shares their live
location or a location pin — no toggle to enable, just build the flow:
**Example:**
| | |
| -------- | -------------------------------------------------------------------------------------------- |
| Customer | *shares a location* |
| Bot | "Thank you for sharing your location. Our team has received it and will assist you shortly." |
## Un-subscribe & Re-subscribe
Unlike the three buttons above, **Un-subscribe** and **Re-subscribe** aren't standalone triggers
— they're button actions you add **inside an Interactive Message** block.
Open **Keyword Replies** and create a new flow (or open an existing one) — this is the flow the
Interactive Message and its button will live in.
Drag it onto the canvas and connect it to your flow.
Open the Interactive Message block and click **Add Button**.
e.g. **Static**, title `Unsubscribe`.
Under **When user presses the button**, select **System Default Action Button**.
Choose **Unsubscribe** (or **Re-subscribe**) from the Action Type list.
Connect the button to any follow-up flow (e.g. a confirmation message), then click **Save**.
**Unsubscribe** stops sequences and broadcasts for that contact. **Re-subscribe** is its mirror
— it re-adds the contact to the sequences/broadcasts they'd opted out of, configured the exact
same way except for choosing **Re-subscribe** as the Action Type.
These same steps work for every other System Default Action Button — **Get Started**, **No
Match**, **Location Reply**, **Chat with Human**, **Chat with Bot**, **Confirm Order**, and
**Cancel Order** — just select the matching Action Type instead of Unsubscribe.
## Chat with Human
The **Chat with Human** button lets a customer request a live agent. ChatSyncs emails the
address set as **Chat with Human Email** in General Settings and starts the Chat with
Human flow.
Build the flow with an **Actions** block selecting the **Chat With Human Template**, connected
to **Start Bot Flow**, then an Interactive Message thanking the customer with a button to switch
back to the bot (configured as a **System Default Action Button** → **Chat with Bot**):
## Chat with Bot
The **Chat with Bot** button is the reverse — it lets a customer who's talking to a live agent
switch back to automated replies. Build it the same way: **Actions** block selecting the **Chat
With Robot Template**, connected to **Start Bot Flow**, then an Interactive Message welcoming
the customer back with a button to switch to a human agent again (**System Default Action
Button** → **Chat with Human**):
## Confirm Order & Cancel Order
**Confirm Order** and **Cancel Order** are system default action buttons for **eCommerce
integrations only** — they fire from order events on a connected **Shopify** or **WooCommerce**
store, not from a normal chatbot conversation.
**Confirm Order** works the same way, triggered when the customer confirms instead of cancels.
If your store isn't on Shopify or WooCommerce, you don't need to configure either button.
## Frequently asked
Add an Interactive Message block with a button, set **When user presses the button** to
**System Default Action Button**, choose **Unsubscribe** as the Action Type, then connect
and save. See [Un-subscribe & Re-subscribe](#un-subscribe-re-subscribe) above.
**Bot Settings → Settings → General → Chat with Human Email.** Every Chat with Human
request emails that address.
Check that **Get Started Message** is enabled in **Bot Settings → Settings → General** —
the Get-started action button does nothing while that toggle is off.
Get-started, No Match, and Location Reply trigger automatically from a system event — you
build a flow directly off their tile. The rest (Unsubscribe, Re-subscribe, Chat with Human,
Chat with Bot, Confirm Order, Cancel Order) only run when added as a button's action inside
an Interactive Message block.
No — they're only triggered by order events from a connected Shopify or WooCommerce store
and aren't meant for regular chatbot flows.
* **Get-started silently does nothing** if **Get Started Message** is disabled in General
Settings — enable it first.
* **No Match needs No Match Reply enabled** in General Settings, or the fallback never
sends.
* **System Default Action Buttons only work inside Interactive Message blocks** — you can't add
one to a Text, Image, or other message block.
* **Confirm Order / Cancel Order are eCommerce-only** — they don't fire from a normal chatbot
conversation.