> ## Documentation Index > Fetch the complete documentation index at: https://developer.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. 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. ## 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. > **"Send the payment\_reminder template to +91 98765 43210 for invoice INV-1001, ₹5,000, due 15 Oct."** Fills in the customer's name, invoice, amount and due date, and the end of the **Pay Now** button's link. If the template has a quick-reply button, such as **Need help**, it asks which of your bot replies that button should run. You can leave it unset; the message is still sent, but the button then starts no reply. > **"Anyone who asked about pricing this week and never got an answer — list them."** 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. ## 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."** ## Templates > **"Make a template that tells customers their order has shipped, with a button to track it."** Drafts a utility template with the customer's first name and the order number filled in at send time, shows you the wording, and submits it to WhatsApp once you agree. It then tells you the template is waiting for approval, because it can't be sent until WhatsApp says yes. > **"Create a one-time-passcode template that expires after 10 minutes."** Makes the OTP message WhatsApp provides, with its Copy code button and the expiry time shown. > **"Make a summer sale carousel with these three product photos and a Shop Now button on each."** Builds a swipeable carousel. Every card gets the same kind of media and the same buttons, which WhatsApp requires. > **"Has my order\_shipped template been approved yet?"** Checks live with WhatsApp. If it was rejected, you get the reason and what to change. A template that WhatsApp approved can still need its variables mapped in ChatSyncs before the assistant can send it, and it tells you when that is the case. New templates start out waiting for WhatsApp's review, so ask the assistant to check on them rather than sending straight away. The assistant can't edit or delete a template. To change one, ask for a new version under a new name. ## 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](https://help.chatsyncs.com/docs/send-bulk-whatsapp-messages) in ChatSyncs | | "Change the wording of my approved template" | The ChatSyncs API has no way to edit a template yet, so the assistant can't | "Create a new version of order\_shipped called order\_shipped\_v2 with this wording" | | "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 No. Ask as you would ask a colleague. If something's ambiguous — like which WhatsApp number to send from — the assistant asks. 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. Your AI app asks you to approve anything that sends or changes something (unless you've chosen "always allow"), so read what it proposes before approving. If a message has already gone, it can't be unsent: WhatsApp doesn't allow that. It can read recent messages with a contact when you ask it to. It doesn't read anything on its own initiative. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.