teclaIntegrationsTry for free

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.

Download for Mac

Free to start. No card needed.

Fix the export bug Northwind reported

GmailEmail from Northwind’s support lead

  1. SentryFound the error behind the report, and when it started
  2. GitHubFound the cause in the code and opened a pull request with a test
  3. LinearUpdated the issue with the cause and the pull request
  4. GmailDrafted the reply to the customer, for you to approve

What you do, step by step

Each task shows its plan before it starts, so you know what Tecla will do before you run it. You can stop the task at any moment, or tell Tecla to do it differently.

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.

These apps are an example. Tecla does the same work with the apps you use. Click an app to see what Tecla does in it. See all the apps

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.

More use cases