Discuss Nami
Tell us what you need to prioritize and which evidence you already use.
Nami enquiries →Share the publication, the question, and enough context to understand the work. Do not include passwords, API keys, payment details, or other secrets.
Tell us what you are working on.
Choose the closest topic and include enough context for us to understand the publication or question. Do not include passwords, API keys, payment details, or other secrets.
Send an enquiryDiscuss Nami
Start with the reason you came here.
Discuss Distribution
Share the destinations you use and how drafts are reviewed, approved, and scheduled.
Distribution enquiries →Product or support
Ask about current access, a plan, the Special Launch, or a problem with the publication.
Product or support →For Nami or Distribution enquiries, include a public publication URL if available. For support, describe what you did, what you expected, and what happened.
Give us enough context to understand the question.
For Nami or Distribution enquiries, include the public URL if one is available. For support, describe what you did, what you expected, and what happened.
What happens next
CMSense reviews the topic and publication context. A message does not guarantee design-partner access, a specific product outcome, or an invitation to another program.
Already use CMSense?
Sign in first when the request involves account access, billing, or a private publication.
Open CMSenseLoading contact form…
Keep secrets out of the message.
CMSense does not need your password, payment card details, API keys, session cookies, or server credentials to review a contact request.