DEV Community

Cortex AI
Cortex AI

Posted on Originally published at buildcortex.dev

How an AI agent for Tekmetric works

An AI agent for Tekmetric connects one of two ways: an app approved by Tekmetric that the shop admin authorizes under Shop Settings, Integrations, or a webhook an admin adds themselves. API credentials are not self-serve (one review reports a wait of 2 to 3 weeks). Tekmetric already covers texting, reminders and campaigns; an agent adds follow-up judgment on estimates and declined work, with a service advisor approving every message.

An AI agent for Tekmetric is a small program that watches what happens in your shop (an estimate nobody answered, a repair order that finished while the car sat on the lot, declined work for a customer who is due back) and drafts the next step for a service advisor to approve. In Tekmetric it can reach your data in two ways: through an app Tekmetric has approved, which your shop admin authorizes, or through a webhook an admin adds themselves. What it should not do is send anything to a customer without a person reading it first.

This guide covers what Tekmetric already does, where the gaps are, how an agent connects, and what to keep with your advisors.

What Tekmetric already does

Check this first so you don't pay for something you already have.

Tekmetric's integrations page says it has 70+ integrations and lists two-way texting, text-to-pay, digital vehicle inspections, automated reminders, scheduled campaigns and Google review requests. Partners such as ShopGenie and AutoBucks add things like service reminders and a text-based rewards program. We did not find AI features described on that page.

So the reminders and campaigns are already there. They run on rules: this message, at this time, to this list.

Where the built-in tools stop

A reminder fires on a date. It doesn't know that the customer who declined a suspension job last month asked about financing, or that two estimates are sitting unanswered on the same day your advisor is out.

The gaps we hear about most:

  • Estimates that go quiet. Sent, viewed, never answered, then forgotten.
  • Declined work. Inspection findings the customer put off, never revisited at the right moment.
  • Finished cars that wait. A repair order marked complete and a customer who hasn't been told.
  • Money and parts elsewhere. Balances in QuickBooks, parts in a supplier portal, leads in your phone system.
  • The owner's morning view. Cars in, estimates open, cars ready, balances owed.

What an agent does around Tekmetric

These are illustrations of the pattern, not a client story.

Agent Starts when Reads Drafts Person approves
Estimate follow-up An estimate has no response after a set number of days Estimate lines, vehicle, notes, history A personal text or a call reminder, ranked by dollar value Service advisor
Declined work revisit A customer is due back and has open declined items Declined lines, mileage, last visit A message naming the specific item Service advisor
Ready for pickup A repair order is complete and the car is still there Repair order status, contact A pickup message Front desk
Owner morning report Every morning Orders, estimates, balances One summary None, it reads only

How an agent connects to Tekmetric

Two routes exist, and they are quite different.

  1. An approved app, authorized by your admin. Tekmetric points developers to an application page. One third-party review reports that credentials are not self-serve: they need an active paid subscription and manual approval from Tekmetric that typically takes 2 to 3 weeks, and they use OAuth 2.0 client credentials. It also reports that each query returns at most 25 records, so reading a whole shop's history takes many requests. That review is published by a company that sells managed API layers, so confirm these details with Tekmetric. Once a connected app exists, the shop admin grants it access: Shop Settings, then the Integrations tab, then Manage, then Grant Access. Revoking it works from the same screen.
  2. A webhook you add yourself. A partner's setup guide shows that an admin can add a webhook under Settings, then Integrations, and that webhooks deliver appointment and repair order updates in real time, instead of waiting for an hourly sync. We found no public list of events, so ask Tekmetric which ones exist before building on them.

Webhooks tell an agent something changed, which suits follow-up. A good agent then reads the record, checks it hasn't already acted on that event, and drafts. Events can repeat, and a careless build messages the customer twice.

Connecting ChatGPT to Tekmetric

We found no native ChatGPT or Claude connector. An assistant would need approved API access or a webhook feeding it, plus a place for a person to approve drafts. That last part is what turns a chatbot into something safe to put near customers.

Setup steps and what you need

  • A Tekmetric admin who can grant access and add integrations.
  • Two or three jobs in order. Quiet estimates and declined work are usually first.
  • Access to the other systems: phone provider, QuickBooks, review accounts.
  • One advisor per agent approving drafts for the first few weeks.

Start with a person approving every draft and loosen it only after you've read enough to trust it. We explain the model in human-in-the-loop AI.

Limits and risks

  • Safety work stays human. An agent never tells a customer a car is safe to drive or talks anyone out of a brake or steering repair.
  • Prices and warranty. Discounts, goodwill repairs and warranty calls are the advisor's.
  • Double messages. If Tekmetric's automated reminders and an agent both text about the same car, pick one per stage.
  • Wrong customer. Match on phone number and vehicle, not just a name.
  • Upkeep. Credentials and events change. Someone has to own that, which is the reason for managed AI operations.

Where Cortex fits

Cortex builds AI agents that work inside the software you already run, with a person approving anything that goes to a customer. We are not a Tekmetric partner or certified app, and we'll say so when Tekmetric's own tools are enough. See what we connect on integrations and how this looks for auto repair. For recovering work that fell off the board, see declined work. If your shop runs another system, read AI agents inside AutoLeap.

The free AI Operations Audit looks at your shop software, phones and books in 30 minutes and tells you which job to hand an agent first.

Questions people ask

Does Tekmetric have AI built in?

Tekmetric's integrations page lists two-way texting, automated reminders, scheduled campaigns, Google review requests and digital vehicle inspections. We did not find AI features described on that page.

Does Tekmetric have an API?

Yes, but it is not self-serve. Tekmetric sends developers to an application page, and one third-party review reports it needs an active paid subscription plus manual approval that typically takes 2 to 3 weeks.

Can I connect ChatGPT to Tekmetric?

We foun

Top comments (0)