PolyAI-LDN · mintlify · Aug 17, 2026
diff --git a/api-reference/messaging/sms-and-rcs-api/introduction.mdx b/api-reference/messaging/sms-and-rcs-api/introduction.mdx
@@ -6,7 +6,7 @@ description: "Send and receive SMS messages through your PolyAI agent."
 
 The SMS API lets you programmatically send SMS messages to end users and handle inbound replies through your PolyAI agent. It supports two directions:
 
-- **Outbound** — your system triggers an SMS to a user via the [Send SMS](/api-reference/sms/endpoint/send-sms) endpoint. Each request creates a new conversation session.
+- **Outbound** — your system triggers an SMS to a user via the [Send SMS](/api-reference/messaging/sms-and-rcs-api/send-sms) endpoint. Each request creates a new conversation session.
 - **Inbound** — users reply to an outbound SMS (or message your agent's number directly). The agent handles the conversation automatically over SMS. No API calls are needed from your side.
 
 ## Prerequisites
@@ -82,7 +82,7 @@ When a user sends an SMS to one of your provisioned Twilio numbers:
 | **New user** | A new conversation session is created. The agent's start function runs with `conv.channel_type = "sms"`. |
 | **Active session exists** | The message is added to the existing conversation. The agent continues where it left off. |
 | **Previous session timed out** | A new session is created. |
-| **Reply to an outbound SMS** | The message is added to the session created by the [Send SMS](/api-reference/sms/endpoint/send-sms) endpoint. The outbound message is part of the conversation context. |
+| **Reply to an outbound SMS** | The message is added to the session created by the [Send SMS](/api-reference/messaging/sms-and-rcs-api/send-sms) endpoint. The outbound message is part of the conversation context. |
 
 ### Inactivity timeout
 

diff --git a/api-reference/messaging/sms-and-rcs-api/rcs.mdx b/api-reference/messaging/sms-and-rcs-api/rcs.mdx
@@ -37,7 +37,7 @@ Handoff is supported on RCS, in the same way as SMS. See [Chat handoff integrati
 
 ## Sending messages to customers (outbound)
 
-Outbound RCS messages work the same way as [outbound SMS](/api-reference/sms/endpoint/send-sms), with two differences:
+Outbound RCS messages work the same way as [outbound SMS](/api-reference/messaging/sms-and-rcs-api/send-sms), with two differences:
 
 - You must pass the Twilio Messaging Service SID for your RCS sender in the `messaging_service_sid` field.
 - The recipient's number in `user_number` must be prefixed with `rcs:`.
@@ -207,6 +207,6 @@ The possible cases are:
 
 ## Related
 
-- [SMS API](/api-reference/sms/introduction)
-- [Send an outbound SMS](/api-reference/sms/endpoint/send-sms)
+- [SMS API](/api-reference/messaging/sms-and-rcs-api/introduction)
+- [Send an outbound SMS](/api-reference/messaging/sms-and-rcs-api/send-sms)
 - [Chat handoff integrations](/integrations/chat/introduction)
diff --git a/integrations/chat/amazon-connect.mdx b/integrations/chat/amazon-connect.mdx
@@ -79,7 +79,7 @@ If you see `ResourceNotFoundException`, the region is almost certainly wrong –
   <Card title="Chat handoff overview" href="/integrations/chat/introduction" icon="message">
     All chat handoff integrations and the shared payload shape.
   </Card>
-  <Card title="Managed Topic actions" href="/managed-topics/how-to-setup-action/handoff" icon="bolt">
+  <Card title="Managed Topic actions" href="/knowledge/faqs/actions/handoff" icon="bolt">
     Wire a function into a Knowledge topic.
   </Card>
 </CardGroup>
diff --git a/integrations/chat/five9.mdx b/integrations/chat/five9.mdx
@@ -68,7 +68,7 @@ If the conversation never reaches Five9, check that the inbound campaign is **Ru
     All chat handoff integrations and the shared payload shape.
   </Card>
 
-  <Card title="Managed Topic actions" icon="bolt" href="/managed-topics/how-to-setup-action/handoff">
+  <Card title="Managed Topic actions" icon="bolt" href="/knowledge/faqs/actions/handoff">
     Wire a function into a Knowledge topic.
   </Card>
 

diff --git a/integrations/chat/nice-cxone.mdx b/integrations/chat/nice-cxone.mdx
@@ -62,7 +62,7 @@ If the conversation never reaches CXone, double-check **Integrations > NICE CXon
   <Card title="Chat handoff overview" href="/integrations/chat/introduction" icon="message">
     All chat handoff integrations and the shared payload shape.
   </Card>
-  <Card title="Managed Topic actions" href="/managed-topics/how-to-setup-action/handoff" icon="bolt">
+  <Card title="Managed Topic actions" href="/knowledge/faqs/actions/handoff" icon="bolt">
     Wire a function into a Knowledge topic.
   </Card>
 </CardGroup>
diff --git a/integrations/chat/webex.mdx b/integrations/chat/webex.mdx
@@ -57,7 +57,7 @@ If the conversation never reaches Webex, check the Bring Your Own Channel config
   <Card title="Chat handoff overview" href="/integrations/chat/introduction" icon="message">
     All chat handoff integrations and the shared payload shape.
   </Card>
-  <Card title="Managed Topic actions" href="/managed-topics/how-to-setup-action/handoff" icon="bolt">
+  <Card title="Managed Topic actions" href="/knowledge/faqs/actions/handoff" icon="bolt">
     Wire a function into a Knowledge topic.
   </Card>
   <Card title="Managed services" href="/integrations/managed-services" icon="handshake">

diff --git a/messaging-channel/sms-and-rcs/rcs.mdx b/messaging-channel/sms-and-rcs/rcs.mdx
@@ -96,11 +96,11 @@ One configuration powers voice, web chat, SMS, and RCS. Persistent memory travel
     Two-way SMS messaging on the same agent brain as voice and chat.
   </Card>
 
-  <Card title="SMS API" icon="code" href="/api-reference/messaging/SMS %26 RCS API/Overview/send-sms">
+  <Card title="SMS API" icon="code" href="/api-reference/messaging/sms-and-rcs-api/send-sms">
     Send outbound SMS messages through the PolyAI outbound webhook API.
   </Card>
 
-  <Card title="RCS API" icon="code" href="/api-reference/messaging/SMS %26 RCS API/rcs">
+  <Card title="RCS API" icon="code" href="/api-reference/messaging/sms-and-rcs-api/rcs">
     Send rich RCS messages with media, carousels, and SMS fallback.
   </Card>
 

diff --git a/...el/sms-and-rcs/sms-and-rcs-campaign-registration-compliance-requirements-us.mdx b/...el/sms-and-rcs/sms-and-rcs-campaign-registration-compliance-requirements-us.mdx
@@ -91,7 +91,7 @@ Every country in the table below shares the same baseline: opt-in consent before
     Rich, branded messaging over the RCS channel with SMS fallback.
   </Card>
 
-  <Card title="SMS API" icon="code" href="/api-reference/messaging/SMS %26 RCS API/Overview/send-sms">
+  <Card title="SMS API" icon="code" href="/api-reference/messaging/sms-and-rcs-api/send-sms">
     Send outbound SMS messages through the PolyAI outbound webhook API.
   </Card>
 

diff --git a/messaging-channel/sms-and-rcs/sms.mdx b/messaging-channel/sms-and-rcs/sms.mdx
@@ -181,7 +181,7 @@ Conversation lifecycle controls for inactivity timeout, end-of-conversation logi
 ## Related pages
 
 <CardGroup cols={2}>
-  <Card title="SMS API" icon="code" href="/api-reference/messaging/SMS %26 RCS API/Overview/send-sms">
+  <Card title="SMS API" icon="code" href="/api-reference/messaging/sms-and-rcs-api/send-sms">
     Send outbound SMS messages through the PolyAI outbound webhook API.
   </Card>
 

diff --git a/releases/notes/24.11.mdx b/releases/notes/24.11.mdx
@@ -10,7 +10,7 @@ Expand the items for details:
 <AccordionGroup>
 
 <Accordion title="Enhanced SMS" icon="comment-sms" id="enhanced-sms-functionality">
-Builders can now easily upgrade [SMS](/messaging-channel/sms) templates into advanced, customizable [functions](/tools/introduction) to support complex use cases.
+Builders can now easily upgrade [SMS](/messaging-channel/sms-and-rcs/sms) templates into advanced, customizable [functions](/tools/introduction) to support complex use cases.
 
 ![calling](/images/release-notes/2411/convert-sms.png)
 

diff --git a/releases/notes/24.12.mdx b/releases/notes/24.12.mdx
@@ -19,7 +19,7 @@ Expand the items for details:
 Use variants to manage [Knowledge](/knowledge/faqs/introduction) content for multiple locations in a single agent, and use one agent to handle
 enquiries about a business with outlets in different timezones, legal jurisdictions, or tax codes.
 
-Each variant has content for custom attributes like phone numbers, addresses, and opening hours. You can use variants and variables in [SMS](/messaging-channel/sms),
+Each variant has content for custom attributes like phone numbers, addresses, and opening hours. You can use variants and variables in [SMS](/messaging-channel/sms-and-rcs/sms),
 [functions](/tools/introduction), and [Knowledge](/knowledge/faqs/introduction) entries, with the `${variant_foo}` format:
 
 > Imagine you have an attribute `site_number`, your SMS content field would be:

diff --git a/releases/notes/25.01.mdx b/releases/notes/25.01.mdx
@@ -80,7 +80,7 @@ End functions allow unconditional function calls at the conclusion of conversati
 
 **Use Cases:**
 - **Data logging:** Save conversation details to a [CRM](/integrations/introduction).
-- **Task automation:** Trigger workflows or send follow-up [SMS](/messaging-channel/sms).
+- **Task automation:** Trigger workflows or send follow-up [SMS](/messaging-channel/sms-and-rcs/sms).
 
 Visit the full [End Function](/tools/end-tool) page for implementation details.
 

diff --git a/releases/notes/25.03.mdx b/releases/notes/25.03.mdx
@@ -86,7 +86,7 @@ SMS messages are now triggered **inline** during [function](/tools/introduction)
 </Accordion>
 
 <Accordion title="Improved KB search for actions" icon="magnifying-glass" id="improved-kb-search-for-actions">
-The Knowledge search bar now fully indexes action keywords like [SMS](/messaging-channel/sms), [handoff](/voice-channel/handoffs), [function](/tools/introduction), and [variant](/knowledge/variants/introduction).
+The Knowledge search bar now fully indexes action keywords like [SMS](/messaging-channel/sms-and-rcs/sms), [handoff](/voice-channel/handoffs), [function](/tools/introduction), and [variant](/knowledge/variants/introduction).
 
 **What's new:**
 - These terms are now searchable across the Knowledge area.

diff --git a/releases/notes/26.05.mdx b/releases/notes/26.05.mdx
@@ -29,7 +29,7 @@ When an SMS conversation goes idle and the session times out due to inactivity,
 
 This applies only to abandoned (timed-out) sessions. Conversations that end naturally or because the user explicitly leaves are unchanged.
 
-See [SMS overview → Session timeouts](/messaging-channel/sms#session-timeouts) for details.
+See the [SMS overview](/messaging-channel/sms-and-rcs/sms) for details.
 
 </Accordion>
 

diff --git a/voice-channel/message-templates.mdx b/voice-channel/message-templates.mdx
@@ -232,7 +232,7 @@ The notification is sent automatically and does not require configuration. It us
   <Card title="Twilio integration" icon="phone" href="/voice-channel/numbers/twilio/introduction">
     Connect your Twilio account to enable SMS.
   </Card>
-  <Card title="Outbound SMS API" icon="paper-plane" href="/api-reference/outbound-sms/introduction">
+  <Card title="Outbound SMS API" icon="paper-plane" href="/api-reference/messaging/sms-and-rcs-api/introduction">
     Send SMS programmatically and open reply-enabled sessions.
   </Card>
   <Card title="Self-serve dashboards" icon="chart-line" href="/analytics/dashboards/introduction">

diff --git a/voice-channel/number-availability.mdx b/voice-channel/number-availability.mdx
@@ -140,7 +140,7 @@ Before going live with 2-way SMS in any country:
   <Card title="Message templates" icon="message" href="/voice-channel/message-templates">
     Set up Twilio, create templates, and send SMS from your agent.
   </Card>
-  <Card title="Outbound SMS API" icon="paper-plane" href="/api-reference/outbound-sms/introduction">
+  <Card title="Outbound SMS API" icon="paper-plane" href="/api-reference/messaging/sms-and-rcs-api/introduction">
     Send SMS programmatically and open reply-enabled sessions.
   </Card>
   <Card title="Twilio integration" icon="phone" href="/voice-channel/numbers/twilio/introduction">