OKTO for Priority: your ERP, on WhatsApp
This page sets out exactly what connects between OKTO and Priority: which documents can be retrieved, how the connection works, what is needed on your Priority side, and the limits we know about and handle.
What it gives you
Priority holds every answer your customers are looking for — their balance, their invoices, their price list, their last order. The problem is that only someone sitting in front of the system can get them out.
OKTO makes Priority accessible in the channel your customers already use anyway.
What you can retrieve
| Document / data | What the customer writes | What comes back |
|---|---|---|
| Invoice by number | “Send me invoice 30412” | PDF within seconds |
| Invoices by period | “June’s invoices” | Every invoice in the range |
| Customer statement | “Send my statement” | Up-to-date PDF from the ERP |
| Debt aging | “What’s my balance?” | Aging report |
| Personal price list | “Send my price list” | The price list assigned to the customer |
| Delivery notes | “This week’s delivery notes” | By date range |
| Opening an order | “2 pallets of guacamole” | Summary for approval → order in the ERP |
How the connection works
OKTO connects to Priority through OData REST — Priority’s standard API — using a dedicated user that you create and restrict.
The flow, end to end:
- 01The customer sends a WhatsApp message
- 02The system identifies them by phone number, against the customer table in Priority
- 03A language model understands what they asked for
- 04The system runs a targeted query against Priority — on the relevant entity only
- 05The document is sent on WhatsApp and deleted from the server
No sync. No parallel database. No nightly export. Every read is a live read.
The full order process — parsing, product matching, personal pricing and the approval gate — is on the orders agent page.
Orders agentWhat we need from you
We know exactly what is needed, and the list is short:
- Active OData access
- On your Priority
- A dedicated user
- With permissions restricted to the defined entities only
- Document generation procedures
- Generating PDFs through the API is an extension installed separately in each installation. If you don’t have it, it’s a short configuration with your Priority implementer, and we support it
- Price lists assigned to customers
- A customer with no price list assigned can’t receive prices. It’s also an excellent diagnostic: the system shows you the missing assignments
- Time zone setting
- Date queries in Priority depend on the time zone configured for the company. We set it for each customer separately.
If something on the list is missing, it isn’t a blocker. Most items are a short configuration with your Priority implementer, and we support it. The full checklist is available for download.
Priority readiness checklistTypical timeline
- Weeks1–2
- Connection and permissions. Creating a dedicated OData user, verifying access from our side, and mapping the document types in your installation.
- Weeks2–3
- Fit and testing. Verifying the document generation procedures, checking price list assignments, setting the time zone, and testing end to end on real data.
- Weeks3–4
- Internal run. The agent opens to managers and salespeople only, alongside the existing process, to validate recognition quality.
- Weeks4–6
- Opening to customers. Gradually, with close monitoring. Orders are a separate phase that starts only once documents are stable.
What doesn’t change for you
- No change to your work processes in Priority
- No module to install inside the ERP
- No migration and no data transfer
- Your team keeps working exactly as before
OKTO sits on top of Priority, not inside it.
Limits we know about and handle
Priority has real API limits. Integrations that don’t account for them break in production:
- Record cap per query
- Large queries are returned in pages. OKTO handles the paging automatically.
- Calls-per-minute limit
- Going over it returns a rate error. OKTO applies graduated back-off and retry, so automation running across hundreds of customers doesn’t bring the connection down.
- Time zone sensitivity
- Date queries in Priority depend on the company’s time zone setting. We set it for each customer separately and make no assumptions.
- Custom procedures
- The names and structure of document generation vary between installations. We map them during implementation.
Priority FAQ
Does it work with Priority in the cloud and on-premises?
Yes, as long as there is OData access from the internet or through a configured secure connection.
Who sees the data?
Only the customer who asked, and only their own data. Identification is made against the phone number on the customer record in Priority. Anyone not identified as a customer gets a general answer only, with no access to documents.
What if a customer’s phone number isn’t up to date in Priority?
The system treats them as a lead and passes them to the team. Once the record is updated, they can be re-identified with one click from the dashboard.
Does it slow Priority down?
No. Queries are targeted and small — a single document or a filtered list, never a full scan.
What happens if Priority is unavailable?
The system tells the customer there is a temporary fault, hands over to a human representative and alerts the team. It doesn’t make up an answer.
We already have an integration platform for Priority.
OKTO doesn’t replace an integration layer — it’s a conversation channel on top of the ERP. In many cases the two run side by side.
How many API calls does it use?
It depends on volume. In a typical documents conversation: one identification call and one retrieval call. We measure it for each customer and show it in the dashboard.
Can we limit what the system is allowed to access?
Yes, and we recommend it. The dedicated user gets permissions only for the entities you define.