Guides for the people who run the system every day: what each feature is for, the reasoning behind it, and the steps to use it well.
Group the tickets of one big piece of work into a project, see how far along it is, and post progress updates in one place instead of in chat messages. · 4 min read
When a dropshipping customer says their products will not upload to eBay, Shopify, WooCommerce, TikTok Shop, Wix or Allegro, read the platform's answer in aiku first. Most of the time it is the platform's own rule and the customer guide already tells them what to do. · 7 min read
For QA - find the tickets waiting for a check, test the fix on the live page, give a clear pass or fail, and know what happens next. · 2 min read
Turn a customer conversation into a ticket without retyping it, hold the chat open until the work is done, and let whoever fixes it tell the customer and close the conversation. · 5 min read
For engineers and lead engineers - how to pick up tickets, keep them moving, work on them together with collaborators, ask the reporter a question, close them with a note, and ask QA to check your fix. · 11 min read
Report a bug or ask for a feature from aiku or Slack, follow what happens to it, answer the engineers' questions in time, and rate the fix when it is done. · 5 min read