How Can We Help?
The Kira Help Center is built directly into the product, with guides covering every module and feature available right where you are using them rather than on a separate website you have to navigate to in a different tab. If the guides do not answer what you need, our support team is one message away.
This page is designed to work the way you would actually want a support resource to work. Answer your question first if the answer exists and is easy to find. Give you the option to browse for more depth if you want it. And provide a clear, direct path to a real person the moment either of those is not enough for your specific situation.
We have deliberately tried to avoid the experience that makes getting help feel like a maze you have to successfully navigate before anyone actually engages with your problem. That experience is frustrating in a way that is entirely unnecessary, and it is not how this support center is built.
Why This Is Organized the Way It Is
The structure of this Help Center is deliberate, and understanding the thinking behind it might help you find what you need faster than you otherwise would.
The topics below are organized around what you are actually trying to do, getting started, managing your billing, fixing something that has stopped working, rather than around how our internal teams happen to be organized. Nobody searching for help thinks in terms of which department owns their problem. They think in terms of their actual situation. Why is my call agent not placing calls? How do I request a refund? Where do I update my payment method? Those are the questions this Help Center is built around, in your language, not our org chart.
This matters more than it might sound like at first. A support structure organized around internal departments forces you to correctly guess which team owns your problem before you can even begin looking for an answer. That is an extra step with no value to you whatsoever. It has nothing to do with actually solving what is wrong and everything to do with how the support system happened to be set up. Organizing around your actual goals removes that friction entirely and gets you to the right answer faster regardless of which team ultimately handles the underlying issue.
Browse by Topic
| Topic | What It Covers |
|---|---|
| Getting Started | Setup, connecting your tools, and completing your first tasks on the platform |
| Account and Billing | Plans, invoices, renewals, payment methods, and refund eligibility |
| Agents and Automation | Email Agent, Call Agents, building workflows, and managing what runs on your behalf |
| Integrations | Connected messaging channels and the API Integrations Hub |
| Troubleshooting | Common issues, error messages, and step by step guidance for resolving them |
| Security and Privacy | Data handling, permissions, access controls, and privacy settings |
Each of these topics links through to a full set of detailed guides inside the in-app Help Center. This page is your starting point and quick reference, not a replacement for the deeper, step by step content that lives directly inside the product where it is most useful, right next to the feature it is explaining, at the moment you actually need it.
Self-Service Exists Because It Is Genuinely Faster for You
We invest heavily in guides and a searchable Help Center, and it is worth being direct about why. It is not primarily about reducing how often you contact us, even though that is a real side effect. It is because finding an answer yourself, right now, at 11pm on a Tuesday when our support team is not immediately available, is almost always faster than waiting for a reply, even a genuinely fast one.
A well-built self-service resource means you are not stuck sitting on an open email thread for something you could resolve in thirty seconds if the answer were clearly written somewhere you could actually find it. That is a better outcome for you regardless of how quickly we would have responded.
This changes how we think about what good support actually means. A support team that measures itself purely by how quickly it closes tickets is missing half the picture. The fastest possible resolution is often one where you never needed to open a ticket at all because the answer was already there, easy to find, in plain language that matched how you were thinking about the problem.
When self-service genuinely cannot solve it, when something is actually broken, when your situation is specific enough that a general guide will not cut it, that is exactly when reaching a real person becomes the right move. Not a fallback we are quietly hoping you will not need, but the appropriate next step for a real problem that requires real human engagement.
Contact Support
Reach our team at support@kiraai.ai. When you write in, include your account email address and a clear description of what is happening. The more specific you can be about what occurred and when it occurred, the faster we can actually help rather than spending the first exchange just trying to understand the situation before we can begin addressing it.
If something broke in a specific sequence of steps, describe those steps. If you saw an error message, include it. If the issue started at a particular time or after a specific action, mention that. Every detail you include upfront is one less round of back and forth before we can get to the actual resolution.
Response times vary by plan. Business customers receive priority support handling, meaning their messages move to the front of the queue rather than waiting alongside individual user requests. If your team is on an eligible plan and response time is important to your operations, this is worth knowing about.
Service Status
We publish live operational status and full incident history on our status page. If something is wrong with the platform, you can check there first to see whether it is a known issue being actively worked on before spending time troubleshooting something that turns out to be on our end rather than yours.
If an incident affects your account or your data, we keep you updated throughout rather than going quiet while the investigation is ongoing. We would rather communicate early with incomplete information than stay silent and leave you wondering whether anyone is even aware something is wrong. Transparency during an incident is part of how we take it seriously, not just the resolution at the end.
Help Yourself, Faster
A few things worth knowing about that can get you to an answer more quickly than going straight to a support email for every question.
- The In-App Help Center contains step by step guides built directly into the product rather than on a separate site. Open it from within Kira to find guidance organized around the feature you are currently using, which is usually the fastest path to an answer for how-to questions.
- Voice Command and Chat let you ask Kira directly how to do something from within the platform. Sometimes the fastest path to an answer is simply asking the product itself rather than searching for a written guide about it.
- The Specifications and Use Cases pages give you a fuller picture of what Kira can actually do across its full feature set. If your question is less about something being broken and more about whether a capability exists at all, these pages are worth checking before reaching out to support.
How Our Help Content Improves Over Time
Help Center articles are not written once and left untouched while the product changes around them. That is how documentation goes quietly stale, technically existing but no longer accurately reflecting how the feature actually works, leaving people more confused after reading it than before.
We track which guides people find genuinely useful versus which ones result in people still needing to contact support afterward. The real measure of whether a help article is working is not whether it technically exists. It is whether it actually solved the problem for the person who read it.
That signal feeds directly into how we improve the content. Articles that consistently leave people needing to follow up get rewritten rather than left as-is because nobody got around to updating them. If you have ever read a help article and still had to email support anyway, that is exactly the kind of gap we want to close. If you encounter one and let us know which article it was when you write in, that feedback genuinely helps us improve it for everyone who comes after you.
What Happens After You Reach Out
It is worth being transparent about what actually happens once you send a message to support@kiraai.ai, because leaving that as a black box is not consistent with how we try to operate on transparency generally.
Your message gets reviewed against your account details and the specifics you have described. Where possible, we resolve things directly in a single exchange rather than bouncing you between multiple people who each need you to re-explain your situation from the beginning. If your issue requires deeper investigation, a bug that needs to be reproduced, an account-specific configuration problem, a payment issue that involves a third-party processor, we will tell you that is happening and keep you informed rather than leaving you wondering whether your message simply disappeared into a queue somewhere.
Our goal with every support interaction is a real resolution, not a closed ticket. Those are not always the same thing, and we try to hold ourselves to the former rather than the latter.
Frequently asked questions
Quick answers to common questions.
Email support@kiraai.ai with your account email address and a clear description of what is happening. Include as much relevant detail as you can upfront, what occurred, when it occurred, and any error messages you saw. The more specific your initial message is, the faster we can get to an actual resolution. Business customers receive priority handling on eligible plans.
Open Settings from within your Kira account to view your current plan, review past invoices, update your payment method, or make changes to your subscription. For information about refund eligibility and how to request one, see our Refund Policy.
Email support@kiraai.ai with a description of what happened, the steps that led to it so we can attempt to reproduce the issue on our end, the platform you are using (web, Mac, or Windows), and a screenshot if you have one available. The more detail you include upfront, the faster we can diagnose what went wrong.
Yes. We publish live service status and full incident history on our status page, which is updated in real time when an issue is identified and throughout the resolution process. If you are experiencing something unexpected, checking the status page first will tell you quickly whether it is a known platform issue being actively worked on.
Email support@kiraai.ai and let us know which article you tried and what it did not address. That feedback is genuinely useful to us because it tells us exactly where the content needs to improve rather than leaving us guessing. We would rather hear about a gap directly than have the same article quietly frustrate the next twenty people who encounter it.
Because you should not have to correctly guess which internal department owns your problem before you can start looking for an answer. Organizing around your actual goals removes that guessing step entirely and gets you to the right information faster regardless of how the work is divided internally on our end.
Response times vary by plan. Business customers on eligible plans receive priority handling and move to the front of the support queue. For all other plans, we aim to respond as quickly as possible and will always acknowledge your message so you know it has been received.