Wikett
Book a demo

AI customer support

Support that fixes the bug, not just the ticket.

Wikett handles frontline requests, backed by data from your own systems. When a ticket needs engineering, it finds the root cause in your logs, code and deploys, pages the team that owns it, and keeps your customer updated until it’s fixed.

See how it works

Email, website chat and WhatsApp. Works inside your help desk.

Works with the tools you already run

  • Zendesk
  • Freshdesk
  • Intercom
  • HubSpot
  • Datadog
  • Splunk
  • GitHub
  • PagerDuty
  • Slack

The gap

Support AI stops at the help center. AI SRE starts at the alert.

Technical tickets fall in between. They wait in a queue, get routed by guesswork, and engineers start the investigation from scratch.

Support AI

Talks to your customer, but stops at docs and simple actions. Anything technical goes back to a human.

Wikett runs the whole loop

  1. 01Clarify the ticket with the customer
  2. 02Investigate logs, traces, code and deploys
  3. 03Page the team that owns the service
  4. 04Raise the fix for review
  5. 05Close it with the customer

AI SRE

Investigates production, but only from internal alerts. It never talks to the customer who noticed first.

Products

One engine, two products.

For routine questions

Wikett Core

Answers order, account, how-to and eligibility questions from your documents and systems, and applies your rules exactly.

  • Connects to your ERP, CRM, order system and internal APIs, read-only
  • No-code rules for return windows, pricing tiers and order minimums. The rule decides, not the model
  • Every answer cites its source. Low confidence goes to a person
  • Spots engineering-bound tickets, packages the IDs, timestamps and affected users, and creates the ticket in your help desk
Setup daysBuilt for Head of Support

For hard technical tickets

Wikett Pro

Works a ticket end to end, like a senior support engineer with read access to production.

  • Traces request IDs through logs, metrics, traces and recent deploys
  • Every finding links to the query behind it, one click from the evidence
  • Finds the owner from CODEOWNERS and on-call, then pages them with evidence
  • Groups the same issue across customers into one incident
Setup weeksBuilt for Support + Engineering

How it works

From ticket to fix in one thread.

01Core

Clarify

Asks once for request IDs, timestamps, screenshots and how many users are affected.

02Core

Hand off

Spots tickets that need engineering, packages everything it gathered and creates the ticket in your help desk.

03Pro

Investigate

Narrows systems with your service map, traces the request and compares error rates with baseline.

04Pro

Route

Pages the owning on-call in PagerDuty, Opsgenie or Slack with the evidence and customer impact.

05Core

Close

Confirms recovery and sends the customer a plain-language resolution on their channel.

Read-only everywhere. The only things Wikett writes are messages and tickets. In a later phase, Pro will also draft fix PRs that your team reviews and ships through your own CI/CD.

Trust and security

Built to be right, and to say when it isn’t sure.

A confident wrong answer to a customer is worse than no answer. Wikett is designed around that.

  • Evidence you can openEvery claim links to the query that supports it, so an engineer can check it in one click.
  • Human approvalReplies that state a root cause or ETA need a support lead’s approval until your account passes its accuracy gate.
  • Least privilegeRead-only credentials per source under Wikett’s own short-lived identity. Revoke any source at any time.
  • Your data stays yoursPII and secrets redacted before any model call. Zero-retention agreements with model providers. Strict isolation between customers.
  • Untrusted inputCustomer messages are treated as data, never as instructions. Only allow-listed actions.
  • Full audit trailEvery query, rule decision, message and approval is logged and exportable. SOC 2 Type I in progress.

What we hold ourselves to

The bar for every design partner.

98%+

Core answer accuracy on audited samples

<1 min

First response in chat, under 5 minutes by email

60%+

Technical tickets where the root cause is found

2×

Faster median resolution on technical tickets

These are the targets we commit to with design partners, measured on each account’s own tickets.

Pricing

Pay for resolutions, not seats.

Core

  • Platform fee with included resolutions
  • Free replay on your past tickets before go-live

Pro

  • Billed only when the root cause is found or an evidence-backed ticket is routed
  • 15 free investigations once Core has been live for 30 days
  • Every result shows the engineer time it saved
No per-seat pricingHard monthly caps you setDesign-partner pricing, subject to change

Book a demo

See how Wikett would handle your support queue.

Tell us about your help desk and the tickets that take longest to resolve. We’ll walk you through how Wikett handles them, from the first reply to the root cause.