Contact routing

Send the message to the right operating lane.

Knyton uses dedicated addresses so service requests, product inquiries, partnerships, support, and formal correspondence remain separated and accountable.

Primary contact

Start with the purpose of the message.

For a new paid service project, use the guided questionnaire on the Services page. For everything else, use the address that matches the subject below.

Business services

contact@knyton.com

New Sarim Systems service requests, general business inquiries, and project intake.

Compose email →
Founder and executive matters

founder@knyton.com

Executive correspondence, confirmed client matters, formal proposals, and founder-level communication.

Compose email →
Partnerships

partnerships@knyton.com

Institutional relationships, collaborations, pilots, sponsorship discussions, and strategic partnerships.

Compose email →

Product inquiries

Each active product has its own address.

Product inquiries should not be routed through the general services inbox. This preserves clean records and prevents Mirsad, Rasil AI, and Qiyad correspondence from being mixed together.

Mirsad

mirsad@knyton.com

Mirsad beta access, research-platform inquiries, and product-specific communication.

Compose email →
Rasil AI

rasil@knyton.com

Rasil private-alpha interest, product inquiries, and approved operator communication.

Compose email →
Qiyad Logistics

qiyad@knyton.com

Qiyad correspondence only. Qiyad Corridor Intelligence remains paused and no logistics service is currently offered.

Compose email →

Specialist routing

Operational mailboxes for established matters.

These addresses are intended for the specified subject. New sales inquiries should begin through contact@knyton.com rather than billing, support, legal, or vendor channels.

Customer supportsupport@knyton.com
Billing and account recordsaccounts@knyton.com
Media relationspress@knyton.com
Legal correspondencelegal@knyton.com
Privacy requestsprivacy@knyton.com
Vendor relationsvendors@knyton.com

Security boundary

Do not email passwords, payment-card data, or private customer records.

Initial email is appropriate for project descriptions and ordinary business information. Credentials, regulated data, confidential customer records, and sensitive files require a separately approved transfer method.