> ## 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.

# Things to ask — worked examples

> Real prompts that work with the ChatSyncs MCP server, covering daily inbox triage, following up leads, sending order updates, organising contacts with labels and custom fields, and handling catalog orders. Use when a customer has connected the MCP and asks what they should actually say to the assistant.

Once ChatSyncs is [connected](/mcp/connect), you talk to your assistant normally. These are
prompts that work, and what happens behind each one.

<Tip>
  You don't need to name abilities or IDs. "Message Rahul" is enough — the assistant finds the
  number, works out which of your WhatsApp lines to send from, and formats the request.
</Tip>

## Starting the day

> **"What's happened on WhatsApp since yesterday? Anything I need to reply to?"**

Lists your recent contacts, reads the latest conversations, and points out the ones where the
customer spoke last.

> **"Show me my account — how many message credits have I got left?"**

Your plan, expiry, subscriber count and message credits.

## Replying and following up

> **"Reply to Rahul and tell him his order ships tomorrow."**

Finds Rahul, checks the conversation for context, and sends — after showing you the wording.

> **"Send the order\_shipped template to +91 98765 43210."**

Looks up your approved templates and sends the right one. This works even if the customer
hasn't messaged in weeks, because templates aren't limited by the 24-hour window.

> **"Anyone who asked about pricing this week and never got an answer — list them."**

<Warning>
  The assistant sends **real messages to real people**. It shows you what it's about to send and
  waits for approval. Read it before you approve.
</Warning>

## Organising contacts

> **"Tag everyone who asked about the premium plan as Hot Lead."**

Creates the label if it doesn't exist, then applies it to the contacts you identify.

> **"Put Rahul in the onboarding sequence and note that he's a referral from Priya."**

Enrols him in the follow-up sequence and attaches an internal note your team can see.

> **"Set Rahul's city to Mumbai and his plan to Gold."**

Stores those against his custom fields.

## Working as a team

> **"Assign this conversation to Priya and mark my last three as resolved."**

> **"Which conversations are still open?"**

## Shop and orders

> **"Any new orders today?"**

> **"Mark order ord\_8823 as shipped."**

> **"I've updated products in Commerce Manager — sync my catalog."**

## Buttons and bots

> **"Ask Rahul whether he wants Monday or Tuesday, with buttons."**

Sends a message with tappable reply buttons instead of asking him to type.

> **"Run the welcome flow for the number that just messaged."**

Triggers one of your existing chatbot flows for that contact.

## Prompts that need rephrasing

| What you might say | Why it doesn't work | Say this instead |
| - | - | - |
| "Text everyone on my list about the sale" | There's no bulk send — that's what Broadcasting is for | Build a [broadcast](/learn/chatsyncs-broadcasting/send-a-broadcast-message-in-chatsyncs) in ChatSyncs |
| "Make a template for order updates" | Templates need Meta's approval, so they're created in ChatSyncs | Create it in ChatSyncs, then ask the assistant to send it |
| "Message this customer from last month" | Outside 24 hours, plain text won't deliver | "Send them the re-engagement template" |
| "Upgrade my plan" | The assistant can't touch billing | Do it in ChatSyncs directly |

## Frequently asked

<AccordionGroup>
  <Accordion title="Do I have to phrase things a particular way?">
    No. Ask as you would ask a colleague. If something's ambiguous — like which WhatsApp number
    to send from — the assistant asks.
  </Accordion>

  <Accordion title="Can it do several things in one request?">
    Yes. *"Tag Rahul as VIP, note that he called, and assign him to Priya"* is three actions; the
    assistant runs them in order and confirms each.
  </Accordion>

  <Accordion title="What if it gets something wrong?">
    You approve every action before it happens, so mistakes are caught before they're sent. If a
    message has already gone, it can't be unsent — WhatsApp doesn't allow that.
  </Accordion>

  <Accordion title="Can it read a customer's whole history?">
    It can read recent messages with a contact when you ask it to. It doesn't read anything on
    its own initiative.
  </Accordion>
</AccordionGroup>