← All posts
Playbook6 min read

[PLAYBOOK] · May 4, 2026 · 07:30

Twelve chat patterns every SaaS should ship on day one

A pre-built library of auto-replies that handle 60-80% of incoming messages without an agent ever opening the inbox.

RM

Robin Monteiro

Founder, muro.chat

#patterns#auto-reply#playbook#support-ops

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 $12 / Team $24 / Pro $49.
Full breakdown: https://muro.chat/pricing

2. 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. Self-hosting / on-prem

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.

RM

✎ Written by

Robin Monteiro

Founder, muro.chat