<aside> 💡 Use case: answer chats and DMs at any hour with words you approved, capture real leads into your CRM, and wake you only when a message is worth it.

</aside>

<aside> 👀 Who reads this folder: Leads & conversations, and the orchestrator. The playbook "DM or lead at 11pm" reads routing-rules.md to decide whether to wake you.

</aside>

faq-library.md

<aside> 📚 Controls: every answer the bot may give. If a question is not in this file, the bot hands it to a person.

How to fill it: write questions the way customers really ask them, and keep each answer short enough for a chat bubble. Prices, dates and policies are copied from where they really live, and every answer carries a "Last checked" date.

Save as brand-os/conversation/faq-library.md.

</aside>

# FAQ library

> Read by: leads-conversations, which answers through ManyChat, Twilio SMS and Front.
> If a question is not in this file, the bot does not answer it. It hands over to a person (see routing-rules.md).
> Every answer here is one you have approved, word for word. Prices, dates and policies are copied from where they really live.

## How to fill it
- Write the question the way customers actually ask it. Add the other ways they ask it in "Also asked as".
- Keep each answer short enough for a chat bubble.
- Put the "Last checked" date on every answer and re-check anything with a price, a date or a policy in it.

## Orders and delivery
| ID | Question | Also asked as | Approved answer | Link | Last checked |
|---|---|---|---|---|---|
| F01 | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] |
| F02 | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] |

Example row (Northwind Coffee): | F01 | When will my order ship? | where is my order, shipping time | [your real shipping answer] | /shipping | [date] |

## Product
| ID | Question | Also asked as | Approved answer | Link | Last checked |
|---|---|---|---|---|---|
| F10 | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] |
| F11 | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] |

## Prices and offers
- Prices come only from: [FILL IN: your price page or product feed]. The bot links there and never types a price from memory.

| ID | Question | Also asked as | Approved answer | Link | Last checked |
|---|---|---|---|---|---|
| F20 | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] |

## Hours, location and contact
| ID | Question | Also asked as | Approved answer | Link | Last checked |
|---|---|---|---|---|---|
| F30 | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] |

## Returns, refunds and account
| ID | Question | Also asked as | Approved answer | Link | Last checked |
|---|---|---|---|---|---|
| F40 | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] |

## Questions the bot never answers
Always handed to a person.
- Anything about a specific person's order, payment or account details
- Complaints
- [FILL IN]

routing-rules.md

<aside> 🧭 Controls: who handles each kind of message, how fast, what makes a lead real, when the owner gets an SMS, and how contacts go into HubSpot without duplicates.

How to fill it: set your business hours and quiet hours first. Then write the checks that make a lead real for your business. Keep phone numbers in your Twilio settings, never in this file.

Save as brand-os/conversation/routing-rules.md.

</aside>

# Routing rules

> Read by: leads-conversations. Tools: ManyChat (chat and DMs), HubSpot (CRM), Twilio (SMS), Calendly (your own booking link for leads), Front (shared inbox).
> Who handles each kind of message, how fast, and when a message is real enough to wake the owner.

## Hours
- Business hours: [FILL IN: days and times, with time zone]
- Quiet hours (nobody is woken): [FILL IN]

## Who handles what
| Intent | Looks like | Handled by | Channel | Reply within |
|---|---|---|---|---|
| FAQ | A question in conversation/faq-library.md | bot | where it came in | right away |
| New lead | Wants to buy, book or get a quote | bot qualifies, then [FILL IN: person] | [FILL IN] | [FILL IN] |
| Existing customer issue | Order, delivery, account | [FILL IN: person or team] in Front | [FILL IN] | [FILL IN] |
| Complaint | Upset, something went wrong | [FILL IN: person] | [FILL IN] | [FILL IN] |
| Partnership or press | Collaboration, media | the owner | [FILL IN] | [FILL IN] |
| Job seeker | Asking about work | [FILL IN] | [FILL IN] | [FILL IN] |
| Spam or abuse | Links, insults, bots | nobody, archive it | none | none |

