Amrak commands are ordinary requests your team types in plain English or Arabic, such as "add two FAQs to the shipping page" or "which items run out this week?", and Amrak carries them out inside the systems you already run: your website, dashboards, CRM, ERP, calendar, client portal and design tools. Below are 30 ready-to-use commands, six each for marketing, sales, operations, management and IT/admin, with the system each one touches and whether it waits for your approval. The rule is simple: messages to clients, deleting anything and changing prices always stop for a yes, and everything else is carried out and logged. We then show how to write a good command, build your command map and measure the time you save.
How does Amrak carry out a command, and which ones wait for approval?
Every command goes through five steps: Amrak understands the request, checks the person's permissions, prepares the full change, asks for approval if the action is sensitive, then completes the task and logs it. We walk through a complete example in how Amrak works, from one sentence to action.
Three kinds of action are always sensitive: messages to clients, deleting anything and changing prices. For those, Amrak shows you exactly what will happen and waits. Everything else runs within the person's permissions and is recorded with who asked, when and what changed. Permissions come first: someone who may edit products but not prices never reaches prices at all. If you want other actions to wait for a yes too, such as publishing to the public website, say so in your command map: each connector is built around your own rules.
Teams are ready for this. In PwC's Middle East Workforce Hopes and Fears Survey 2025, 32% of employees in the region said they use generative AI tools daily. Yet that use usually happens in a separate chat window, while the work lives in company systems, where finding things is a job in itself: in a Gartner survey of digital workers in the US, UK, India and China, 47% said they struggle to find the information or data they need to do their jobs well. A command that runs inside your systems takes the searching and clicking out of the request.
The commands below are examples. What Amrak can do depends on what your systems allow, and we confirm it with you before anything is built. The systems it connects to are listed on the Amrak page.
Which Amrak commands can marketing teams use?
Marketing teams publish, schedule and report every week, so their commands save many clicks.
| Command | System it touches | Waits for approval? |
|---|---|---|
| "Write an article on choosing a delivery partner in English and Arabic, add a fitting image from our library and schedule it for Thursday at 10 am." | Website and content publishing, image library, calendar | No, logged |
| "Move every post planned for next week to the same days the week after." | Content publishing, calendar and scheduling | No, logged |
| "Which articles brought the most visits this month, and which pages do people leave fastest?" | Dashboards and analytics | No, logged |
| "Add two FAQs about delivery times to the shipping page." | Website pages | No, logged |
| "Design the cover page of our new services booklet in our brand colours." | Design tools | No, logged |
| "Delete last summer's campaign page and remove its images from the library." | Website pages, image library | Yes: deletes content |
Which Amrak commands help sales teams?
Sales commands work mostly in the CRM. Drafts run freely, but nothing reaches a client until you approve it. See also our guide to AI in sales.
| Command | System it touches | Waits for approval? |
|---|---|---|
| "Show every client we haven't contacted in a month, with their last deal and account owner." | CRM | No, logged |
| "Draft a follow-up for each of them in their own language and let me review before anything goes out." | CRM | Yes: message to clients |
| "Add the client I met today, with company, phone and email, and set a follow-up call for next Tuesday." | CRM, calendar | No, logged |
| "Prepare a one-page brief on the client I'm meeting this afternoon: open deals, last contact and open portal requests." | CRM, client portal | No, logged |
| "Which clients sent requests through the portal this week, and which are still waiting for a reply?" | Client portal, CRM | No, logged |
| "Change the price of the annual support package in the online store from the first of next month." | Product store | Yes: price change |
What can operations teams ask Amrak to do?
Operations commands read and update the ERP. Purchase orders come back as drafts, and anything that tells a client about a change waits for approval. More in our article on AI in operations.
| Command | System it touches | Waits for approval? |
|---|---|---|
| "Which items will run out this week? Draft a purchase order for each supplier." | ERP | No, logged (draft only) |
| "Show current stock of our best-selling products in every warehouse." | ERP | No, logged |
| "List the purchase orders that are late, with the supplier and expected date." | ERP | No, logged |
| "Update the stock count for the items in this morning's delivery." | ERP | No, logged |
| "Move Thursday's installation visits to Sunday and draft a note to each affected client." | Calendar, CRM | Yes: message to clients |
| "Delete the duplicate purchase order created yesterday." | ERP | Yes: deletes a record |
What can managers ask Amrak?
Managers mostly ask questions, and the answer comes from live systems instead of a report someone has to prepare. We cover this shift in AI for managers.
| Command | System it touches | Waits for approval? |
|---|---|---|
| "Summarise yesterday's work: what was published, which client requests were closed and what is still open." | Website, client portal | No, logged |
| "Why did website visits drop last week, and which pages performed best?" | Dashboards and analytics | No, logged |
| "Compare new clients this month with last month, by source." | CRM, dashboards | No, logged |
| "Which portal requests have been open the longest, and who owns each one?" | Client portal | No, logged |
| "Book a meeting with the sales and operations leads for Sunday at 9 am." | Calendar | No, logged |
| "Post a notice to all clients in the portal about our holiday working hours." | Client portal | Yes: message to clients |
Which Amrak commands help IT and admin teams?
These commands handle the website changes that usually mean opening page after page. The rules behind permissions and approvals are explained in our guide to AI governance for small and mid-sized companies.
| Command | System it touches | Waits for approval? |
|---|---|---|
| "Change our phone number on every page of the website, and show me the list of pages first." | Website pages | No, logged |
| "Find images in the library with no alt text and write a description for each." | Image library | No, logged |
| "List the pages that have no meta description or a meta title longer than 60 characters." | Website pages | No, logged |
| "Add our new team member to the About page with this photo and job title." | Website pages, image library | No, logged |
| "Show every change made to the website through Amrak this week: who asked, when and what changed." | Website, Amrak activity log | No, logged |
| "Delete the duplicate copies of our logo from the image library." | Image library | Yes: deletes content |
How do you write a good Amrak command?
A good command reads like a clear message to a capable colleague and answers four questions.
- What: the action and the thing it acts on. "Add two FAQs" is clearer than "fix the FAQs".
- Where: the system, section or page. "On the shipping page", "in the CRM", "in the image library".
- When: a date, a time or a period. "Thursday at 10 am", "this month", "from the first of next month".
- For whom: the audience or the records. "Clients we haven't contacted in a month", "existing clients only".
Three habits help too. Say what you want back: a list first, a preview or a draft. Start with one outcome per command and combine steps once you trust the result. And use your own names for things: we build the connector around your sections and your words.
| Vague | Specific |
|---|---|
| "Post about the offer." | "Write a short article in English and Arabic about our winter offer for existing clients, use the offer image in the library and schedule it for Sunday at 9 am." |
| "Follow up with clients." | "Draft a follow-up for every client in the CRM we haven't contacted in a month, in their language, for my review." |
| "Check the stock." | "Which items in the main warehouse will run out before the end of the week?" |
How do you build a command map in the discovery session?
The command map decides what we build. You leave the free discovery session with a first version, and we refine it together before the build starts.
- List the repeated tasks for each role. Ask each team what they do every week that takes many clicks or screens.
- Describe each task: the system, how often it happens, the steps it takes by hand and who does it.
- Mark the sensitive ones. Messages to clients, deletions and price changes wait for approval. Add any other action you want treated the same way.
- Set permissions by role. A sales coordinator may update client records but not prices, for example.
- Write each command in your team's own words, using the four questions above.
- Pick the first set: commands that are frequent, take many steps and carry little risk.
- Agree what a good result looks like: what the person checks afterwards, whether the page, the record or the draft.
After the map, HBS Tech builds the connector, tests it with your team on real work, then hands it over with training and a ready-to-use command guide. New commands or systems added later are quoted before work starts.
How do you measure the time Amrak saves?
Measure before you start. On our Amrak page we count 14 manual steps to publish one article by hand, from logging in to pressing publish, against one sentence with Amrak. Count your own tasks the same way.
- Take a baseline. Pick five to ten commands from your map and record the steps, the minutes by hand and how often each happens in a week.
- Time the new way honestly, including writing the command and reviewing the result.
- Multiply by frequency to get hours per week for each role.
- Track quality too: corrections, missed pages and rework, before and after.
- Use the log. It records who asked, when and what changed, so you see which commands people actually use.
Then decide where the saved time goes. Gartner reported in May 2026 that AI tools save sellers an average of 4.8 hours per week, yet 72% of sales organisations report low reinvestment of those savings in high-value sales work. Time you do not plan for disappears. For the full set of metrics, read how to measure AI ROI.
If you want a list like this built around your own systems and approval rules, book a free discovery session through the Amrak page. We will map the commands that save your team the most time and show you which ones will wait for your yes.
