docs(KNO-12105): update push engagement status copy in message-statuses

[webbjordy]

Summary

• Replaces the outdated Push — Not currently supported entry under Marked as read / opened with accurate copy explaining that push read status is not implicitly managed by Knock but can be set manually via the message engagement API using knock_message_id, and that Knock's mobile SDKs handle this automatically when a notification is tapped.
• Applies the same correction to the Link clicked push entry — swaps "Not currently supported" for "Not implicitly managed by Knock. You can manually set this status using the message engagement API with the knock_message_id from the push payload." (SDK sentence omitted here since tap handlers set read/interacted, not link_clicked).

Closes KNO-12105.

Test plan

• Verify the updated push entries read accurately on docs.knock.app/send-notifications/message-statuses#marked-as-read--opened and #link-clicked
• Confirm no broken links were introduced

🤖 Generated with Claude Code

[linear]

KNO-12105 [Docs] Update docs regarding push engagement status support

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Mar 18, 2026 9:55pm

[cursor]

Risk LOW: Updates push engagement status copy in message-statuses.mdx, replacing "Not currently supported" with accurate descriptions of manual and SDK-based status management.

Reasons

• Only a single .mdx content file is modified — no components, layouts, or configuration files touched
• The diff is minimal at 2 additions and 2 deletions (4 total lines changed)
• No new pages, sidebar changes, or image additions
• Changes are confined to a single documentation section (content/send-notifications/)
• Pure copy update with no structural or logic changes

Notes

• Verify the references to "message engagement API" and "Knock's mobile SDKs" are accurate and match current product capabilities
• Confirm that the knock_message_id terminology aligns with the actual push payload field name
• Author (webbjordy) is not yet in the repository contributor list, so skipping auto-approval — a team member should review and approve

  

_{Sent by Cursor Automation: Docs PR classifier}

[webbjordy]

Hey @cellomatt and @scotidodson addressed the feedback on the link_clicked push entry. Leaving threads 1 and 3 for Scoti's follow-up restructure PR. Ready for another look when you get a chance!

[scotidodson]

Changes look great!