Run IT support with structure, automation and accountability — without enterprise complexity.
Manage incidents and service requests, coordinate multi-team fulfilment, route and escalate tickets automatically, track response and resolution targets, and share knowledge across your Kanishu products.
The problem
Requests arrive by email, chat and corridor — and nobody can say what is late
Without one queue, work is chased by memory: who owns this, what is breaching, why does the same laptop keep failing. Answers to "how are we doing" take a spreadsheet and an afternoon.
What changes with Ticketing
Every request in one queue
Tickets from the portal and from your own support mailbox, routed by category to the right team.
Targets you can keep
SLA clocks that respect business hours and holidays and pause while you wait on the customer. Every ticket shows its live SLA status, and breaches are flagged within 15 minutes.
Fewer repeat incidents
Repeat problems on the same asset are spotted and pushed toward a root-cause fix instead of another quick patch.
Changes with a paper trail
Change requests with risk, plans and rollback, approved before work starts — or pre-approved through an approved standard change.
Key capabilities
What Ticketing does across its plans. Availability and limits vary by plan — each capability below shows the plan it starts on, and the comparison lists every difference.
Take the 3-minute tour
Ticketing with sample data — the screens your team would use every day.
See it








Works with the rest of Kanishu
IT Asset Management
Link tickets to assets and see an asset's ticket history (Growth and up); on ITAM's Business plan, raise a ticket straight from an asset.
Vendor & Contract Management
A vendor issue can be escalated straight into a ticket your support team works as usual.
Continuous Assurance
Changes approved by their own requester, or incidents closed without a root cause, are flagged automatically.
Everything Ticketing does
Every capability, grouped by what it's for — not a feature-name soup.
Ticketing Core
Service Catalog & Request Fulfillment
Growth and aboveSLA Management
Change Management
Growth and aboveProblem Management
Major Incident Management
Business and aboveKnowledge Base
Automation
Email-to-Ticket
Growth and aboveCustomer Satisfaction (CSAT)
Growth and aboveReporting & Analytics
Team & Access Management
Security
Integrations & API
Growth and aboveSecurity
Plans & pricing
Capabilities marked "All plans" above are in every plan; higher plans add capacity and the capabilities marked with the plan they start on.
Starter
Minimum 3 agents — from INR 1,197/mo
Growth
Minimum 3 agents — from INR 2,697/mo
Business
Minimum 5 agents — from INR 7,995/mo
Enterprise
Minimum 10 agents — from INR 24,990/mo
Full plan comparison
| Included | Starter | Growth | Business | Enterprise |
|---|---|---|---|---|
| Minimum agents billed | 3 | 3 | 5 | 10 |
| Requesters (end users who raise tickets) | Unlimited & free | Unlimited & free | Unlimited & free | Unlimited & free |
| Ticketing core, SLA, Knowledge Base, Problem Management | ||||
| Service Catalog & approval workflows | — | |||
| CSAT surveys & reporting | — | |||
| Automation rules | 3 | 15 | Unlimited | Unlimited |
| Change Management | — | |||
| Email-to-ticket | — | |||
| Self-service API & cross-product linking | — | |||
| Major Incident Management | — | — | ||
| Moving between Ticketing and other Kanishu products without signing in again | ||||
| API calls a day, per function | — | 500 | 5,000 | Unlimited |
| API clients (integrations without a login) | — | 2 | 5 | 20 |
| Custom report builder | — | — | ||
| SLA policies per ticket category | — | — | ||
| Require MFA (for admins only, or for everyone) | — | — | ||
| Organisation-wide change log and export | — | — | ||
| Joiners, movers and leavers (People) | — | — | ||
| Signed API requests (an HMAC on every call) | — | — | — | |
| Email support (first reply within 3 business days) | ||||
| Priority support (first reply within a business day) | — | — | — | |
| Automatic login changes for joiners and leavers | — | — | — | |
| Single sign-on with your identity provider (SAML: Entra ID, Google, Okta) | — | — | — | |
| Standard changes (pre-approved routine changes, with approval and review) | — |
Questions
Can customers email us to raise a ticket?
Yes, on Growth and up: connect your own support mailbox and each new email becomes a ticket; replies thread onto the same ticket.
Can I buy just this product?
Yes. Every Kanishu product is sold and billed on its own. Start with one and add others later from the same account — no bundle.
Do the products share one sign-in?
Your team moves between the Kanishu products your organisation uses without signing in again. Each product keeps its own roles and permissions, and People keeps one directory of your staff for all of them.
What happens when we reach a plan limit?
Your admins get an email at 80% and again at 100% of a limit. Nothing is deleted: at the limit you can't add more until you free some up or upgrade, and the usage is shown on your My Plan page.
Do you issue GST invoices?
Yes — a GST tax invoice in rupees for every payment.
What support do you offer?
Support is by email, from inside the product (Contact Support) or by replying to our emails. We reply within 3 business days on every plan, and within 1 business day on plans that include priority support. Business days are Monday to Friday, 9:00 to 17:00 India time. We don't offer chat or phone support.
Using more than one part of your IT stack?
See how Ticketing connects with the rest of the suite — one account, single sign-on, and cross-linked records.
How the suite works together