diff --git a/src/linq/resources/chats/chats.py b/src/linq/resources/chats/chats.py
index 81edb5e..536da39 100644
--- a/src/linq/resources/chats/chats.py
+++ b/src/linq/resources/chats/chats.py
@@ -300,6 +300,24 @@ def create(
         This rule applies only to `POST /v3/chats`. Follow-up messages on an existing
         chat (`POST /v3/chats/{chatId}/messages`) are not subject to this restriction.
 
+        ## Reusing an Existing Chat
+
+        Chats are keyed on the `from` line plus the exact set of `to` handles. Repeating
+        this request with the same `from` and `to` returns the **existing** chat and
+        sends the message into it instead of starting a second conversation.
+
+        A group chat that has a `display_name` is excluded from that matching. To run
+        several parallel groups over the same participants, name each one with
+        `PUT /v3/chats/{chatId}` before creating the next: the following
+        `POST /v3/chats` with the same `to` then returns a new, separate `chat_id`. Two
+        other cases also produce a new chat instead of reusing one — the participant set
+        changed (a participant was added or removed), or the `from` line left the group.
+
+        Whenever the response is a new chat, the first-message rules above apply to that
+        request: no link in the first message, and no `reply_to` or message effect. To
+        send into a chat you already know, use `POST /v3/chats/{chatId}/messages` with
+        its `chat_id`.
+
         Args:
           from_: Sender phone number in E.164 format. Must be a phone number that the
               authenticated partner has permission to send from.
@@ -921,6 +939,24 @@ async def create(
         This rule applies only to `POST /v3/chats`. Follow-up messages on an existing
         chat (`POST /v3/chats/{chatId}/messages`) are not subject to this restriction.
 
+        ## Reusing an Existing Chat
+
+        Chats are keyed on the `from` line plus the exact set of `to` handles. Repeating
+        this request with the same `from` and `to` returns the **existing** chat and
+        sends the message into it instead of starting a second conversation.
+
+        A group chat that has a `display_name` is excluded from that matching. To run
+        several parallel groups over the same participants, name each one with
+        `PUT /v3/chats/{chatId}` before creating the next: the following
+        `POST /v3/chats` with the same `to` then returns a new, separate `chat_id`. Two
+        other cases also produce a new chat instead of reusing one — the participant set
+        changed (a participant was added or removed), or the `from` line left the group.
+
+        Whenever the response is a new chat, the first-message rules above apply to that
+        request: no link in the first message, and no `reply_to` or message effect. To
+        send into a chat you already know, use `POST /v3/chats/{chatId}/messages` with
+        its `chat_id`.
+
         Args:
           from_: Sender phone number in E.164 format. Must be a phone number that the
               authenticated partner has permission to send from.
diff --git a/uv.lock b/uv.lock
index 5c4d766..a5cdde6 100644
--- a/uv.lock
+++ b/uv.lock
@@ -530,7 +530,7 @@ wheels = [
 
 [[package]]
 name = "linq-python"
-version = "0.16.0"
+version = "0.17.0"
 source = { editable = "." }
 dependencies = [
     { name = "anyio" },