This page is one working day, six in the morning to six in the evening, of AI agents running inside Priority and alongside the organization’s people — in sales, purchasing, collections, service, installations and management. Scroll, and the clock moves.
priority_create_entity
confirm: true · token 90sThe morning-brief agent
Runs on a schedule, not on a question. Reads what it remembered yesterday, checks what changed overnight, and prepares for each team the three lines that matter to it — and the list of decisions waiting for a person.
Scheduled run · 06:00 · every working day
Good morning. 41 orders came in from the shop overnight, all posted to Priority. One anomaly: customer 4021 cut its orders by 38% this quarter — flagged for handling. Cash for the week: fine. Three quotes over ₪50K have waited more than 10 days for an answer — passed to the sales agent.
Thanks. Route 4021 to Dana, not to me.
Updated. From today, anomalies for customers in that segment go to Dana. Remembered.
schedule.rundaily · 06:00 · Asia/Jerusalempriority_remember{ recall: true }priority_query_table{ table: 'ORDERS', filter: "CURDATE ge yesterday 18:00" }388mspriority_detect_anomalies{ scope: [sales, cashflow], window: 90d }1.1spriority_whatsapp_send{ to: 'רון' }06:12priority_rememberThis hour: 3 system calls · 0 records written in Priority · 1 question to a person · 1 thing remembered
The field-sales agent
The salesperson is on the way to a customer. He asks out loud — how many are in stock, what the price is, when it arrives — and asks for a quote for the customer. The agent checks, prepares and shows it for approval; after one tap of approval the quote is recorded in Priority, with a PDF ready for the customer and a datasheet. Without approval, nothing is written.
“Check how many AC-2200 cameras we have in stock, what Reshet Electronics pays after their discount, and prepare them a quote for 40 units, net 30.”
AC-2200: 26 in the main warehouse, 60 more arriving on 3.9. Reshet Electronics’ price from their own price list: ₪1,180 per unit. I prepared a quote for 40 units, net 30, ₪47,200 before VAT. Approve?
Yes. Attach the datasheet.
Quote 20481 is recorded in Priority. The quote and the datasheet are attached.
priority_query_table{ table: 'LOGPART', filter: "PARTNAME eq 'AC-2200'" }241mspriority_get_navigation_property{ CUSTOMERS/'רשת אלקטרוניקה' → PRICELIST }203mspriority_validate_business_rules{ doc: 'quote', customer: 'רשת אלקטרוניקה', terms: 'net30' }96mspriority_create_entity{ confirm: false }08:43priority_create_entity{ confirm: true, token: ••••90s }priority_whatsapp_send_media{ files: ['20481.pdf', 'AC-2200.pdf'] }priority_rememberThis hour: 4 system calls · 1 record written in Priority · 1 question to a person · 1 thing remembered
The purchasing agent
Not just “where is the order”. The agent crosses the delay against what is waiting for it — customer orders, a work order, a forecast — drafts the supplier a mail, and asks the buyer for the one thing that needs a person: approving the send. Without her approval the mail does not go out and nothing is written.
PO 7731 · supplier: Metal HaTzafon · promised: 26.8 · 3 days late
Hello, order 7731 (240 × aluminum profile 40/40) was due on 26.8. We would appreciate an updated date by end of day — two customer orders for next week depend on it.
Send it. And add that if it is after 3.9 we split the order.
Sent 10:19. A follow-up reminder is set for tomorrow 10:00. Both customer orders are flagged “at risk” in Priority.
priority_query_table{ table: 'PORDERS', filter: 'DUEDATE lt today and closed eq false' }312mspriority_get_navigation_property{ PORDERS/7731 → PORDERITEMS_SUBFORM → demand }277mspriority_demand_forecast{ part: 'ALU-4040', horizon: 14 }1.3spriority_semantic_search_erp'פרופיל אלומיניום 40/40'640mspriority_update_entity{ confirm: false }10:19priority_outlook_send{ to: 'מתכת הצפון' }priority_update_entity{ confirm: true, token: ••••90s }schedule.oncetomorrow · 10:00This hour: 5 system calls · 1 record written in Priority · 1 question to a person · 0 things remembered
The collections agent
An aging report is a list. Collections is a conversation. The agent knows every customer’s history — who always pays a week late, who disputes an invoice — and phrases a different reminder for each. A promise to pay is recorded; a dispute goes to a person.
Hello, a gentle reminder: invoice 30877 for ₪18,400 was due on 20.8. If it has already been paid — thank you, we will update. If not, an estimated date would help.
It will go out on 6.9, once we receive the signed agreement.
Thank you, recorded: 6.9. We will only come back if it does not arrive.
Another customer · Techno-Service · disputes invoice 30791 (“we never received the part”) → handed to Dana, the account manager, with the full history.
priority_financial_analytics{ report: 'aging', overdue_days: 7 }1.6spriority_remember{ recall: 14 customers }priority_whatsapp_send× 8 · priority_outlook_send × 3priority_update_text{ confirm: false }11:52priority_update_text{ confirm: true, token: ••••90s }priority_whatsapp_sendschedule.once7.9 · 09:00priority_rememberThis hour: 2 system calls · 1 record written in Priority · 1 question to a person · 1 thing remembered
The installation-scheduling agent
Scheduling an installation is four calendars that have to agree: the technician, the customer, the stock and the van. The agent proposes a slot, checks the parts are in the warehouse, confirms with the customer on WhatsApp and records the service call — and reminds both a day before.
When can you install the air conditioner? Afternoons are better.
There is a slot on Tuesday 1.9 between 14:00–17:00 with Oren, the technician who already installed at your place in 2024. Does that work?
It works.
Booked. Service call 5512 is recorded, the parts are marked for picking. A reminder will arrive a day before.
priority_query_table{ table: 'SERVCALLS', filter: "STATDES eq 'ממתין לתיאום'" }256mspriority_outlook_calendar{ users: ['אורן', 'ניר'], range: '30.8–3.9' }412mspriority_remember{ recall: true }priority_aggregate_items{ call: 5512, check: 'stock' }198mspriority_update_entity{ confirm: false }13:36priority_update_entity{ confirm: true, token: ••••90s }priority_outlook_calendar{ create: true, attendees: ['אורן', 'לקוח'] }schedule.once31.8 · 09:00This hour: 4 system calls · 1 record written in Priority · 1 question to a person · 0 things remembered
The service-desk agent
Before anyone replies, the agent has already opened the file: what the customer bought, how long the warranty runs, what happened on the previous call and which part is probably needed. It drafts the reply and attaches the right document. A fault that needs a technician goes to the technician, with everything ready.
The PX-300 we bought in February stops after about ten minutes of work with error E-41. It has been happening since yesterday. — Gal Industries
Hello, the call is open (5519). Your PX-300 is under warranty until next February. E-41 is in most cases the temperature sensor — the diagnostics sheet is attached. Nir, the technician, will contact you by end of day to schedule; the part is already reserved in your name.
Good. Send it.
Sent 15:08 · Nir received the call on WhatsApp with the history and the part number.
priority_outlook_inbox{ folder: 'service', unread: true }priority_get_entity_by_key{ CUSTOMERS: 'גל תעשיות' → equipment, warranty, calls }304mspriority_semantic_search_erp'E-41 PX-300'710mspriority_create_entity{ confirm: false }15:08priority_create_entity{ confirm: true, token: ••••90s }priority_outlook_send{ reply: true, attach: 'PX-300 diagnostics.pdf' }priority_whatsapp_sendpriority_rememberThis hour: 4 system calls · 1 record written in Priority · 1 question to a person · 1 thing remembered
What is left at the end of the day
Everything written today was written after a preview and a person’s approval, and every line can be opened to see who wrote it and why. And what the agent learned today it does not keep to itself: it proposes it as a rule — and a person decides.
Today: 6 runs, 22 calls to systems, 5 records written in Priority — all after approval. 6 questions went to people, 6 were answered. 4 new things remembered.
A learning proposal: this week 3 customers asked for net 30 instead of net 15 on their quotes. Make it the default for chain customers? I changed nothing — waiting for a decision.
No. Keep net 15 and flag every request to me.
Remembered. Nothing changed.
priority_audit_query{ range: 'today' }188mspriority_get_learning_insights{ window: 7d }18:06priority_rememberschedule.rundaily · 06:00This hour: 2 system calls · 0 records written in Priority · 1 question to a person · 1 thing remembered
This is the day from above: the timeline, with the stops where an agent stopped and asked a person — and beneath it the register: every record written in Priority today, with the time, the agent that wrote it, and the person who approved it. Click a time to jump back to its scene.
| Time | Agent | Written in Priority | Approved by |
|---|---|---|---|
| 08:43 | The field-sales agent | quote 20481 | Yossi |
| 10:19 | The purchasing agent | both customer orders flagged “at risk” | Michal |
| 11:52 | The collections agent | promise to pay 6.9 on the customer card | Rotem |
| 13:36 | The installation-scheduling agent | service call 5512 — date, technician, parts | The Levi family |
| 15:08 | The service-desk agent | call 5519 · TS-11 reserved | Adi |
Every row in the register was written after approval by the person named in it. Deletes: zero. No ERP deletes exist.
Claude, ChatGPT, Copilot and Gemini are clients of a language model: the way a person talks to the agent. The agent itself is ours — the memory, the tools, the permissions and the audit log — and runs next to your Priority. The model gets replaced; the agent stays, and the memory stays with you.
22 kinds of agents, 7 departments. Each has one clear job, what it writes in Priority, and when it stops and asks a person. Six of them took the stage above.
Answers the salesperson on the way to a customer — by voice, on WhatsApp — and returns a recorded quote.
No quote is forgotten: who has not answered, what the next step is, and why quotes get lost.
Orders that arrive by mail, on WhatsApp or as a PDF enter Priority as orders — validated, not typed.
Every branch knows by morning what sold, what is missing and what is on the way — without the Sunday spreadsheet.
Knows every customer’s history and phrases a different reminder for each.
Supplier invoices matched to purchase orders, bank reconciliation, and a month-end without the to-do list in your head.
A late supplier, a missing order confirmation, a changed price — the agent sees it against what is waiting for the item.
Sees low stock before it is out, and dead stock before it ages.
A delayed shipment tells the customer before the customer asks.
A shipment abroad is a pile of documents that have to agree with each other — commercial invoice, packing list, certificate of origin, the forwarder’s booking.
An import shipment is a whole chain — supplier, forwarder, customs broker, port — and the agent follows it and updates on every change.
Counts, picking and transfers — the warehouse updates the system as it goes, not at the end of the shift.
Opens the file before anyone replies: equipment, warranty, history, the part probably needed.
Four calendars that agree: the technician, the customer, the stock and the van.
Contracts that expire, periodic visits that come due, and renewals that do not fall between the cracks.
Work orders short of material — known on Sunday, not on Thursday.
Budget against actual, hours against plan, and a milestone approaching — before it passes.
A non-conformance opens the day it happens, not at month-end — and a repeating supplier is seen at once.
Attendance reports that close themselves — gaps, exceptions and approvals — before payroll gets stuck.
Runs on a schedule, not on a question: what changed overnight, what is off, and what waits for a decision.
The meeting summary becomes tasks in Priority and the calendar — with an owner and a date.
A customer who goes quiet — seen before they are at the competitor.
Every agent on this page runs on the same foundation: MCP for Priority, the MCP server we build and operate ourselves. What it knows about Priority, what it may write and who approves first — facts you can check, not promises.
Most of what's sold today as a 'smart business chatbot' is a conversational interface over documents. It answers nicely, sometimes opens a ticket, sometimes hands off to a rep — and that's useful. But it ends at an answer. The work itself, the thing someone on your team does manually every morning in Priority or in a spreadsheet, stays exactly where it was.
An agent is a different animal. It doesn't wait for you to ask — it takes a goal, builds a plan and goes into the systems you already run to carry it out. At the end of a conversation with a chatbot you have an answer on the screen. At the end of an agent's run there is a record written in the system, and you can open it and see who wrote it and why.
| Aspect | Chatbot | AI agent |
|---|---|---|
| What it receives | A question | A goal |
| Where its knowledge comes from | What was fed to it in advance | The systems themselves, at run time |
| What it does | Phrases an answer | Runs a chain of actions end to end |
| What you have at the end | Text on the screen | A record written in the system |
| When something goes wrong | Keeps answering | Stops, explains and hands off to a person |
| Who finishes the work | You, after the conversation | The agent, as it goes |
We get asked this a lot, so here's the direct answer: we don't sell a WhatsApp bot as an off-the-shelf product. What does exist — MCP for Priority, our MCP server for Priority ERP, has a WhatsApp add-on for an extra ₪500. That is, WhatsApp exists here as an add-on to a server already connected to Priority, not as a separate bot that runs marketing conversations with customers. If a marketing WhatsApp bot is what you were looking for — we'll tell you so in the first call, not on page three of the proposal.
A chatbot holds a conversation: you ask, it answers, and the execution stays with you. An agent takes a goal, builds a plan and carries it out inside the systems — pulling data, cross-checking it and writing back. At the end of a conversation with a bot you have an answer. At the end of an agent's run there is a record written in the system.
Chatbot or chat bot — however you write it, it's the same thing: a conversational interface that answers. What it does give you — answers to common questions around the clock, a first pass over incoming inquiries, and routing to the right person. That's worth something, and if you already have one on your site there is no reason to switch it off. What it doesn't give you — execution. It won't go into Priority, won't match an invoice against a purchase order, and won't leave a written record at the end. That is exactly where an agent begins.
We build agents — systems that do work inside your systems, not just talk about it. If, after we understand what you need, it turns out a simple chatbot is the right fit, we'll tell you that straight — even if it means this is not a job for us.
MCP for Priority, our MCP server for Priority ERP, has a WhatsApp add-on for an extra ₪500. That is, WhatsApp exists here as an add-on to a server already connected to Priority — not as a separate bot that runs marketing conversations with customers. A marketing WhatsApp bot is not what we build, and if that's what you're looking for we'll tell you so up front.
Writing is off by default. When you turn it on, every operation is shown for approval first and only then sent — with a server-signed, single-use token that expires after 90 seconds. A person sees exactly what is about to happen before it happens.
We don't quote for a website chatbot, because it is simply not what we sell. An agent has no single price list, because most of the work sits in the connection to your systems and in the business rules — not in the 'bot' itself. What does have a list price is the technical foundation: MCP for Priority starts at ₪1,500 per month, with paid add-ons — Write operations, WhatsApp module, Outlook module, Multi-company, Extra 2,000 calls/mo, Extra user. excl. VAT (18%) The rest of the scope is defined together, once we understand exactly what needs to run.
The duration varies with the size of the company and the complexity of the project. Most projects take between a month and a few months. We prefer to start with one process running end to end and expand from it, rather than opening a huge project with no visible result for half a year.
Let's check together whether you have work for an agent
Not every process needs an agent, and some processes need order first, not AI. In one conversation we'll tell you honestly what's worth it, what isn't, and where it makes the most sense to start.