> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orbit.devotel.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Continue a conversation on a different channel

> Re-bind this conversation (its id, message history, AI-agent session state and contact-scoped agent memory) onto `target_channel` so a customer can continue the SAME thread after switching channel (SMS ↔ email ↔ web-chat ↔ voice ↔ …) without repeating themselves. Repoints the conversation's primary `channel` (the default for the next operator OR AI-agent reply) and unions the new channel into `channels[]` so the full cross-channel history keeps loading. Idempotent — already on the target returns 200 with `already_on_channel=true`. Rejects terminal threads (422, reopen first) and channels the contact has no identity for (400). Sends NO outbound message — the next reply still routes via the standard reply path.



## OpenAPI

````yaml /openapi.yaml post /api/v1/conversations/{id}/resume-channel
openapi: 3.1.0
info:
  title: Devotel CPaaS API
  description: Orbit by Devotel — Communications Platform as a Service API
  version: 1.0.0
  contact:
    name: Devotel
    url: https://devotel.io
    email: support@devotel.io
  license:
    name: Proprietary
servers:
  - url: https://api.orbit.devotel.io
    description: Production
security:
  - Bearer: []
  - ApiKey: []
tags:
  - name: Messages
    description: >-
      Send and manage messages across all channels (SMS, WhatsApp, RCS, Email,
      Viber, etc.)
  - name: Fax
    description: >-
      List and track fax (MMS/T.38) transmissions on Telnyx-backed fax numbers
      (sending flows through the Messaging API)
  - name: Agents
    description: AI agent creation, configuration, and execution
  - name: Voice
    description: Voice calls, IVR, conferencing, and SIP trunking
  - name: OnCall
    description: On-call rotations and escalation policy planning for incident alerting
  - name: Webhooks
    description: Webhook endpoint management and delivery logs
  - name: Numbers
    description: Phone number search, provisioning, and configuration
  - name: Brand Identity
    description: >-
      Unified cross-channel brand trust posture (10DLC, toll-free, WhatsApp,
      RCS, branded calling, number KYC)
  - name: Contacts
    description: Contact management, segmentation, and lifecycle tracking
  - name: Campaigns
    description: Marketing campaign orchestration and analytics
  - name: Flows
    description: Automation flow builder and execution engine
  - name: Templates
    description: Message template management and approval workflows
  - name: Settings
    description: Organization, channel, and user preference settings
  - name: Verify
    description: OTP generation and verification across channels
  - name: Push
    description: Push notification delivery via FCM and APNs
  - name: Integrations
    description: Third-party service connections and OAuth management
  - name: CDP
    description: >-
      Customer Data Platform — activation surface (CRM object sync, streaming
      destinations, ad-audience activation)
  - name: Files
    description: >-
      Server-to-server media upload, listing, retrieval, and deletion
      (signed-URL backed)
  - name: Commerce
    description: >-
      Omnichannel conversational-commerce — persistent cart + checkout state
      machine, channel-agnostic hosted pay-by-link, native WhatsApp checkout,
      and AP2-style agent payment mandates.
  - name: Sync
    description: >-
      Real-time shared-state primitive (Twilio Sync parity) — Documents, Maps,
      Lists, and ephemeral Streams, with change events relayed over the
      /api/v1/ws/sync WebSocket gateway
paths:
  /api/v1/conversations/{id}/resume-channel:
    post:
      tags:
        - Conversations
      summary: Continue a conversation on a different channel
      description: >-
        Re-bind this conversation (its id, message history, AI-agent session
        state and contact-scoped agent memory) onto `target_channel` so a
        customer can continue the SAME thread after switching channel (SMS ↔
        email ↔ web-chat ↔ voice ↔ …) without repeating themselves. Repoints the
        conversation's primary `channel` (the default for the next operator OR
        AI-agent reply) and unions the new channel into `channels[]` so the full
        cross-channel history keeps loading. Idempotent — already on the target
        returns 200 with `already_on_channel=true`. Rejects terminal threads
        (422, reopen first) and channels the contact has no identity for (400).
        Sends NO outbound message — the next reply still routes via the standard
        reply path.
      parameters:
        - schema:
            type: string
          in: path
          name: id
          required: true
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              additionalProperties: false
              required:
                - target_channel
              properties:
                target_channel:
                  type: string
                  description: The channel to continue the conversation on.
                  enum:
                    - sms
                    - whatsapp
                    - email
                    - rcs
                    - viber
                    - instagram
                    - messenger
                    - line
                    - telegram
                    - voice
                    - apple_messages
                    - web_chat
                reason:
                  type: string
                  maxLength: 280
                  description: >-
                    Optional free-text note stamped into the activity trail
                    (e.g. "customer asked to switch to email").
      responses:
        '200':
          description: Default Response
components:
  securitySchemes:
    Bearer:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: Dashboard JWT token from Clerk
    ApiKey:
      type: apiKey
      name: X-API-Key
      in: header
      description: Server-to-server API key (dv_live_sk_*)

````