WhatsApp Operations Inbox
The exchange's smart secretary: work messages from customers' WhatsApp groups (the groups linked in each account's file) come in here automatically, get read, and an "action button" with a pre-filled form is built for each one: receipt → record transfer/item, IBAN → deposit request, trade message → trade form, crypto hash → record transaction. Ordinary chit-chat isn't saved.
Page layout
- Top bar: the "Pending", "Unrecognized" and "Duplicate" tabs with counters; the other statuses (Done, Rejected, Auto-archived, Blocked) are in the "More" menu. The gear button opens the inbox settings (managers only).
- One line per message: account name, amount and unit, counterparty (receiver, IBAN or a snippet of the message) and time. Messages sit under "Today", "yesterday" or the date of that day, and priority items come first under "🔥 Priority".
- Tags only for problems: each line shows at most one coloured tag — the most important problem (such as "Amount mismatch", "Invalid format" or "Duplicate?"). All badges are still shown in the header of the details panel.
- Small icons: an up arrow means sent by us, a forward arrow means a receipt forwarded from another group, a green tick means the figures were matched with the PDF text, and an amber triangle means the receipt was read with low confidence and should be checked against the image. Hover over an icon to see its meaning.
- Dot next to the time: amber means the message has been idle longer than the configured hours, red means more than twice that. The "Idle over N h" chip at the top shows how many such messages there are; click it to see only those, click again to see everything.
- Details panel: account name and badges, the receipt preview (click to zoom) and the extracted fields with labels: amount, receiver, payer, tracking code, receipt date, IBAN and confidence; for trade messages the side, amount, second currency, rate and fee. Suggested actions and "Done", "Reject" and "Block…" always stay at the bottom of the panel.
- Phone: the list is a single column and each message takes two lines; tap a message to open its details and use "Back" to return to the list.
Which Messages Get Read?
-
A photo or PDF of a bank receipt — the amount, bank, tracking code and names are read automatically, and recording it against the customer's open payment commitment or as a "Funds Transfer" with a prefilled form is suggested.
-
An IBAN number or a foreign IBAN (only from the customer, not our own numbers) — two suggestions: "Create deposit request" and "Create staged deposit."
-
A trade message (only from "Exchange WhatsApp numbers" — Settings) — in the format below.
-
A crypto transaction hash (64 characters, or a tronscan/bscscan/etherscan link) — main button "Record crypto": the crypto form opens with this hash and the group's customer account, the amount, currency and wallet are read from the network automatically, and saving marks the message done. If the same hash is already recorded, the button is "View document".
-
A crypto screenshot (from a wallet or exchange app) is information only: it is not counted in "Pending", priority or the no-action alert and does not appear in the main list; it shows under the "Crypto" chip of the "Type" filter. The amount, network, addresses and (usually truncated) hash read from the image are only displayed, and its button is "Record with hash": the crypto form opens with the customer account so you can paste the full hash. If the app finds this screenshot's transaction among the deposits to your own wallets, the card shows "Transaction found" and "Record crypto" prefills the full hash; if several same-amount transactions are found, all are listed so you can pick the right one against the screenshot.
Trade Message Format
sell 1000 USD by IRT rate 181500
buy 1000 USD by IRT = 181,500,000
sell 500 EUR by USD rate 1.08 fee +20
buy 350,000 rmb by usd ist (6.7425) = 51,910 usd ist
sell 1,000 usd sol by rmb (6.70) = 6,700 rmb
buy 5,000 usd teh by usd ist (=) = 5,000 usd ist
buy 2,000 usd hav by usd (1.005) = 2,010 usd
sell 10000 usd by 36700 aed
change eur to usd ist (1.1596)
change all rmb to usd (6.70)
خرید ۲۰۰۰۰ درهم با تومان (۷۱۲۰۰)
فروش ۳،۵۰۰ دلار به درهم = 128380 + ۱۰ دلار کارمزد
sell= sell to the customer,buy= buy from the customer. The equivalent Persian words for sell / buy / by / with / rate / fee are also accepted. Arabic (بيع / شراء / مقابل / عمولة), Kurdish (فرۆشتن / کڕین / بە / کۆمیسیۆن) and Russian (продажа / покупка / продаю / куплю / за / по курсу / комиссия) are read too; Russian currency names in any inflection (“долларов”, “рубли”, “дирхамы”) map to the currency code.- Fully Persian messages are read too: the Persian name of a currency (درهم, دلار, یورو, تومان/تومن, ریال, لیر, یوان, تتر, پوند, روبل, «دلار حواله»…) is the same as its currency code, whether written with Arabic ک and ی, with آ, or with colloquial suffixes such as «دلاری» or «درهمها». Persian digits and the Persian comma between thousands («۳،۵۰۰») work too. A Persian word you add to the “Currency dictionary” in the inbox settings (for example «دلار استنبول») is recognized as well.
- Instead of a rate, you can write the total amount of the second side with an
=sign; the rate is calculated automatically. - The fee is optional:
fee +20means we take 20 from the customer,fee -20means we give it to the customer. The fee currency is also optional (fee -50 USD) and defaults to the trade's second currency. - Rate in parentheses: whatever appears inside
(...)is the trade rate, e.g.(6.7425). If the parentheses contain only=, the rate is 1:(=). You can still write the total of the second side with an=after the parentheses. - USD variants:
usd sol/usd teh/usd ist(two words, or joined with an underscore likeusd_ist) are recognized; if the currency codeUSD_SOL/USD_TEH/USD_ISTexists it is chosen. A loneusdequals your default variant — Settings → "If a message only says usd, which one is meant?" (for exampleist, i.e. usd = usd ist). - Havale: the suffix
havmeans havale;usd hav→USD_Randeur hav→EUR_R.
Important — trade summary: if you use the "Send trade summary to group" feature, don't also send a manual message in this format for the same trade, so a duplicate suggestion isn't created. Summaries the system itself sends are recognized and ignored; if you want the inbox to never read trade messages at all, turn off the "Read trade messages from groups" option in Settings.
Amount and Rial Unit
The amount on rial receipts is converted to toman or rial according to Settings → "Receipt rial unit" and entered into the forms. Lira, yuan, and other currency receipts are transferred in their own currency.
Notes
-
In the form opened by a suggestion button (transfer, commitment part, commitment, deposit request, crypto), the inbox receipt itself appears under the attachment field as “Inbox receipt attached”; click the image or “View receipt” to open it full size and compare it with the amount and details the app detected. If you choose another file, it replaces the inbox receipt.
-
Duplicate and forwarded receipts are detected automatically; a receipt that only looks like another one gets a warning badge so you can decide.
-
Clicking the receipt photo enlarges it; "Block" (group / sender-in-group / sender everywhere) is on each row's button. Removing an entry from the block list requires the settings-manager permission.
-
After recording from any suggestion, the inbox item is automatically marked "Done". If the same message has already produced a document (for example a colleague recorded the same card first), the second recording is refused with “This message was already recorded by … in …”; once the earlier document is reversed, recording again is allowed. A payment commitment or deposit request form opened from a pending card is also refused if a colleague handled that card before you submit.
-
Messages colleagues send are labeled "Sent by us"; their numbers are defined in Settings → "Exchange WhatsApp numbers".
-
A receipt forwarded from another customer's group is linked to the first one automatically, and related commitments or a "Funds Transfer" with both parties are suggested.
-
The "Extract with AI" button is also available in the Dismissed, Auto-archived and Unknown tabs; the "type" filter is chosen with the chip buttons above the list.
Non-receipt files (Alipay QR/invoice)
When an image or PDF is not a receipt and contains no IBAN or transaction hash, two actions are suggested: "Create staged payment with this file" and "Deposit request with this file". The form is prefilled with the group's customer and the file itself is attached automatically as the "destination file", so it travels with the assignment message to the payer. The destination account, holder name and amount are also prefilled when possible and can be edited before saving.
-
Trader and fee detection in trade messages: the fee is read in both forms — “fee +50” and “+ 50 usd fee” — and its currency snaps to one of the two trade sides. The message text is prefilled verbatim into the trade description, and when someone is mentioned (@ID) or the sender is recognized, the trader is auto-selected from the WhatsApp IDs on user profiles. The mention itself (@ID) is not copied into the trade description.
-
Full-balance settlement: a “change cur1 to cur2 (rate)” (or
byinstead ofto) message — with or without “all” — from the exchange’s own numbers prefills the trade form with the customer’s entire cur1 balance (as of click time) — buy/sell direction comes from the balance sign, and a missing rate means the board buy/sell mid. -
No rate, two amounts: you can skip the rate and give both sides — inline “sell 10000 usd by 36700 aed” or with equals “sell 10000 usd by aed = 36700”; the rate is derived by division.
-
Desk formats also accepted (besides the samples above): "by" may be
toorba;havale/hav= remittance variant;karmozd= fee ("ba 175 usd karmozd"); Turkish İ ("usd İst") is fine; the total may follow a comma or come right after the second currency ("by usd teh , 1025", "by usd ist 100,000"); if the first amount is missing but rate and total are given ("Buy usd by toman (223,500) , 200,835,000 tmn") the amount is computed;full/allinstead of an amount = convert the whole balance ("Buy full aed by toman (61,000)"); a signed spread between two variants of one currency ("euro hav by euro ist (+0,004)" = rate 1.004); two variants of one currency without a rate = 1:1; "change" with an explicit amount ("change 12,379 usd hav to usd ist (=)", "change 200 m toman to rmb (33,450)");kafter a number means thousand ("sell 10k usd by toman (269,000)" = 10,000 USD). -
Decimal comma: a European rate like “(1,1596)” is read correctly as 1.1596; three-digit-group commas (10,000) remain thousands separators.
Currency type suffix in messages (usd ist, …)
A variant is the suffix after the code: "usd ist" Istanbul dollar, "usd teh" Tehran dollar, "usd hav" remittance (USD_R), "usd sol"… The exchange default variant (Settings → default currency variant, for example ist) IS the main currency: "usd" and "usd ist" are both your USD, "eur ist" is your EUR — unless a separate currency like USD_TEH exists, which wins.
Queue, auto-archive and bulk actions
-
Priority & unanswered alert: more important items come first under "🔥 Priority", and an item left idle beyond the configured time gets an amber dot next to its time (red after twice that).
-
Auto-archive: a pending item idle for the configured hours moves to the "Auto-archived" tab so the counter only shows fresh work. Hours of the exchange's days off are not counted, so a message that arrived on Wednesday evening is still pending on Saturday morning.
-
Bulk actions: in the Pending tab select multiple rows with checkboxes and archive/dismiss/mark-done at once.
-
Return to queue: an item that went to «Unrecognized», «Rejected», «Auto-archived» or «Duplicate» by mistake becomes «Pending» again with the «Return to queue» button at the bottom of the details panel; in the same tabs you can also select several with the checkboxes. This is recorded in the activity log. «Extract with AI» in these tabs also returns the item to the queue automatically when it finds a receipt, an IBAN or a crypto hash.
-
Being reviewed: while someone is posting a receipt, others see a "👀 being reviewed" badge so a receipt is not posted twice.
-
Duplicates: a duplicate receipt is detected automatically, and receipts that merely look alike are not treated as the same.
-
Commitment suggestions with confidence: the "post to commitment" buttons show how confident the match is.
-
These behaviors are configured in "Inbox settings" (admin only); see the "Inbox performance" report too.
Trade messages with an invalid format
If a colleague sends a trade message in a broken format (no rate, unknown currency name, …), it is not discarded: it stays in the queue with a red “Invalid trade format” badge and can be selected in the “type” filter, so the manager can see who wrote what and remind them of the correct format. Common typos are corrected automatically as far as possible. A correct example appears under the badge, in the message's own language: Persian (فروش 1000 دلار به تومان (215,000) + 20 دلار کارمزد), Arabic (بيع 1000 دولار مقابل درهم (3.67) + 20 دولار عمولة), Kurdish (فرۆشتن 1000 دۆلار بە درهم (3.67) + 20 دۆلار کۆمیسیۆن), Russian (продажа 1000 долларов за дирхамы (3.67) + 20 долларов комиссия), otherwise the Latin one. A fee you pay is written with -. A message that contains an IBAN (such as account details a colleague sends for a deposit) or only announces a rate is not treated as an invalid format. If a message has only the total and the rate, the first amount stays empty and the rate and total go to the form as written; the inbox does not calculate anything itself.
Draft trade: a message with an invalid format gets a "Record Buy & Sell (draft)" button. The trade form opens with the customer account, the message text in the description and the trader, plus whatever the text states unambiguously (buy or sell, the currencies, the amount and the rate); complete the rest from the message text and check everything before saving.
Correcting a trade message after it was sent
A trade message in the group sometimes changes after it is sent. The inbox understands three ways of correcting it:
- Edit in WhatsApp (within 15 minutes of sending): the new text automatically replaces the card's text and the card gets an "Edited in WhatsApp" badge.
- Reply with the
Edit:prefix, with no time limit and only from our own numbers: reply to the trade message and writeEdit: sell 1200 usd by irt rate 98500. The text after the prefix becomes the valid trade of that same card; no separate card is created. If you correct several times, the last correction wins. A reply without this prefix is a new message as usual. Partial corrections work too: if you write only the rate, only the amount with its currency, only the second currency or only the fee, just that piece is applied to the earlier trade and the rest is unchanged; the card gets the «Partly corrected via reply» badge and the original message text stays, with the correction line under it. If it is unclear which side the piece belongs to, the card becomes «Invalid trade format». - Reply
Cancel, only from our own numbers: the quoted trade is cancelled; a pending card is "Dismissed" with a "Cancelled via reply" badge. A note after the word is optional (Cancel - was a mistake). - Deleting the message: a pending card is automatically "Dismissed" with a "Deleted by sender" badge.
Only a reply that starts with one of these two keywords is a command; any other reply ("ok", "received?" …) leaves the card unchanged.
In all three cases the previous text stays in the card details, struck through, under the new text so you can see what changed. The "Book trade" button is always pre-filled with the latest text.
If the trade was already booked, the app never touches the document: the card returns to the top of the pending queue with a red "Corrected after booking" (or "Deleted after booking") badge, shows both texts and has a "View booked document" button. Look at the document and decide: edit the document and mark "Done", or "Dismiss" if the correction was unwarranted. The "Book again" button is only for after you have reversed the previous document.
Unknown word in a trade message: if a word like “harat” resolves to no currency, the card shows an “Unknown word” badge and asks which currency it refers to; choosing one stores the word in the exchange's dictionary and re-reads the message. Next time it is read automatically.
Editing a receipt image before booking (black box, blur, crop)
Sometimes part of a receipt — the account balance, a card number or a third party's name — must not reach the recipient group. Under the receipt image on the inbox card, press “Edit image”:
- Black box: drag a box on the image; that area becomes solid black.
- Blur: that area is turned into a coarse, unreadable mosaic.
- Crop: drag a box around the part to keep; the rest of the image is cut away.
- Undo reverts the last step and Start over brings back the original image. Save stores the edited version separately.
It works with a mouse and with touch (phone). The original image is never changed: the AI still reads the original, and the card shows an “Edited” badge with a “Show original” button. When you book a part or a transfer from this card, both versions are attached to the document, and whatever goes out to the recipient's WhatsApp (forward on booking, “Resend receipt”, “Send all receipts” and the ZIP) is the edited version. “Revert to original” deletes the edited version. Every edit and revert is recorded in the activity log.
Retention
Inbox items are kept for 3 business days; older ones are deleted automatically whatever their status. Days off come from the Business days card in Settings (weekly days off, official holidays and extra days off) and are not counted, so messages from before a weekend or a long holiday are still there when you return. Documents already booked from the cards stay untouched.
- If the recipient name or IBAN on the receipt matches none of the payer's open commitments, the commitments are still offered but tagged “⚠ recipient doesn't match” and not highlighted; the main button becomes “Record transfer”, with “Create commitment” for that IBAN. If you still open such a commitment, a recipient-mismatch warning appears above the part form.
Receipt check badges (October 2026)
-
Check badges: a receipt whose amount or tracking code looks suspicious comes with a warning badge so it can be checked against the receipt image.
-
Sent by a colleague; it was rejected before: a colleague posted a receipt that was first set aside as “not a receipt”; this time it is read directly and, even if it is again judged not a receipt, it is not closed automatically.
-
A successful Alipay receipt is no longer rejected because of the QR at its bottom, and if someone deletes a message “for everyone” in WhatsApp and sends it again, the second copy appears in the queue itself.
-
Cards and files the app itself sends to WhatsApp never enter the queue again.
-
Forwarded receipts from other Nexto exchanges: a receipt sent to the recipient group (“Image with an info header” or “PDF” format) by another exchange that uses Nexto is no longer closed but read in the inbox: amount, currency, tracking code, destination account holder, bank and IBAN are taken exactly as the sender’s Nexto wrote them, because this data travels inside the file itself — so no misreading and no extraction cost — and the item shows the «Nexto file data» chip instead of the confidence percentage. A receipt your own exchange sent is still closed if it comes back to your inbox (e.g. a colleague forwards it to another group). This works only when the file itself arrives untouched (sent by Nexto, forwarded within WhatsApp, or a PDF); a photo saved to the gallery and sent again is recompressed by WhatsApp and is read the normal way. Balance cards, statements, trade receipts and other cards are still closed, whoever sent them.
-
Receipt reading credit ran out: when the automatic receipt reading credit (wallet or the plan's monthly quota) runs out, a yellow notice «Automatic receipt reading credit has run out» with a «Top up credit» button appears above the inbox, and each receipt shows «Receipt reading credit has run out». Messages and receipts still arrive and can be registered manually; the app retries from time to time by itself (the «AI extraction» button always tries). After a top-up, the same day's receipts are read automatically and the notice disappears.
-
Unread receipts still get suggestions: if a receipt was not read with AI (credit ran out, manual or off mode, monthly cap), the buttons for registering into the group's open commitments and «Register transfer» still appear. Amount and tracking code are prefilled when possible. The source of each guess is shown on the card; compare the amount and code with the receipt before registering. If the forwarded twin's document already covers this customer, the main button is «View document» and pressing «Done» is enough, so nothing is registered twice.
-
Text IBAN messages: when a customer sends an IBAN as text (e.g. «Keshavarzi Bank / account holder: … / IBAN / amount … toman»), the message is read and the «Register deposit request» and «Define payment commitment» buttons come prefilled with the IBAN, account holder name, bank and amount. The amount is filled only when its unit (rial or toman) is written in the message; notes in parentheses such as «(active)» are not part of the name. If one message has several IBANs, the card shows how many, and each IBAN gets its own «Register deposit request» with the name and amount from its part of the message. A payment-list PDF works the same way: every IBAN in the PDF text gets its own suggestion.
-
Payment party code in trade messages: the trader can name the other payment party in the trade message itself, so the payment commitment is created together with the trade.
-
«Trade commitment» filter: with the payment commitment shortcut on, the type chips above the inbox include a «Trade commitment» filter: «Payment party» cards (code replies on registered trades) and trade messages that carry a payment party code — including codes that were not found (red badge) — are shown together.
Staff: trade messages are read only from the exchange's own numbers. The WhatsApp number registered for each active user under “Users” counts as staff automatically; in the inbox settings add only other numbers (for example a company line).
ID cards and cash-delivery receipts
A photo of an ID card or passport on its own is not a receipt and is set aside; but if it comes with a sign that cash was handed over, it counts as a cash-delivery receipt and stays in the queue for you to record.
Failed or pending receipts and the deposit request
- If the file shows signs of a transaction (tracking code, time, amount with a date, a transaction status or both parties' names), the receipt suggestions appear (record into a payment commitment or «Record Funds Transfer») even if the AI did not recognise it as a receipt — never «Create deposit request». «Create deposit request» is only for a plain IBAN or account card, so a receipt the customer sent is not paid out a second time.
- If the status printed on the receipt is not successful, the card shows a «Receipt status: …» badge: red for a failed transfer, yellow for one still pending. Do not record a failed receipt; check with the customer.
- A file the AI judged «Not a receipt» but which carries financial signs does not go to «Unrecognized»; it stays in the queue with a «Needs review» badge for you to look at.
When the list is empty, the details panel steps aside and a link to the fullest other tab appears (for example "4 items in Done").
Unlinked groups
Messages from a group that is not linked to any account are not read at all: they do not enter the inbox and are not kept anywhere. To read a group, first link it to the customer's account in the account form (WhatsApp group or read-only groups); new messages from that group arrive right away. Messages sent before linking are not brought in.
Receipt whose file did not arrive
If a receipt file cannot be received from WhatsApp (connection problem or a file larger than 11 MB), the message is not lost: the item enters the queue with the red “Needs review” badge and the note “This message’s file was not received from WhatsApp”, and its caption is shown; view the receipt in the WhatsApp group itself. If the file of the same message later arrives from another line, it takes this item’s place. Messages sent while the WhatsApp line was disconnected arrive after it reconnects (up to 48 hours). Messages the app itself sends to a group do not come back into the inbox.