- Seven new automation patterns are now live across sales, support, operations, and marketing in the KOIRA marketplace.
- Each pattern targets a specific, named task — not a vague 'workflow' — so you know exactly what you're turning off your plate.
- Patterns are trained once from a plain-English description or a single walkthrough, then run on any website without needing an API.
- New ops patterns include schedule confirmation chasing and waitlist backfill — two tasks that eat disproportionate owner time for small service businesses.
- The sales follow-up cadence pattern now supports multi-touch sequences with conditional branching based on whether a lead opened, clicked, or replied.
- All new patterns feed into the workspace approval queue, so you stay in control until you're confident enough to let them run fully autonomously.
What the Marketplace Actually Is
The KOIRA marketplace isn't a library of pre-built integrations that require you to connect APIs and map fields. It's a collection of automation patterns — trained behaviors that know how to navigate real websites, read real data, and take real actions on your behalf, the same way you would if you sat down and did it yourself.
When a new pattern ships, it means we've built, tested, and refined a specific automated behavior until it's reliable enough to hand to any owner-operator without a technical setup conversation. You pick the pattern, point it at your situation, and it runs.
This August, we added seven new patterns. Here's what they are and who they're for.
New Sales Patterns
1. Conditional Lead Follow-Up Cadence
The 5-touch sales sequence we documented earlier this year assumed linear follow-up: touch 1, touch 2, touch 3, regardless of what the lead did. This new pattern adds conditional branching.
If a lead opens touch 1 but doesn't reply, the next message is warmer and more direct. If they click a link but don't book, the follow-up references what they clicked. If they go dark after touch 2, the sequence shifts to a re-engagement angle rather than continuing the original pitch.
This matters because flat cadences treat a lead who read your email three times the same as one who never opened it. The conditional pattern reads engagement signals and adjusts. It's trained once on your voice and your offer, then runs across every new inbound lead automatically.
Best for: Service businesses, consultants, agencies, anyone running inbound leads from a form or booking page.
2. Stale Pipeline Nudge
Deals sitting in your CRM past their expected close date don't need a new strategy — they need a nudge. This pattern monitors your pipeline for deals that have gone quiet beyond a threshold you set (say, 10 days without activity), then drafts and sends a follow-up that sounds like you wrote it that morning, not like a CRM automation.
The message references the specific deal context, the last touchpoint, and a clear next step. No generic "just checking in" language.
Best for: B2B service businesses, freelancers, anyone using a CRM who lets deals go cold because follow-up feels awkward.
New Support Patterns
3. Inbox Triage with Escalation Routing
This pattern reads your support inbox, classifies incoming messages by type (refund request, shipping question, product issue, general inquiry), drafts a reply for each, and flags anything that needs a human eye before it goes out.
The classification logic is trained on your actual message history, not a generic taxonomy. If your customers tend to phrase refund requests as "I'm not happy with my order," the pattern learns that framing rather than waiting for the word "refund" to appear.
Messages that hit escalation criteria — angry tone, legal language, repeat contact — get pulled into the approval queue with a summary instead of auto-sending. You review those; the rest go out.
This builds directly on the 80/20 escalation rule we've written about: automate the 80% that's routine, stay in the loop on the 20% that isn't.
Best for: E-commerce stores, subscription businesses, any owner handling more than 20 support messages per day.
4. Review Response Cadence
Responding to Google and Yelp reviews matters for local search ranking and for the humans reading them before they decide to book. Most owners know this. Most owners also let it slide for weeks.
This pattern monitors your review platforms, drafts a response for every new review within 24 hours, and queues it for one-click approval. Positive reviews get a warm, specific acknowledgment. Negative reviews get a calm, professional response that addresses the issue without being defensive.
The tone is trained on your voice. If you're a laid-back surf shop, the responses don't sound like a corporate PR statement.
Best for: Any local business with a Google Business Profile or Yelp presence — salons, restaurants, service shops, gyms.
New Operations Patterns
5. Schedule Confirmation Chasing
Appointment no-shows cost service businesses an average of 15–20% of booked revenue. Confirmation reminders help, but most booking tools send one generic reminder and stop there. If the client doesn't respond, nothing happens.
This pattern sends a confirmation request 48 hours out, then — if there's no response — follows up at 24 hours with a different message and a clear "reply YES or we may offer your slot" framing. If still no response at 4 hours, it flags the slot as at-risk and optionally begins backfilling from the waitlist.
The messages are written in your voice and reference the specific appointment. No "Dear Valued Customer" language.
Best for: Salons, clinics, personal trainers, any appointment-based business losing revenue to no-shows.
6. Waitlist Backfill
When a cancellation comes in, most businesses either scramble to fill it manually or just absorb the lost revenue. This pattern automates the backfill: it reads the cancellation, identifies the next eligible person on the waitlist, reaches out with the open slot details and a time-limited acceptance window, and books them if they say yes.
If the first person passes or doesn't respond within the window, it moves to the next. The whole chain runs without you touching it.
Best for: High-demand service businesses with active waitlists — popular salons, fitness studios, specialty clinics.
7. Invoice Chase Sequence
Chasing unpaid invoices is one of the most uncomfortable tasks in any service business. Most owners either send one reminder and hope, or let it drag for weeks before following up again.
This pattern sends a structured three-touch chase: a polite reminder at day 3 past due, a firmer follow-up at day 10, and a final notice at day 21 that references next steps. Each message is drafted in your voice and references the specific invoice, amount, and project.
The sequence stops automatically when payment is received. You never have to manually track which clients are overdue.
Best for: Freelancers, agencies, contractors, any service business invoicing clients on net terms.
How These Patterns Fit the Broader Framework
Every pattern in the marketplace is designed to operate at L4 autonomy — it runs end-to-end on its own, but surfaces anything uncertain into your approval queue rather than guessing. As you build confidence in a pattern's outputs, you can dial down the approval frequency until it runs fully autonomously.
This is different from what most automation tools offer. Zapier requires APIs on both ends. Traditional RPA breaks when a website changes its layout. Most AI tools run a vision pass on every action, which gets expensive fast.
KOIRA patterns are trained once — from a plain-English description or a single walkthrough — and self-heal when the sites they touch change their structure. The cost per run stays low because the model doesn't re-interpret the world from scratch every time; it knows what it's doing.
If you want to understand the technical distinction in more depth, this post on no-API automation covers the architecture.
What's Coming Next
The patterns shipping in September are focused on marketing: automated blog brief generation from search gap analysis, Google Business Profile post scheduling with seasonal variation, and a social posting pattern that adapts content format per platform rather than cross-posting the same text everywhere.
If there's a specific busywork task you want to see as a pattern, the request form is in your workspace settings. The most-requested patterns get prioritized for the next release cycle.
Activating Any of These Patterns
All seven patterns are live in the marketplace now. To activate one:
- Go to your KOIRA workspace and open the Marketplace tab.
- Filter by function (Sales, Support, Operations, Marketing) or search by task name.
- Select the pattern and walk through the setup: describe your voice, point it at the relevant tool or website, and set your approval preferences.
- Run a test batch and review the outputs in the approval queue.
- Adjust any tone or logic settings, then set the pattern to run on its schedule.
Most patterns are live within 15 minutes of setup. The conditional sales cadence takes slightly longer because it needs a sample of your existing messages to calibrate voice matching.
The goal with every release is the same: fewer tasks that eat your evenings, more time on the work only you can do.
“Every pattern in the marketplace is designed to operate at L4 autonomy — it runs end-to-end on its own, but surfaces anything uncertain into your approval queue rather than guessing.”
| Area | Doing It Manually | With a KOIRA Pattern |
|---|---|---|
| Lead Follow-Up | Send the same sequence to every lead; forget to adjust after they engage | Conditional cadence reads engagement signals and branches automatically |
| Stale Deals | Notice a deal went cold two weeks later; send an awkward 'just checking in' | Pattern detects inactivity and sends a context-specific nudge at the right moment |
| Support Inbox | Read every message, draft replies one by one, miss the escalations that need attention | Pattern classifies, drafts, and routes — escalations go to queue, routine replies go out |
| Review Responses | Respond to reviews in batches when you remember, weeks after they post | Pattern drafts a response within 24 hours of every new review, queued for one-click approval |
| Appointment Confirmations | One generic reminder; no-shows absorb 15–20% of booked revenue | Multi-touch confirmation chase with at-risk flagging and automatic waitlist backfill |
| Invoice Chasing | Send one reminder, feel awkward following up, let overdue invoices drag for months | Three-touch chase sequence runs on schedule, stops automatically when payment clears |
How to Activate a New Marketplace Pattern in KOIRA
- 01Open the Marketplace tab in your workspace. Log into your KOIRA workspace and navigate to the Marketplace tab in the left sidebar. All published patterns are listed here, filterable by function: Sales, Support, Operations, or Marketing.
- 02Select the pattern that matches your task. Use the function filter or search by task name — for example, 'invoice chase' or 'review response.' Each pattern card shows the specific task it handles and the type of business it's built for.
- 03Walk through the setup: describe your voice and point it at your tools. Each pattern's setup screen asks for the context it needs: a description of your tone, sample messages if relevant, and the website or tool it should operate on. You can type this in plain English — no technical configuration required.
- 04Set your approval preferences. Decide how much you want to review before outputs go out. Start with full approval on every action if you're new to the pattern, or set a threshold — for example, approve only messages flagged as uncertain — if you're confident in the pattern's calibration.
- 05Run a test batch and review the outputs. Trigger a test run against a small set of real data — a handful of leads, a few recent support messages, or your current overdue invoices. Review the outputs in the approval queue and note anything that needs adjustment.
- 06Adjust tone or logic settings based on the test. If the voice doesn't sound right or the branching logic is too aggressive, update the pattern's settings and run another test. Most patterns settle within one or two iterations.
- 07Set the pattern live on its schedule. Once you're satisfied with the outputs, set the pattern to run on its configured schedule — hourly, daily, or triggered by a specific event like a new form submission or a cancellation. It runs from here without you touching it.