Every SaaS gets the same dozen questions on repeat: pricing, refunds, integrations, hours, GDPR, login problems, missing features, "is X possible?", invoices, billing email, security, and "are you a real person?". Patterns in muro let you answer each of these without an agent reading the message — sub-second response, zero burnout.
Below is the library we ship in the demo workspace. Copy any of them into your Settings → Patterns as a starting point. They're all keyword-triggered (case-insensitive) and you can tune the priority so a more specific pattern wins over a generic one.
1. Pricing
Reply with a one-line summary + a link to your pricing page. Don't paste a wall of plan details — the page does that better. Example:
textFlat pricing — no per-seat fee. Solo $19 / Fleet $59.
Full breakdown: https://muro.chat/pricing2. Refund policy
3. Integrations / API
4. Hours / availability
5. GDPR / privacy / data
6. "Are you a real person?"
This one's easier than people think — visitors aren't hostile, they just want to know what they're talking to. A direct, short answer is fine: "You're currently chatting with our auto-reply bot. A human will jump in within ~5 minutes during business hours."
7. Login / password help
8. Migration from another chat tool
A huge share of pre-sales chats are "can I bring my stuff over?". Be honest about what transfers: "Switching is quick — drop in the widget snippet and you're live. We don't bulk-import old conversation history, but you can import your canned replies via CSV so the team starts ready on day one."
9. Missing feature / roadmap
Don't fake a date. A real answer is: "We don't have a public roadmap. If this is a blocker for you, send details — we'll let you know if it's on the next quarter's list."
10. Invoice / billing email
11. Security / SOC 2 / penetration test
12. Languages / i18n
A note on tuning
Patterns can fight each other if you're not careful — "price" matches both "what's the price?" and "I bought a printer with my last invoice". Use the priority field to break ties (higher wins) and prefer multi-word keywords over single ones for accuracy. Watch the /app/notifications stream for a few days after you ship a pattern; you'll see which messages it caught and which it shouldn't have.