We create support tickets automatically from inbound phone calls, so those tickets have no conversation thread. We want to email the customer our answer from our shared support inbox and have their reply come back onto the same ticket. A human does this in seconds from the Help Desk. We cannot find any supported way to do it from the API.
What we tried, with the actual results
- POST to the conversations threads collection returns 405, while GET on the same collection returns 200. The v4 equivalent is 404.
- Replying into an existing thread works: POST /conversations/v3/conversations/threads/{threadId}/messages returns 400 VALIDATION_ERROR rather than 404, so only thread creation is missing.
- PUT /crm/v4/objects/ticket/{ticketId}/associations/default/conversation/{threadId} returns 200 and attaches an existing thread to a threadless ticket, so association is not the problem.
- The Help Desk UI uses a private front end RPC, createEmailThreadAndSend, which is cookie and CSRF authenticated and not usable with a private app token.
- Single send needs the transactional email add on, and creates no thread anyway.
- The only email action a ticket workflow offers points at a marketing asset, which is not our shared inbox and creates no thread.
- An email engagement created with hs_email_status: SENT logs on the timeline and delivers nothing.
Question
Is there any supported route today, public or beta, for an app to originate an email thread on a ticket in a shared inbox?
This has been asked before without resolution
- I create a Ticket via API - It's got no Conversation (Feb 2026, accepted answer says no public API can create a thread)
- Idea, still open since Aug 2023: Create Conversation over the API