AI-powered IT support

The helpdesk that
triages itself.

Every ticket is categorised, prioritised, and put on an SLA clock the moment it lands. When something's too vague to act on, TicketWhip asks the submitter for what's missing — and escalates to a human when it stops making progress.

Runs in your own Firebase project. Your data stays yours.

4priority tiers, assigned automatically
3AI providers — Gemini, OpenAI, or Claude
0API keys in your source tree

How it works

  1. Someone submits a ticket

    Through the portal, the AI assistant, or plain email — inbound mail becomes a ticket and replies thread back into the conversation.

  2. The AI triages it

    Category, priority, and an SLA deadline in business minutes — not wall-clock, so a Friday-evening P3 isn't breached by Monday standup.

  3. Gaps get chased automatically

    Too little detail to act on? The AI asks for specifics and pauses the clock. After a configurable number of unanswered rounds it stops asking and hands the ticket to a person — no silent dead ends.

  4. Your team handles what's left

    Agents get a live queue, drafted replies, knowledge-base matches, and Slack alerts before an SLA breaches rather than after.

What's in it

AI triage, your provider

Gemini, OpenAI, or Anthropic Claude — chosen from a dropdown, switched without a redeploy. Keyword fallback keeps triage working if the model call fails.

SLA that respects business hours

Per-priority targets counted in working minutes, with your schedule and holidays. Breach warnings fire to Slack and email before the deadline.

Self-service that deflects

A conversational assistant answers common questions and surfaces knowledge-base articles before a ticket is ever created — and reports what it deflected.

Email in, email out

Confirmations, reply notifications, and satisfaction surveys. Everyone controls which of those they receive.

Directory sync

Google Workspace SSO with domain restriction, nightly user sync, or CSV import. Roles carry into Firebase custom claims and Firestore rules.

Keys in Secret Manager

Every credential lives in Google Secret Manager, managed from the admin console and write-only — the UI never reads a value back.

Request access

Tell us a little about your team and we'll get back to you. This form doesn't create an account — a human reads it.