What a vendor's email meant
A reading of an inbound message, what it counts as, and why correcting one is worth more than a score.
Vendor mail arrives all day and most of it says something about a submission. MetaOpus reads it and records what it was understood to mean, with the words that reading rests on.
Completed, not intended
“We submitted him” and “we should be able to submit him tomorrow” differ by four words, and only one of them is an event. A reading that cannot prove the past tense is not recorded as having happened.
Effective confidence
Two things are combined: how confident the reading is, and how firmly the candidate was identified. A perfect reading of a sentence about somebody nobody can name is still not usable.
When two consultants match the same name, nothing is chosen for you. Picking wrong records a submission against the wrong person and blocks a duplicate check that should have fired.
Correcting a reading
Saying what a message really meant is the only evidence there is that the rules need changing. It is worth more than any confidence number the system can produce about itself.
Frequently asked
Does a reading change a submission on its own?
It proposes what happened and shows the words behind it. The record moves when a person agrees, which is why the quoted sentence is always shown.
What if a vendor writes something vague?
It stays vague. An intention is not recorded as an event, and that is deliberate — a pipeline full of things that nearly happened is not a pipeline.
Is my mail being read wholesale?
Only the mailboxes your administrator connected for this purpose, and only to record what happened to your own submissions.
Was this helpful?
More in Reading the numbers
Still stuck? Tell us what you are trying to do — a person answers, and we would rather fix the product than explain it twice.