What it is
A proposal is an act the email agent proposes as an Inbox row; a person presses. The email agent is Ask Tightly reading the files that land in a connected inbox, understanding what they say, and proposing one act per file that a person approves. It is Ask Tightly's own Skill, Reads your mail, on the ladder's second rung, Drafts it, you approve; it never sends, never moves money and never writes a record on its own. It is sold with Tightly Pro and switched on in Settings › Email, the row Reads attachments. Until it is on, nothing is read, fetched or proposed, and the rest of email works as it did.
How Tightly decides it
The loop has five steps. Read: only mail whose sender or a recipient matches a supplier's or an account's contacts or domains is read at all; each new thread is read off a queue, and Tightly stamps the time it read each thread on the row, so the wait is a fact and never a guess. Understand: who wrote is decided by the sender's domain against the suppliers' and accounts' recorded domains, one match or nothing, never by a filename or a subject; what a file is comes from the sell-out intake's known layouts or the account's own published mapping; what a PDF says is read with the page cited under each figure. The proposal: one per attachment per act, as an Inbox row and the Mail row's badge; a second read of the same attachment files no second row. Approve: the row is assigned to the mailbox's owner, and a proposal whose owner cannot be resolved is not filed at all. Execute and receipt: the act runs through the object's own writer, and its receipt is the writer's own, such as {n} rows recorded, with the day and the person who pressed.
Four acts can be proposed: a sell-out file into Tightly Connect; a supplier's update to a purchase order (a confirmation, a moved date, a changed quantity or price); an account's claim; and, for a readable sell-out file whose sender's domain names more than one account, naming the account. A supplier invoice is refused before it is read, because Tightly holds no invoice. Corrections teach through the objects that already learn: attaching a file to an account records the domain, and Not this file with a reason becomes a case in the Skill's own evals, never a retrained weight.
The words on the face
| Where | Words |
|---|---|
| Inbox kind | Sell-out file with Import and Not this file; Supplier update with Approve and Ignore; Account claim with Accept and Dismiss |
| Read | Read from the file, Read from page {n}, Two accounts match, Account not named, Not recognised, Not read yet |
| Files | Sell-out · week {n}, Invoice · not read, None |
| State | Imported {date} · {name}, Not this file |
| Settings row | On since {date} · {name}, Off, Sold with Tightly Pro. |
A percentage never prints; where confidence changes what a person does it is one of the words above. Two accounts match is left for a person, because two matches is no match. A file from a domain on no record reads Account not named and offers Attach to an account instead of Import.
What you can do about it
Open the Inbox row or the Mail row's file. The file opens beside what Tightly read from it: the file's first rows or the cited page, the figure row (doors, units and the read word), and one consequence before the one button, "Lands {n} rows as {account}'s week {w}; their grade re-reads now." Press Import; the receipt replaces the button in the intake's own words, {n} rows recorded, the Mail row's state turns and the account's grade re-reads. Not this file with a reason becomes a case for the Skill's evals. After four approvals in a row with no correction on one account's sell-out files, the Skill offers a promotion to Does it, then tells you for that account and that act only, as a row a person accepts; an order or a claim never promotes. Turn the agent off in Settings › Email and nothing is read or proposed.
Glossary line
An act the email agent proposes as an Inbox row; a person presses.