## What makes a lead real
A lead counts as real when it meets all of these:
| Check | Real when |
|---|---|
| [FILL IN: e.g. what they want] | [FILL IN] |
| [FILL IN: e.g. where they are] | [FILL IN] |
| [FILL IN: e.g. size of the order or job] | [FILL IN] |

Example row (Northwind Coffee): | What they want | A wholesale order for a cafe or an office |

## Waking the owner
The playbook dm-lead-at-11pm reads this.
- Wake the owner outside business hours only when: the lead is real (table above) and [FILL IN: anything else, e.g. they asked to talk today]
- How: Twilio SMS to [FILL IN: the owner's number is stored in your Twilio settings, not here]
- The SMS says: "[FILL IN: e.g. Real lead from <channel>: <one-line summary>. Details in HubSpot.]"
- Everything else waits for the morning in Front, with the bot's auto-reply sent.

## HubSpot
- Before creating a contact, search HubSpot by email and phone. If one exists, update it. Never create a second record for the same person.
- Fields the bot fills: [FILL IN: name, email, phone, source channel, what they asked]
- Lead source value: [FILL IN: the value you use for chat and DM leads]

## Never
- Share one customer's details with another.
- Give a refund, a discount or a promise that is not in faq-library.md without a person's OK.
- Send the booking link to anyone who is not a real lead: [FILL IN: or "send it to everyone who asks"]

auto-reply-scripts.md

<aside> 🤖 Controls: the exact messages ManyChat may send without a person: hello, after hours, lead questions, your own Calendly booking link, hand over, complaint, stop.

How to fill it: write each message in your voice. The bot sends them word for word and fills only the parts in angle brackets.

Save as brand-os/conversation/auto-reply-scripts.md.

</aside>

# Auto-reply scripts

> Read by: leads-conversations. These are the exact messages ManyChat (and Twilio for SMS) may send without a person.
> Write them in your voice. The bot sends them word for word, filling only the parts in angle brackets.
> Anything outside these scripts and conversation/faq-library.md goes to a person.

## How the bot introduces itself
[FILL IN: e.g. say it is an automated assistant for <brand>]

## Scripts
| ID | When it is sent | Message | Next step |
|---|---|---|---|
| R01 Hello, business hours | First message in business hours | [FILL IN] | answer from faq-library.md or route |
| R02 Hello, after hours | First message outside business hours | [FILL IN: say when a person will reply] | log in Front, check routing-rules.md for waking the owner |
| R03 FAQ answer | The question matches faq-library.md | <approved answer> + [FILL IN: e.g. "Did that answer it?"] | if no, hand over |
| R04 Lead questions | Someone wants to buy, book or get a quote | [FILL IN: the questions that test routing-rules.md, one at a time] | create or update the contact in HubSpot |
| R05 Booking link | A real lead wants to talk | [FILL IN: your line] + <your Calendly link> | log the booking in HubSpot |
| R06 Hand over | The bot cannot help | [FILL IN: tell them a person will reply and roughly when] | assign in Front |
| R07 Complaint | Someone is upset | [FILL IN: sorry, a person will pick this up] | route to the complaint owner, no promises |
| R08 Stop | They ask to stop messages | [FILL IN: confirm they will get no more messages] | mark as opted out in HubSpot and ManyChat |
| R09 Not understood | The bot cannot tell what they want | [FILL IN] | after [FILL IN: how many tries], hand over |

Example (Northwind Coffee), R02: "Thanks for the message. We're roasting, not reading, right now. A person will reply after we open at [your opening time]."

## Rules
- Never more than [FILL IN: how many] automated messages before a person takes over.
- Never send a price, a date or a policy that is not in faq-library.md.
- A stop request is honoured at once, on every channel.

<aside> 👉 Next: /reporting

</aside>