---
title: "From a customer’s bug report to a fix and a reply"
description: "A customer reports a bug by email. Tecla has the task ready. You run it, and Tecla finds the cause, opens a pull request and drafts the reply."
url: "https://www.usetecla.com/use-cases/customer-email-to-fix"
updated: "2026-11-15"
---

# From a customer’s email to a fix, and the reply.

A customer writes that the export does not work. Usually someone has to read the email, find the error, make an issue, fix the bug and answer the customer. Tecla finds the task in the email. When you run it, Tecla does each of those steps in the app where it belongs.

## The task

**Fix the export bug Northwind reported** (Email from Northwind’s support lead)

## What Tecla does when you run it

1. **Sentry:** Found the error behind the report, and when it started
2. **GitHub:** Found the cause in the code and opened a pull request with a test
3. **Linear:** Updated the issue with the cause and the pull request
4. **Gmail:** Drafted the reply to the customer, for you to approve

## What you do, step by step

1. A customer writes to you. You do nothing yet.
2. Tecla finds your task, and writes its plan.
3. You read the plan, and you run the task.
4. Tecla does the work in each app. You see each step.
5. You review the pull request, read the reply, and approve it.

Each task shows its plan before it starts, so you know what Tecla will do before you run it.

## Why one app is not enough

A coding agent needs you to describe the bug. An email assistant can only answer “we are looking into it”. Here the email, the error, the code and the issue are one piece of work, and Tecla has the context of all four.

The apps in this example: [Gmail](https://www.usetecla.com/integrations/gmail), [Sentry](https://www.usetecla.com/integrations/sentry), [GitHub](https://www.usetecla.com/integrations/github), [Linear](https://www.usetecla.com/integrations/linear).

## Questions

### Does Tecla merge the pull request?

No. It opens the pull request, and you review and merge it as you do with any other.

### Does Tecla need access to my code?

Yes, for this kind of task. You connect GitHub or GitLab with your own account, and Tecla sees what that account can see.

### Does Tecla answer the customer 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.
