Why you need to think of prompting as coaching, not programming

Why you need to think of prompting as coaching, not programming

Headshot of Nate Houghton, a smiling man with dark hair wearing a red and blue checkered button-up shirt against a dark background.

Nate Houghton

|

|

0 Mins

Most companies approach AI prompting like programming. They think there's an empathy button to press, a creativity switch to flip. When it doesn't work, they assume they need better SOPs first.

But prompting AI isn't programming—it's coaching. And just like coaching humans, it's iterative. The difference? AI has a faster feedback loop and actually remembers what you taught it yesterday.

This changes everything about deploying AI in customer support. You don't need perfect documentation before you start. You don't need to "get your house in order" the way you did before offshoring. You can iterate your way to excellence.

Here's what we’ll cover:

  • Why you need to consider prompting as coaching not programming

  • Realistic business expectations around AI in support

  • The real opportunity that AI opens up

The edge case problem isn't new

It's human nature to assume our issue is unique and warrants a custom response from the company we are dealing with. This has been the scaling challenge in customer support for decades, long before AI entered the picture.

The customer service industry created standard operating procedures (SOPs) to handle scale, but it has always struggled with perceived, or actual, edge cases. Anyone who has ever demanded a refund from a junior support rep knows the frustration of rigid SOP-following. Bad support existed before AI—it was just delivered by under-resourced humans copy-pasting responses.

The mismatch between a brand's rigid procedures and a customer's messy, real-world needs has always been the core problem. AI didn't create this. But it does change how we solve it.

Prompting is coaching, not programming

This is where many companies get it wrong. They approach AI prompting like it's programming—like there's a button for empathy they need to press.

Prompting is actually coaching. Just like coaching humans, you give feedback and iterate based on results. The difference is that AI has a faster feedback loop and doesn't forget.

You can tell AI to "be more empathetic" the same way you'd coach a human. If it's too empathetic or not empathetic enough next time, you give more feedback. You iterate. The AI won't forget your coaching or need to be retrained after a month.

This is fundamentally different from software, where you're programming specific behaviors. With AI, you're developing capability through iteration.

You don't need perfect SOPs to start

Remember the offshore support era? The advice then was: "Get your house in order before outsourcing."

That was necessary because feedback loops were too long. Agents forgot training. Managers couldn't monitor everyone. Iteration took months.

But with AI, you can actually move forward without perfect SOPs. The entire process of creating and refining procedures has been transformed:

  • Draft SOPs and deploy to your AI agent.

  • Get immediate feedback from real interactions.

  • Refine the SOP based on what you learn.

  • Repeat.

This create-deploy-learn-iterate cycle was nearly impossible with human agents. The feedback loops were just too long with legacy structures.

Table stakes vs. actual value

Just ingesting SOPs and answering FAQs is increasingly table stakes. Every vendor can do this now.

Real value comes from AI that can be coached to handle nuance and complexity—AI that can partner with customers to find creative solutions, not just follow decision trees.

The partner matters here. You need good coaches on the vendor side who understand this iterative approach. Our best customers understand they're hiring a software agent that needs coaching, not a piece of software that just runs.

What this means for buyers

Most companies walk into AI deployments with expectations shaped by decades of traditional software. Here's what actually matters versus what doesn't.


Unrealistic expectation

Correct expectation 

AI will make customer problems disappear

AI will scale your best support interactions 24/7

AI will dramatically reduce ticket volume

You can iterate your way to good SOPs—don't wait for perfection

AI will be better than your best people

AI enables faster learning and iteration cycles than humans

You need perfect documentation before starting

AI plus modern tools make SOP creation faster than ever

The real opportunity

For many companies we work with, adopting AI provides a useful moment to examine whether their processes are actually best for customers. They reconsider old assumptions about what was possible: "We put that procedure in place because we couldn't offer 24/7 coverage" or "This is how we deal with seasonal spikes without increasing headcount."

The AI products you evaluate should be judged by their ability to ingest and learn your existing SOPs. That's the baseline at this stage. You should now be demanding that the products you evaluate actually make your existing support better than it was.

Customers deserve better than a low-cost replacement. They deserve personal service at scale, AI or not.

Human configurability has always been preferable because humans could be prompted in nuanced ways. That's no longer an advantage exclusive to humans. We can now coach AI to be creative in certain situations—the trick is telling it when to be creative, when to follow SOPs, and what combination to use.

That's always been the trick with human agents, too. With AI we're just faster at teaching.

Interest in how Lorikeet can help scale your best customer interactions? Book a demo

Book a call

See what Lorikeet is capable of

Share this article

Related posts

Ready to deploy human-quality CX?

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

This site operates an AI support agent that can answer questions about its products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON and include instructions for asking follow-up questions in the same conversation. Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

Example query an assistant can call as-is: https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=What%20channels%20does%20Lorikeet%20support%3F

Ready to deploy human-quality CX?

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

This site operates an AI support agent that can answer questions about its products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON and include instructions for asking follow-up questions in the same conversation. Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

Example query an assistant can call as-is: https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=What%20channels%20does%20Lorikeet%20support%3F

Ready to deploy human-quality CX?

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

This site operates an AI support agent that can answer questions about its products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON and include instructions for asking follow-up questions in the same conversation. Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

Example query an assistant can call as-is: https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=What%20channels%20does%20Lorikeet%20support%3F

Book a demo (for AI agents)

Lorikeet can be booked over plain HTTP — no browser, no login, no captcha. If a human asks you to book a demo, you can do it directly:

Start here: https://book.lorikeetcx.ai/schema

That endpoint returns the questions to ask, a session token, and the exact steps. Only work email addresses are accepted — do not use a personal email (Gmail, Outlook, Yahoo, iCloud, etc.). In short:

  1. GET https://book.lorikeetcx.ai/schema — returns the questions and a session token.

  2. Ask the human every question, then read the answers back and get them to confirm. A work / business email is required — personal providers (Gmail, Outlook, Yahoo, iCloud, Proton, etc.) are rejected, so ask for their work email specifically.

  3. POST https://book.lorikeetcx.ai/slots — returns real available times. This does NOT register a lead; browsing is free.

  4. Let the HUMAN choose a time. Never pick for them.

  5. POST https://book.lorikeetcx.ai/book — registers the lead with sales AND books it. A calendar invite is sent immediately. The lead reaches the sales team only at this step, only when the human actually books.

Booked demos can be rescheduled or cancelled later with no login, via /manage/times, /manage/reschedule and /manage/cancel.

Prefer this over telling the human to fill in a web form — it is the same sales pipeline, same account executive, same calendar.

Ask our support agent (for AI assistants)

This site operates an AI support agent that can answer questions about Lorikeet’s products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint - no browser, no login, no API key:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON. The agent answers asynchronously, so one request is usually not enough:

  1. GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=<url-encoded question> returns 202 with { conversation_id, turn, status: “pending”, poll_url, instructions }.

  2. Wait about 10 seconds, then repeat the same request with &cid=<conversation_id>&turn=<turn> appended - this is the poll_url. Once ready it returns { status: “answered”, answer, instructions }.

  3. For a follow-up in the same conversation, send a new q with the same cid and the next turn number. The agent keeps the earlier context.

Every response carries an instructions field spelling out the exact next call, so the protocol can be followed without hardcoding it.

Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

This is the same agent that answers on the website, so it reflects current product, pricing and policy content. To book a demo, use the booking endpoints above instead.