Choose an action… Add tags Remove tags Turn a capability on/off Ticket-logging policy PSA account-status gate Duplicate-ticket checking Device lookup Copy knowledge-base articles Copy setup from another customer Apply a saved setup template Change plan (billing) Review… Clear selection

Portal Branding GROWTH

This brands this KYRA bot portal — your name and logo replace KYRA's in the header for everyone in your MSP. It does not affect ConnectWise, HaloPSA, NinjaOne, Jira or any other third-party portal.

Save

Engineers' Teams support channel

When a customer needs a person, KYRA posts a claimable card into your own Teams channel so any engineer can pick it up and talk to the customer from Teams — you never have to be in the loop.

Loading…

Download KYRA Teams app Generate connection code Disconnect channel

API access

Issue API keys so your own dashboards and tools can read customers, usage and incidents — and trigger announcements — through KYRA's public API (/api/v1). Keys are shown once at creation and are rate-limited to 120 requests/minute. See Help centre → Public API.

Generate key

Loading…

Connect KYRA as an MCP server

Add KYRA to an AI agent (Claude, or any Model-Context-Protocol client) as a custom MCP server. The agent can then read your customers, usage, KPI metrics and incidents — and trigger announcements — using an API key from above. Same Bearer-key auth and 120 req/min limit as the REST API; no new access is granted.

https://kyra-bot.azurewebsites.net/api/mcp Copy URL

Transport: streamable HTTP (POST, stateless). Header: Authorization: Bearer <key>. Tools: list_customers, get_customer, get_usage, get_metrics, list_incidents, send_broadcast.

Scheduled announcements

Send a message to your customers' end users now or on a repeat. If a scheduled send is missed (the app was asleep, or you disabled it for a while) KYRA sends the next one due — it never fires a backlog at your users.

OnceEvery dayEvery weekEvery month Schedule

Applies to the customers you tick below. Times are your browser's local time.

Planned maintenance windows

Tell end users about planned work, and KYRA sends the all-clear automatically when it finishes. While a window is open the bot knows about it — it will say the work is expected and give the finish time, rather than troubleshooting it as a fault. This is not the same as pausing a bot: KYRA keeps answering throughout, and unrelated problems are still handled normally.

Tell end users Add window

KYRA Support access

Let the KYRA support team securely view your account to help with an issue. Access is view-only by default, expires automatically after 72 hours, and you can revoke it at any time. Every support session is recorded in your Activity log.

Loading…

Error detail requests

When something goes wrong, KYRA support sees the error and which of your customers it affected — but never your users' names or their conversations. If they need the full detail to fix it, they'll request time-boxed access here for you to approve.

Help improve KYRA — share failed chats

When KYRA can't resolve a chat (it errors, or can't answer), you can share it with the KYRA team so we can make the bot better. We only receive these once you switch this on. The question and a short transcript are stored encrypted, and end-user names, emails and IDs are stripped. Turn it off any time.

Raise a ticket

Raise and track support requests with the KYRA team directly from here.

Details

Loading…

Your service desk contact info

KYRA shares this with end users when they ask how to escalate an issue or contact you directly, or ask about out-of-hours support. Applies to every one of your customers.

Save contact info

Ticket logging

Choose how much of KYRA's own activity is logged to your PSA. Applies to every customer. A user who explicitly asks KYRA to raise a ticket is always honoured, whatever you pick here.

Log everything
Raise a ticket for every genuine support issue KYRA handles — even ones it resolves itself. A full record for reporting and billing. Actions & escalations only (recommended)
Log a ticket only when KYRA escalates an issue it can't resolve, or performs a Microsoft 365 change. Questions it answers itself are not logged. Log nothing
KYRA never opens a ticket on its own. It still answers, runs actions, and can hand off to a person.

Save ticket logging

Technician Copilot

When KYRA raises a ticket it couldn't resolve, it drafts a suggested resolution for the engineer — grounded in the customer's knowledge base / IT Glue / Hudu docs and similar resolved tickets, never the public web — and posts it as a private note on the ticket (never shown to the end user). Advisory only; KYRA never runs the steps. Off by default; can be overridden per customer on their page.

Save copilot setting

SLA tracking & breach alerts

KYRA checks every connected customer's PSA every 15 minutes and warns you before open tickets breach their resolution target. Set the target hours per priority — leave a target at 0 to ignore that priority.

Save SLA settings

Refresh

Open tickets approaching or past their SLA target, per customer — refreshed automatically every 15 minutes.

Loading…

Proactive incident detection

KYRA watches for spikes of similar tickets across your customers. If the same type of issue is raised several times in a short window, it flags a possible incident so you can get ahead of a wider outage.

Save incident settings

Refresh

Clusters of similar tickets detected recently, per customer.

Loading…

Major-incident comms

Declare a known major incident (an outage you're already aware of). KYRA broadcasts the status to the affected customers' end users in Teams and Slack, and — while it's open — tells anyone who reports the same issue that it's a known incident instead of raising a duplicate ticket.

Affected customers (none ticked = all customers)

Declare incident

Customer satisfaction (CSAT)

After KYRA raises a ticket it asks the end user "Was this chat helpful?" (👍 / 👎) in Teams and Slack. Ratings roll up here and into your Analytics & ROI report.

Save CSAT settings

Compose & send

Send now or schedule for oncedailyweeklymonthly Schedule

For planned-maintenance windows and major-incident comms (with bot-awareness), use Service Desk → Incidents. Email templates below are copy-and-send from your own mail.

Refresh

Ended	Customer	User	Channel	Handled by	Outcome
Loading…