---
title: "An AI assistant for customer support, beyond the reply"
description: "Before you can answer a customer, somebody has to find the bug or make the refund. Tecla has that work ready as a task, and does it when you run it."
url: "https://www.usetecla.com/blog/ai-assistant-for-customer-support"
author: "@miguelaeh_"
published: "2026-11-14"
updated: "2026-11-15"
---

# An AI assistant for customer support, beyond the reply

Before you can answer a customer, somebody has to find the bug or make the refund. Tecla has that work ready as a task, and does it when you run it.

Most AI tools for support write the reply to the customer. But the reply is usually the last step of a ticket, and the smallest one. Before you can answer, somebody has to do something in another tool: find a bug, make a refund, or ask a colleague who knows the answer.

For example, a customer called Omar writes on Monday that his CSV export fails. You can answer in one minute that you are looking into it. The real work is to find the error, find the change that caused it, and get it fixed. That work is in three tools that the support team doesn’t own, so Omar’s ticket stays open for a week while it waits for an engineer.

This post shows what Tecla does with a ticket like Omar’s, and with two other common kinds.

## The short answer

Tecla is a proactive AI assistant for work. It finds and tracks your tasks in the conversations with your customers, in your email, Slack and work apps. When you open Tecla, each ticket that needs work is already a task in your list, with the customer’s history and all the context. You click Run on the ones you want. Tecla does the work behind the ticket in the tool where it belongs, and then it drafts the reply for you to approve.

## A ticket about a bug: Tecla finds the cause and opens the fix

When Omar’s email arrives, Tecla adds the task “Answer Omar about the export bug” to your list. The plan of the task has four steps, and you can read them before you start it.

First, Tecla finds the error in [Sentry](https://www.usetecla.com/integrations/sentry) and the day it started. Second, it finds the change in the code on [GitHub](https://www.usetecla.com/integrations/github) that caused the error, and it opens a pull request with a fix and a test. Third, it updates the issue in [Linear](https://www.usetecla.com/integrations/linear), so that engineering sees the same information as support. Last, it drafts the reply to Omar, which says what was wrong and when the fix will ship. Your engineers review the pull request as they review any other. See [a customer’s email to a fix](https://www.usetecla.com/use-cases/customer-email-to-fix), step by step.

## A ticket about money: Tecla checks the payments and makes the refund

Suppose another customer writes that you charged her two times in March. To answer, you have to look at her payments and read your refund policy. Tecla does both in [Stripe](https://www.usetecla.com/integrations/stripe) and in your documents, and the plan of the task says which of the two payments it will refund and why. You read the plan and run the task. Tecla then makes the refund and drafts a reply with the amount and the date.

## A question that needs an expert: Tecla looks for the answer your team already gave

A third customer asks if your API supports bulk updates. Most questions like this one were answered before, by an engineer in a Slack thread or in a document. Tecla has read those, so it drafts the answer from what your team said the last time. If nobody has answered the question before, Tecla asks the right person in [Slack](https://www.usetecla.com/integrations/slack), waits for the answer, and then drafts the reply.

## Each task comes with the customer’s history

A reply that asks a customer for something that they already told you makes them angry, and with good reason. Tecla builds a memory from all your apps, so the task about Omar has his history attached: his plan, his last three conversations in [Intercom](https://www.usetecla.com/integrations/intercom), and the other bug that he reported in March. The draft reply uses that history. It doesn’t ask Omar which export he means, because he said it in his first email.

## No reply goes to a customer before you read it

Each task shows its plan before it starts, so you know what Tecla will do in Stripe or in GitHub before it does it. A reply to a customer always waits for your approval. You can change the text, approve it, or stop the task.

## Questions

### Is Tecla a chatbot for my customers?

No. Your customers do not talk to Tecla. Tecla works for the person who answers them: it does the work behind the ticket and drafts the reply.

### Does Tecla answer customers without asking me?

No. A message or an email in your name waits for your approval before it goes out. You can edit it first.

### Which support tools does Tecla work with?

It finds your tasks in Gmail and Intercom, and it works in the tools behind the ticket, such as Stripe, Sentry, GitHub, Linear and Jira. [See all the apps](https://www.usetecla.com/integrations).

### Can Tecla fix a bug that a customer reported?

It can find the cause and open a pull request with a test. Your engineers review it and merge it as they do with any other.

### What does Tecla cost?

It is free to start, with no card needed. Then it costs $47 a month, or you buy credit packs from $8. See [the pricing](https://www.usetecla.com/pricing).
