Team Chat — saved replies
Keep a list of replies you send often and drop one into a message from the composer's + menu. Picking a saved reply puts its text in the message box at your cursor — it never sends for you. The same list adds, edits and deletes replies, it is private to you, and it follows you to every device you sign in on. Plans differ only in how many you can keep.
On this page
A saved reply is a title and a block of text you use again and again — a standup format, a "thanks for the review" note, an away message. Instead of retyping it, you open the list and click it into the message you are already writing.
Where to find it
In any Team Chat message box — in a channel or in a thread — open the + menu and choose Saved replies.
You will not see it in a Direct Message with an outside connection: that composer has no workspace, so saved replies do not apply there.
Using one
- Open Saved replies from the + menu.
- Search by the reply's title or by words inside it.
- Click the reply.
Its text goes into the message box at your cursor, replacing whatever you had selected. It is not sent: you can add to it, add mentions, or delete it before pressing Send.
Adding, editing and deleting
- New reply opens a short form: a title (up to 100 characters) and the message text (up to 4,000 characters). Save and it appears in the list.
- The pencil on a row edits that reply.
- The trash on a row asks you to confirm, then deletes it permanently.
Who can see them
Saved replies are yours. They live in your own space in each workspace, so nobody else in the workspace — not other members, not admins — can read or change them. They sync across your devices, so a reply you save on one computer is there on the next one you sign in on.
How many you can keep
Every plan has saved replies. Plans differ only in how many you can keep, and the list shows how many you are using once a numeric limit applies. When you reach the limit, New reply is disabled and the dialog says so; editing and deleting still work, so making room is one click away.
If something goes wrong
A list that could not load says so and offers Try again. A save or delete that fails is shown in the dialog and leaves the list as it was — nothing is removed silently.
Notes for developers
- The data lives at
{tenant root}/saved/{uid}/savedReplies/{replyId}, one document per reply, withtitle,text,createdAtandupdatedAt. Path builders:savedRepliesPathFor/savedReplyDocPathForinsrc/shared/team-chat/firestore-paths.ts. - Caps live once in
src/shared/team-chat/saved-replies.tsand are mirrored infirebase/firestore.rules; the rules also allow only the owner and only those four fields. - The quantity limit is the
max_team_chat_saved_replies_per_workspaceentry insrc/shared/paid-offering.ts. It is a picker-side guard (the rules cannot count documents): the list query is bounded, the picker refuses a create past the plan cap or the 500-reply guard, and the rules bound each document's fields and size. A client that bypassed the picker could still create more replies; there is no server relay for this collection yet. - Account erasure and org member removal delete the parent
saved/{uid}doc recursively (RECURSIVE_MEMBER_PRIVATE_SUBCOLLECTIONSinfirebase/functions/src/member-private-docs.ts). On a self-serve workspace, a departed member's saved data is deliberately retained per RT-025 (chat-workspaces-member-purge.ts), so their replies stay there until the workspace is deleted. The workspace data export includes the replies and flags truncation past 500. - The rules and this feature are written by the Team Chat lanes; deploying rules and functions is the Go-live lane's job.
Last verified 2026-11-20