TikTok DMs: support reply-button cards, typing indicator and mark-read

TikTok's Business Messaging API supports three things that Zernio's TikTok send path doesn't pass through yet:

Reply-button cards TikTok's send endpoint accepts message_type: TEMPLATE with QA_BUTTON_CARD and QA_LINK_CARD. Each is a card with a question and 1–3 reply buttons; tapping one sends the button's text as the user's reply.

Without them, every choice on TikTok has to be typed ("reply 1, 2 or 3"), which makes automations clumsy compared with WhatsApp, Instagram and Messenger. I'd also like to know, through the docs or an error, when buttons sent to TikTok aren't delivered. Right now they're ignored without notice.

TT Docs: Send a Q&A button card

Knowing which button was tapped When a user taps a card button, TikTok's im_receive_msg webhook includes reply_source_payload, whose reply_source_unique_id is the id of the tapped button. Without it, a tap and typed text look the same.

TT Docs: Subscribe to TikTok Business Messaging events via Webhooks

Typing indicator TikTok supports message_type: SENDER_ACTION with TYPING, which shows a "Typing" icon for 5 seconds. On TikTok, POST …/typing currently returns success: false. I use typing to pace automated replies on other platforms.

TT Docs: Send a typing action

Mark-read TikTok supports SENDER_ACTION with MARK_READ, which shows a "Seen" mark to the user. On TikTok, POST …/read currently clears only Zernio's unread state.

TT Docs: Send mark as read action

Related (already reported to support): TikTok send failures come back as an error string that contains TikTok's code ("… failed (code 40064): …"), with no platformError object. Support mentioned this is being reviewed. A structured code would let me tell TikTok's refusals apart without parsing text.

TT Docs: Return codes