- Seven new automation patterns shipped across sales, support, ops, and marketing in July 2026 — no code or API setup required to activate any of them.
- The new sales patterns cover inbound lead qualification and deal-pipeline nudges, two of the highest-leverage tasks owner-operators consistently do manually.
- Support inbox triage now has a pattern that sorts, labels, and drafts replies by urgency tier — cutting average first-response time without adding headcount.
- The scheduling confirmation pattern for operations eliminates the back-and-forth that kills 20–40 minutes per booking for service businesses.
- All patterns default to L4 autonomy (runs end-to-end, owner spot-checks via approval queue) — you can dial back to L3 manual gating if you want to review every output.
- Patterns self-heal when the sites they touch change layout or structure, so a Shopify redesign or Gmail update won't break a running workflow.
What the Marketplace Is, Briefly
The Koira marketplace is where pre-built automation patterns live. A pattern is a workflow template that already knows the general shape of a task — say, "follow up with a lead who filled out a contact form" — but learns the specifics of your business from a plain-English description or a single walk-through. You don't wire up APIs, you don't write triggers, and you don't maintain the underlying code when a platform changes.
Patterns differ from one-off automations in one important way: they've been run enough across enough workspaces that edge cases have already been handled. The first time you build a lead-follow-up sequence from scratch, you'll hit five things you didn't anticipate. A marketplace pattern has already hit them for you.
This July update adds seven new patterns. Here's each one.
New Sales Patterns
1. Inbound Lead Qualifier
Who it's for: Any business that gets leads through a contact form, a booking widget, or a social DM — and then has to manually read each one to decide if it's worth a call.
What it does: When a new lead arrives (form submission, DM, or email), the pattern reads the message, scores it against criteria you define in plain English ("high priority if they mention budget above $5k or a timeline under 30 days"), and routes it: urgent leads get an immediate personalized reply and a calendar link, lower-priority leads go into a nurture sequence, and anything that looks like spam gets flagged for your review rather than auto-replied.
What's new about this version: Previous patterns in this category required you to define routing rules as structured logic. This one takes a paragraph description of your ideal customer and figures out the rules itself. You can still override any decision from the approval queue.
2. Deal-Pipeline Nudge
Who it's for: Service businesses, agencies, and consultants who track active deals in a spreadsheet, Notion board, or lightweight CRM — and regularly forget to follow up with prospects who've gone quiet.
What it does: The pattern watches your pipeline for deals that haven't had activity in a configurable window (default: 5 business days). When a deal goes stale, it drafts a follow-up in your voice, pulls in any context from the last message thread, and queues it for your approval before sending. You review it in under 10 seconds — approve, edit, or skip.
The detail that matters: The draft doesn't sound like a template. It references the specific thing you discussed last, because the pattern reads your prior thread before writing. That's the same principle behind how Koira learns voice from a single example — context-first, not fill-in-the-blank.
New Support Patterns
3. Inbox Triage by Urgency Tier
Who it's for: Any business getting more than 15–20 customer emails or DMs per day — online stores, clinics, salons, agencies.
What it does: Reads every incoming message and assigns it to one of three tiers: urgent (refund disputes, order errors, angry tone), standard (questions, change requests), and low (general inquiries, compliments). Urgent messages get a draft reply generated immediately and flagged at the top of your queue. Standard messages get a draft within the hour. Low-priority messages are batched and drafted once daily.
Why this is different from a filter: Filters sort by sender or subject line keyword. This pattern reads the actual content and intent of the message. A subject line that says "Quick question" but contains a threat to dispute a charge gets correctly classified as urgent.
4. Review Response — Negative Review Handler
Who it's for: Local businesses, restaurants, salons, and anyone managing a Google Business Profile or Yelp listing who gets occasional negative reviews and either ignores them (bad) or spends 20 minutes crafting a careful response (also unsustainable).
What it does: When a review below a threshold you set (default: 3 stars or lower) appears, the pattern drafts a response that acknowledges the specific complaint, doesn't get defensive, and offers a resolution path. It queues for your approval before posting — you read it, tweak the tone if needed, and hit approve. The pattern learns from your edits over time.
What it doesn't do: It doesn't post without your sign-off. Negative review responses are high-stakes enough that the default is L3 (you gate every output). You can upgrade to L4 if you've reviewed 20+ drafts and they're consistently on-point. Review velocity and local rankings are directly connected, and a fast, genuine response to a negative review does more for your local SEO than most tactics.
New Operations Patterns
5. Booking Confirmation + Reminder Sequence
Who it's for: Any service business that books appointments — salons, gyms, clinics, consultants, tutors — and currently sends confirmation and reminder messages manually or via a basic booking tool that doesn't customize the message.
What it does: When a booking is created (the pattern watches your booking page or calendar), it fires a confirmation immediately, a reminder 48 hours out, and a same-day reminder 2 hours before. Each message is written in your voice, includes the specific service booked, and — if you've enabled it — includes a cancellation link that feeds directly into your waitlist fill automation.
The operational win: The average service business loses 20–40 minutes per booking day to manual confirmation messages and reminder follow-ups. This pattern runs that entire sequence without touching your calendar.
6. Invoice Chase Sequence
Who it's for: Freelancers, agencies, contractors — anyone who sends invoices and then has to awkwardly ask for payment when a due date passes.
What it does: Watches your invoicing tool (or your email for invoice threads) for unpaid invoices past their due date. At day 1 overdue, it sends a gentle reminder. At day 7, a firmer follow-up with the invoice attached. At day 14, it drafts a final notice and flags the account for your manual review before sending. Every message sounds like you wrote it — not like a collections notice.
The boundary it respects: The pattern never sends the day-14 message without your explicit approval. At that point the relationship may be worth preserving or the amount may warrant a different approach — that's a judgment call you keep.
New Marketing Pattern
7. Google Business Profile Weekly Update
Who it's for: Local businesses that know they should be posting to their Google Business Profile weekly but almost never do.
What it does: Once per week, the pattern drafts a GBP post based on inputs you've defined: your current promotions, seasonal context, and any recent reviews worth highlighting. It queues the draft for your approval on a day and time you set (most owners pick Monday morning). You approve or edit, and it posts directly to your GBP.
Why this matters for local search: GBP post frequency is a minor but real local ranking signal. More importantly, an active profile converts better — a business with a post from this week looks open and engaged versus one whose last post was four months ago. Google's 2026 algorithm updates put more weight on recency signals for local packs, and weekly GBP posts are one of the lowest-effort ways to stay current.
How Autonomy Levels Work Across These Patterns
Every pattern ships with a default autonomy level. Most of the new ones default to L4 — the pattern runs end-to-end and surfaces outputs in your approval queue, but doesn't require you to manually initiate each run. You spot-check rather than gate.
The negative review handler defaults to L3 (you gate every output) because the stakes of a bad response are higher than a missed GBP post. The invoice chase sequence runs L4 for the first two messages and drops to L3 for the day-14 final notice.
You can adjust any pattern's autonomy level from the workspace settings. If you're new to a pattern, start at L3 and watch 10–15 outputs before moving to L4. If you've been running a pattern for 60 days and you've approved 95% of drafts unchanged, move it to L4 and stop reviewing every one.
What's Coming Next
The next batch of patterns in development includes an abandoned-cart recovery sequence for Shopify stores, a social DM qualifier for Instagram and Facebook, and an inventory alert pattern that watches your POS and Shopify simultaneously and flags drift before it causes an oversell. Inventory drift between Shopify and POS is more common than most owners realize — that pattern addresses the early-warning problem, not just the cleanup.
If you're running a workflow manually right now that you think should exist as a marketplace pattern, there's a "Suggest a Pattern" link in the marketplace sidebar. That's where most of the patterns in this batch started.
A Note on Self-Healing
Every pattern in the marketplace is built to self-heal when the sites or platforms it touches change their layout, update their UI, or shift how data is structured. You don't get a broken automation and a support ticket — the pattern detects the change, adapts, and logs what it changed so you can see it. This is especially relevant for patterns touching Gmail, GBP, and Shopify, all of which shipped interface updates in the past 90 days.
“A marketplace pattern has already hit the edge cases you haven't anticipated yet — that's the whole point of it existing.”
| Area | Doing it manually | Koira marketplace pattern |
|---|---|---|
| Inbound lead qualification | Read every form submission, decide priority, write reply by hand — 5–15 min per lead | Pattern reads, scores, and drafts reply automatically; owner reviews in under 60 seconds |
| Negative review response | Notice review days later, spend 20 min drafting a careful reply, worry about tone | Pattern drafts response within the hour, queued for approval — owner edits or approves in 30 seconds |
| Booking confirmations and reminders | Send confirmation manually, set phone reminders to send 48-hour and same-day messages | Pattern fires all three messages automatically in your voice; zero manual sends |
| Invoice chasing | Check invoice tool weekly, write awkward follow-up emails, track who's been chased | Pattern watches due dates, sends day-1 and day-7 follow-ups automatically, flags day-14 for manual sign-off |
| Google Business Profile posting | Remember to post weekly (usually don't), log in to GBP, write something from scratch | Pattern drafts weekly post based on your inputs, queued Monday morning for one-click approval |
| Deal pipeline follow-up | Scan CRM or spreadsheet manually, notice stale deals too late, write follow-ups from memory | Pattern flags stale deals automatically, drafts context-aware follow-up, owner approves or skips in seconds |
How to activate a new marketplace pattern in Koira
- 01Open the Koira marketplace from your workspace sidebar. Click 'Marketplace' in the left nav. Patterns are organized by function — Sales, Support, Operations, Marketing — and each shows a brief description of what it does and which business types use it most.
- 02Select a pattern and read the setup requirements. Each pattern listing shows what inputs it needs before it can run: a plain-English description of your business, a connected account (Gmail, GBP, your booking tool), and any threshold settings like 'days before a deal is considered stale.' Skim these before activating so you have the information ready.
- 03Connect the required accounts. Most patterns need access to one or two platforms — your inbox, your booking calendar, your CRM, or your GBP listing. Connections are OAuth-based; you authorize once and the pattern uses the connection for all future runs. No API keys to manage.
- 04Answer the plain-English configuration questions. The pattern will ask you 3–6 questions in plain English: things like 'describe your ideal customer in a sentence,' 'what tone should follow-up messages use,' or 'what's your cancellation policy.' Your answers are what make the pattern's outputs sound like you rather than a generic template.
- 05Set your autonomy level. Choose L3 (you approve every output before it sends) or L4 (pattern sends automatically, you spot-check via the approval queue). If you're activating a pattern for the first time, start at L3 and run it for two weeks before moving to L4.
- 06Review the first 5–10 outputs and make edits. The pattern learns from your edits. If you consistently change the sign-off phrase or adjust the urgency classification, the pattern incorporates those corrections into future drafts. Editing early outputs is the fastest way to get outputs you approve without touching.
- 07Move to L4 and step back. Once you've seen 10–15 outputs that required no edits, upgrade the pattern to L4 autonomy. It will run end-to-end from that point, surfacing only the outputs that fall outside normal confidence thresholds for your review. Check the approval queue once a day rather than once per output.