One queue
Marketplace orders, payout exceptions, and new conversations land in a single list instead of four inboxes.
AI automation studio
AI4BIZ builds reviewed workflows for marketplace stores, bookkeeping, and Facebook and WhatsApp conversations. Orders, ledgers, and replies move without another evening of copy and paste.
Built for owner-led businesses. Money, refunds, and tax stay behind a human gate.
What changes
Marketplace orders, payout exceptions, and new conversations land in a single list instead of four inboxes.
Buyer questions and WhatsApp leads get a draft from your script. Off-script messages wait.
Settlements and fees are lined up with the channels you sell on, before the month is supposed to close.
How it works
We sit with the person who does the job today and write the steps, the exceptions, and what must stay human.
Shop admin, accounting software, Meta, and WhatsApp. Read-only first, wherever the platform allows it.
The workflow drafts the action. Money, refunds, and customer sends wait for a rule you have approved.
You get a runbook, a queue of exceptions, and a weekly note on what the automation touched.
Planning ranges
Figures from scoping workshops, not a live customer counter.
Services
01
Order flow, inventory, buyer messages, and listings across Etsy, Amazon, eBay, and your own web store.
One queue for every channel, with a person approving refunds and stock exceptions.
Request this workflow02
Payouts, expenses, and month-end pulled into the accounting software you already use.
A close packet your accountant can read, instead of a folder of screenshots.
Request this workflow03
Lead follow-up, appointment offers, and support replies on Facebook and WhatsApp from scripts you approve.
Faster replies, with quiet hours and a human takeover when a conversation needs one.
Request this workflowSample stories
“The evening order check became a morning exception list. I still approve refunds. I stopped copying tracking numbers.”
“Payouts from two marketplaces land in the review queue already matched. I spend the close on the six lines that do not fit.”
“WhatsApp asks for a time, and the reply offers the open slots. Anything about a complaint waits for us.”
FAQ
Repetitive operations: marketplace orders and stock, payout matching and expense sorting, and first replies on Facebook and WhatsApp. Each build starts from the checklist your team already follows.
No. The workflow takes the copying and the sorting. Your accountant still closes the books. A person still handles refunds, disputes, and anything the rules do not cover.
The least that lets the workflow read, then draft. Shop admin, accounting software, and Meta or WhatsApp business tools. We start read-only where the platform allows, and we write down every permission in the runbook.
A focused first workflow is typically scoped and in review within two weeks. Larger multi-channel builds take longer because the exceptions take longer to write down.
A fixed quote for the first workflow after a short scoping call, then a monthly retainer if you want the queue watched and the rules updated. There is no per-message meter on the intro call.
Only under a rule you approved: which intents, which hours, and which phrases. Refunds, complaints, and anything off-script wait in a queue.
The Remix server stores them in Cloud Firestore and emails the studio with Nodemailer. The browser never writes to the database. Details are on the privacy page.
Yes. Most studios start with the inbox that hurts this month — one marketplace, the month-end close, or WhatsApp leads — and add the next queue after that one is boring.
Next step
A short form is enough. We reply by email with what a first workflow would and would not touch.