Chat
Chat is the message thread between a supplier and each of its customers, and between a supplier and the Clipp team. It lives on the Chats page and opens from the customer page and from orders.
Who uses it
- Supplier staff start conversations with customers, answer them and ask Clipp for help.
- Restaurants reply to their suppliers in the app.
At a glance
| Part | What it does |
|---|---|
| Conversation list | Every thread the business is in, with an unread indicator |
| Thread | The messages, replies in a side thread, and the message box |
| Compose (suppliers) | The pencil icon: pick a customer and start a thread |
| Need Help? | Opens the thread with the Clipp team |
In this section
| Page | What it covers |
|---|---|
| Conversations | Opening, starting and answering threads |
| Message notifications | Push messages, and the email, text and push reminders for unread messages |
Where it shows up
- Chats page (
/chat), and Chat with Customer on the customer page. - Push messages that open the chat; reminder emails and texts.
Permissions
| Action | Needs |
|---|---|
| Read threads | Chat: read access |
| Send, reply, start threads | Chat: full access |
With read access the message box is hidden and replies are off. The thread with the Clipp team is always writable.
Decisions
- Threads are keyed by the two businesses, not by people, so every staff member sees the same thread.
Specs
How a customer's name, email and logo are resolved in chat is described in chat.feature (a planned model; see Customer info).
Known limitations
- Threads with an inactive customer are hidden from the restaurant.
- The page shows "Something went wrong. please try later" if the chat service cannot be reached.
FAQ
I can read a thread but can't reply. Your role has read-only Chat access. See Staff & roles.
How do I message a customer who has never chatted with me? Press the pencil icon, search the customer and select them.