How to Set Up a Helpdesk in Airtable with Claude AI

Most small business owners manage customer support in the messiest way possible. Facebook DMs here. Instagram DMs there. An occasional email thread. A sticky note somewhere about something someone asked.

If you have ever had a customer fall through the cracks because you genuinely forgot to follow up, this is a familiar problem.

I had the same setup for longer than I would like to admit. Until I built a proper helpdesk in Airtable and added a Claude skill on top of it.

Airtable is fundamentally a database. Which is exactly what a helpdesk is. A structured collection of records, each one representing a support ticket with fields for who asked, what they asked, what product they have, what stage the issue is at, and what the reply is.

The benefit over a DM inbox is that nothing disappears. Every ticket has a record. Every message in a thread is logged. You can see what is open, what has been resolved, and what has been sitting unanswered too long.

It is also searchable. When a customer comes back three months later saying they asked about something before, being able to search by their name and find the original thread is genuinely useful.

The helpdesk I built uses two tables in Airtable.

The first is Tickets. Each record is one support issue. It includes the customer name, email, which product they have, the issue description, issue category, SLA status, priority level, and a draft reply field.

The second is Messages. Each message is its own record, linked back to the parent ticket. This is how you build the full conversation thread. Each message has the sender (me or customer), the message text, the date, and any attachments.

This structure keeps tickets clean while preserving the full conversation history.

Customers do not log into Airtable. They use a form.

Airtable has a built-in form feature. You build a form that connects to the Tickets table, and when a customer submits it, a new ticket record is created automatically.

The form I use asks for name, email, which product they are asking about, and a description of their issue. Clean and simple.

I link to the form from my product delivery pages, so customers who need help know exactly where to go instead of hunting for a DM.

This is where it gets interesting.

I built a Claude skill that runs when I open the helpdesk in my daily workflow. It reads the open tickets, looks up the customer product details from my Products table, finds any relevant documentation from my Knowledge and Resources library, and drafts a reply.

The draft reply goes into the Draft Reply field on the ticket record. I review it. I edit anything that needs adjusting. I confirm the reply is accurate for the specific customer situation.

Then I send it.

I am not writing replies from scratch. I am reviewing and approving. The cognitive load is a fraction of what it was when I was starting from a blank screen every time.

This was something I added after realising I had no visibility into how quickly I was actually responding.

The SLA Status field is a formula that calculates how long a ticket has been open and flags whether it is within or outside my target response time. It is automatic. I do not have to manually check.

When I open my helpdesk view, any tickets that have been sitting too long are highlighted. They do not slip past.

The practical difference is not just time. It is the mental shift that comes from having things under control.

When support lives in DMs, every notification feels like a potential fire. You are always half-worried about something you might have missed.

When it lives in a proper system with an AI layer drafting replies, it becomes a manageable part of your day. Open the helpdesk, review the tickets, approve the drafts, done.

Support goes from being the thing that interrupts everything else to one predictable task in the day.

Airtable requires a paid account for some features, particularly the advanced views and charts. The free plan will get you started, but you will likely outgrow it.

Setting up the two-table structure and the form takes time if you are doing it from scratch. There is a learning curve to linking records between tables and getting the views set up in a way that is actually useful.

And the Claude skill layer requires a Claude account and some configuration. It is not a plug-and-play setup.

If you want something already built, the Helpdesk and Support System I sell includes the complete two-table setup, the submission form, the SLA formula, and the Claude skill. It is designed so you can install and use it without building anything from scratch yourself.

Do I need a paid Airtable account?

The basic setup works on the free plan. For charts, advanced views, and some automation features, a paid plan is helpful.

Does this work for just Etsy or any kind of business?

The structure works for any business selling digital products, services, or physical products. The ticket fields are generic and you adjust them for your specific context.

What do I need for the Claude skill to work?

A Claude.ai account is required. The skill files connect Claude to your Airtable base using the Airtable integration. Setup instructions are included with the product.

Can I use this without the Claude skill?

Yes. The Airtable structure works on its own as a plain helpdesk without any AI layer. The Claude skill is an add-on that saves time on drafting replies, not a requirement.

Will customers get automated replies?

No. The Claude skill drafts replies for your approval. Nothing is sent without you reviewing and confirming it. Every reply goes through you.