Call-Center POS
One queue for every order that does not walk through the door. Phone, marketplace and app orders land together, route to the right branch by load and prep time, and leave with a driver — without anyone re-typing anything.
- Marketplaces
- Talabat · MyThings
- Caller ID
- With order history
- Languages
- AR / EN
- Deployment
- On-premise
What a busy phone line actually needs.
Every channel in one queue
Phone, Talabat, MyThings and your own app arrive in the same list, tagged by channel and worked by the same agent with the same keystrokes.
Routing that knows the kitchen
Orders go to the branch that can actually deliver: zone, distance, current ticket load and prep time — not just the nearest pin on a map.
Caller ID with history
The phone rings and the agent already sees the customer, their addresses and their last orders. A repeat order takes seconds.
Status sent back automatically
Accepted, preparing, ready and picked-up go back to the marketplace without an agent tapping a tablet — which is what protects your rating.
Your drivers, a delivery company or Mishwar
Assign to your own drivers with ELTS Delivery Manager, hand over to a delivery company, or to Mishwar. The fee and the settlement land in ELTS ERP against the branch that cooked it.
Commission-aware reporting
Marketplace commission is recorded per order, so branch margin is real rather than gross — and you can see which platform is worth it.
The screens your team will use.
Simplified drawings of the real screens. Screenshots will replace them.
The integrations are the product.
Written and maintained by us — not a plug-in that breaks when someone else's API changes. Need one that isn't listed? We add it on request.
- Talabat Order intake and status updates Available
- MyThings Order intake and status updates Available
- Location Delivery Hand orders to the delivery company Available
- Top Delivery Hand orders to the delivery company Available
- Grandstream Caller ID and call logging on your phone system Available
- SMS and WhatsApp Order confirmations and driver-arrival messages Available
- BranchPOS Orders appear in the branch ticket stream Built in
- ELTS Delivery Manager Your own drivers: assignment and tracking Built in
- Mishwar Hand-over to the Mishwar fleet Pilot
- ELTS ERP Revenue, commission and delivery fee postings Built in
For the person who will run it.
- Platform
- Windows Server, with agent seats on standard Windows PCs
- Agent seat
- Any modern PC; two screens recommended for dispatch
- Database
- SQL Server on-premise, shared with ELTS ERP
- Routing rules
- Zone, distance, branch ticket load, prep time and manual override
- Telephony
- Caller ID and call logging through your phone system (Grandstream)
- Dispatch
- Own drivers with ELTS Delivery Manager, delivery companies, or Mishwar
- Languages
- Arabic (right-to-left) and English, switchable per user
- Security
- A login per agent; permissions for refunds, price override and reassignment
- Audit
- Every status change stamped with agent, time and channel
- Deployment
- On-premise, with installation and agent training on site
- Support
- 24/7, every day — phone, WhatsApp and AnyDesk remote sessions, in Arabic and English
For the agent desk and the branch.
Licensed per centre, not per feature.
Every plan includes the full feature set in Arabic and English, installation, training and 24/7 support. What changes is scale, and how much we run for you.
Single centre
- A small agent team
- Phone orders with caller ID
- One marketplace connected
- On-site installation and training
- 24/7 support
Multi-branch
- Larger agent teams
- Talabat and MyThings
- Routing by load and prep time
- Dispatch board and run sheets
- Commission reporting by channel
Enterprise
- Any number of agents and branches
- Phone system and custom order intake
- Written service levels (SLA)
- Managed servers and backups
- Quarterly review with our engineers
What buyers ask first.
01 Do agents still have to touch the marketplace tablets?
No — that is the point. Orders arrive through the marketplace connection into the same queue as phone orders, and the accepted, preparing and ready states go back automatically. The tablets become a fallback, not a workflow.
02 What happens when Talabat changes its API?
We maintain the integrations ourselves. When a marketplace changes its API, updating the connection is our job, not yours — you find out because nothing broke.
03 Can it route to branches that are not on ELTS?
Partly. A branch on another system can receive orders on a printer, but routing by load and prep time needs BranchPOS at the branch to know what the kitchen is actually holding.
04 Do we need our own drivers?
No. Use your own drivers with ELTS Delivery Manager, hand orders to a delivery company such as Location Delivery or Top Delivery, or to Mishwar — or mix them by area and time of day.
05 How is delivery revenue reported?
Per order, against the branch that fulfilled it, with the marketplace commission recorded separately — so branch profit reflects what you actually kept.
06 How long does a rollout take?
A single call centre usually takes a few days, including agent training. Connecting a marketplace depends mostly on how fast it issues the credentials.
Watch a live order route itself.
We put a test order through a demo marketplace account and you watch it reach a branch queue and a driver. Thirty minutes with an engineer, no slides.
- Amman — Jordan
- info@eltsjo.com
- +962 79 500 5767
- Arabic or English · Reply within one working day