The weekly counts per channel: where-is-my-order, returns, product questions.
afka uses analytics cookies to understand how visitors use the site. No ads, no data sales.
The working manual for setting a store team up with the afka store agent: buyers answered across every channel, the back office handled across more than one platform, and the money rules written in code before the first refund.
A direct-to-consumer brand running more storefronts than it has people: the own store plus Amazon, eBay or Etsy, a founder answering where-is-my-order questions in the evening, and a catalog that updates itself never.
Store teams are small and everyone does everything, which is exactly why the four-row table matters: it is the first time anyone wrote down who decides what.
The owner talks to the agent in Slack and by voice, and holds the autonomy dial and the money rules.
Whoever runs operations owns the catalog and inventory line and approves changes above the agreed level.
Anyone on the team can write to the agent, or dictate to it, in the afka composer: a question about yesterday's returns is a question, not a configuration task.
The meeting agent joins the weekly store call on Zoom, Google Meet or Microsoft Teams, and the decisions about pricing, stock and promotions become tasks with owners.
The approver handles the money queue: refunds above cap, price changes, anything irreversible. Approvals arrive in the inbox in the web app and as a Slack card, and a decision resumes the work in under two seconds. The teacher owns the brand voice the buyer-facing face speaks. The audit reader checks weekly that every refund and every catalog write carries who, what, when and cost.
One store agent with two faces inside the client workspace. The buyer-facing face handles order status, returns and product questions across chat, email, voice, SMS and WhatsApp. The operations face handles catalog and SKU work, inventory and merchandising, across Shopify, WooCommerce, BigCommerce, Magento and PrestaShop. Both faces run under the store skill pack you fill from the interview.
Guidance is plain language: the brand voice, the return philosophy, how the store talks about delays. Guardrails are code: the refund caps per order and per day, the price floor no change may cross, the categories that always wait for a person. A guardrail beats any instruction, from any channel, including a buyer trying to talk the agent into a refund; the conservative action always wins. The interview gathers exactly these answers, and they go straight into the pack:
The weekly counts per channel: where-is-my-order, returns, product questions.
The refund the agent may give without asking: the number per order and the number per day.
The catalog changes that are routine, and the ones, a price, a product page rewrite, a delisting, that must wait for a person.
The words the founder reaches for when a delivery is late: the brand voice, written down.
Connections run through managed connectors: a popup opens, the client authorizes each storefront, the help desk and the inbox, and afka never receives a password. Multi-platform is the point: one agent covers the own store and the marketplaces together, and the connectors screen shows every connection's status with one-click reconnect. Disconnecting is revocation within one task cycle.
One hour with the inbox: how many where-is-my-order, how many returns, how many product questions per week. The counts decide the first configuration, feed the skill-pack interview, and give the client a before picture.
A new workspace picks the store function and produces a first finished artifact from seeded sample data in under a minute. The founder sees a buyer question answered from order data before a single real storefront is connected.
Refunds within policy can run at the level the client chooses, with hard caps enforced in code. Anything above a threshold or irreversible waits for approval. Say the numbers out loud, write them into the guardrail layer together, and show that a cap in code cannot be talked around, by anyone, in any channel.
Let the agent work one real morning of buyer questions while the team watches: real order status from the order system, a routine return processed inside the spending caps, an on-brand review reply. The evening the founder gets back is the product, and the audit log showing every action with its cost is the proof.
Switch on the catalog and inventory work second, once trust exists from the buyer side. Walk the approver through the money queue, put the weekly store call on the calendar with the meeting agent invited, and leave the team owning the dial and the spending caps.
A store runs on a daily pulse and a weekly decision meeting; the rhythm attaches to both.
Daily, five minutes: the approver clears the money queue: refunds above cap, price changes, anything the guardrails held.
Weekly, on the store call: the meeting agent attends, pricing and stock decisions become tasks, and the team reviews the counts against the before picture from step one.
Weekly, ten minutes: the teacher reviews the buyer-facing replies the agent learned from edits, keeps the ones that sound like the brand, and rejects the ones that do not.
Store owners ask about money first. Good: the money answers are the strongest ones.
The spending caps, which live in code and not in the wording the agent is given. A guardrail beats any instruction from any channel, and a request above the cap goes to the approval queue with the full conversation attached.
Billing follows work done rather than seats, so capacity flexes with order volume. A spike needs no seasonal hire and no plan change, and the spending caps hold at any volume.
With the pause button. It is enforced at five chokepoints and takes effect in fractions of a second, measured. In-flight work drains cleanly, and the audit log shows exactly what was in progress when the pause landed.
The three situations you will actually meet: a storefront connector shows reconnect-needed after a platform-side password change, one click repairs it; a buyer case does not fit policy, which escalates to the named human with the order history attached; and a catalog change looks wrong, which the audit log's before and after resolves in minutes. None of the three is an incident.
You earn 30 percent of the client subscription for twelve months from the first paid invoice, with first-touch attribution for 90 days. Your implementation fee is your own business and stays yours. afka publishes no income projections: the terms are the terms.
No. The agent works inside the store and the help desk the client already uses, and acts in the systems where the fix lives.
Shopify, WooCommerce, BigCommerce, Magento and PrestaShop on the store side, and the own store together with Amazon, eBay or Etsy on the selling side.
The first session produces the first handled buyer questions inside agreed caps. The operations face switches on in week two, once the buyer side has earned the team's trust, and the weekly call decides each graduation.
The program terms, the agreement and your link are on the deployer page.
The deployer program