01Support
support@cosantoir.com
Support inbox
Primary customer support for account, product, and service issues.
Support
Customer operations route through the official `@cosantoir.com` support inboxes.
Use the mailbox that matches the situation so account support, rollout help, and customer operations land with the right team from the first message.
Choose the right inbox for faster response and clear ownership.
4
Support inboxes
2
Routing surfaces
Structured
Intake mode
/support@cosantoir.com/help@cosantoir.com/customers@cosantoir.com/success@cosantoir.com/Account help/Rollout guidance/Customer operations/support@cosantoir.com/help@cosantoir.com/customers@cosantoir.com/success@cosantoir.com/Account help/Rollout guidance/Customer operations
Support Dispatch
Put the issue into the right queue before the first reply.
This intake builds a case reference, picks the destination mailbox, and gives you a ready-to-send support draft without bouncing you through dead routes.
Product issueLane 01
Account accessLane 02
Billing or subscriptionLane 03
Rollout guidanceLane 04
Security or abuseLane 05
Sales or procurementLane 06
Structured Intake
Build the case first.
Short and exact is better than long and vague. Reference IDs, timestamps, and the affected surface matter more than a wall of text.
Mailbox routing
Structured intake first, mailbox routing second.
Prepare the case with a reference ID and concise summary first, then use the mapped mailbox when email follow-through is still the fastest path.
Routing without a case shape still wastes the first reply.
02Help
help@cosantoir.com
Support inbox
General help desk intake and first-response customer assistance.
03Customers
04Success
success@cosantoir.com
Support inbox
Customer success, rollout guidance, and ongoing adoption support.
Intake quality
The details that make a support case actually actionable.
Give the team enough context to route, reproduce, and prioritize the issue without spending the first exchange reconstructing missing facts.
Short is fine as long as the essentials are included.
01Include this
Identify the account and surface
Support intake
Account email, organization name, and the product surface involved.
02Include this
Describe the issue cleanly
Support intake
A clear issue summary, timestamps, and any region, device, or browser context.
03Include this
Attach the evidence that matters
Support intake
Request IDs, screenshots, or billing references when the issue is time-sensitive.
Routing notes
How Cosantoir separates support, rollout, and security handling.
General issues, rollout planning, and disclosure-grade security reports do not belong in the same queue, so the support surface now makes those boundaries explicit before the email is sent.
Clear separation keeps response fast and accurate.
01Routing
General support lands in the primary queue
Operator note
Support handles general account and product issues through the primary mailbox.
02Routing
Rollout help belongs with customer success
Operator note
Customer success covers rollout planning, adoption, and operational follow-through.
03Routing
Security findings should bypass general support
Operator note
If the issue is a security finding or active abuse case, route it through the dedicated security page instead.
Next routes
Continue into the route that matches the case you just built.
Use support for account and product issues, move into the security route for verified findings, or switch into the company contact surface when the request belongs elsewhere.
Routing goal
Case-first
Theme
Black
Surface type
Operational