{ "contract_revision": 40, "groups": [ { "id": "setup", "title": "Setting up" }, { "id": "current", "title": "Keeping it current" }, { "id": "reading", "title": "Reading it" }, { "id": "reports", "title": "Reports" }, { "id": "housekeeping", "title": "Housekeeping" }, { "id": "email", "title": "From your email" } ], "prompts": [ { "id": "set-up-my-longbook", "title": "Set up my longbook", "group": "setup", "phrases": [ "Read my 12-month bank statement and help me set up my longbook", "Set up my longbook" ], "aliases": [ "Read my 12-months bank statement along with my onboarding info and help me set up my longbook using longbook's connector and longbook.app/mcp", "Read my bank statement and set up my longbook", "Setup my longbook" ], "attachments": "bank and card statements, ideally the last 12 months, as a PDF with text, an .xlsx or a CSV. Card statements matter too: a bank statement shows only the card bill payment, not what the card was spent on.", "result": "Your longbook filled from your statements: every charge on record, the names you picked in setup filled in where your statements or your answers show them, each account's closing balance set, the charges that clearly repeat planned ahead, and the rest set to repeat once you confirm them. It waits in the Changes screen for you to keep.", "writes": true, "chapter": "first-run", "procedure": [ "1. Check that you are allowed to write to the user's longbook. If not, tell the user which setting to switch on, and stop.", "2. Read the user's statements in the chat. Through the Mac connection, also read the ones in the longbook documents folder. If there are none, ask the user to attach them, and stop. If only bank statements came, ask for the card statements too.", "3. Before reading a line, say which account and which days each statement covers, and today's date.", "4. Read what the user's longbook already holds: members, accounts, commitments, charges, categories, and the names still waiting to be filled in from setup. Know what longbook can hold for each commitment, charge, member and account before you write. Reports are not among them: longbook draws them itself.", "5. Look for the waiting names in the statements first, loosely. A transfer to a person on the 1st of every month could be a salary; a premium line to an insurer could be a health insurance. Record each one under exactly the name the user picked (\"Cook salary\", not \"Ramesh\"), so it leaves the waiting list. Keep the waiting names you cannot find for the questions at the end.", "6. Use what setup already made. Put each statement on the account setup added for its kind. Rename that account to the statement's account first (\"Savings account\" becomes \"HDFC savings 4521\", the last four digits at most), then record its charges under the new name; recording under a new name first would add a second account. \"Self\" is the user. A member setup added by role, such as \"Maid\", is renamed once the user gives the name, and payments are tied to them after that. Never add a second one.", "7. Record every line that is a charge, however small, as paid, on its account. A line that belongs to something already in the longbook is recorded on it, never as a second copy. Name each one the way the user would say it (\"Netflix\", not the bank's reference).", "8. Guess by how much a wrong guess would cost. Copy the amount, the date, the account and the currency exactly as the statement prints them; never guess those. Guess the name, the category, and which commitment a line belongs to, write them, and show them in the table at the end. Ask before writing who a payment is for.", "9. Set a charge to repeat when the statement shows the same payee at least three times, a steady month, quarter or year apart, still going at the statement's end: plan it 24 months ahead, set its price to its latest amount if that changed, and show it in the table. Through a sign-in or a key, the rows you wrote reach the longbook only when the user's app is next open, so list these repeats in the table as ones you will set, and set them after the user answers. Record a repeat that stopped before the statement's end as stopped. A charge seen once or twice that may repeat, such as a yearly premium, is not set to repeat: put your guess of how often in the questions.", "10. Record money in (salary, a refund, interest, cashback) as money in, kept apart from spending.", "11. Skip movements between the user's own accounts: card bill payments, ATM or cash withdrawals, transfers to their own savings, wallet top-ups. One exception: when the longbook already holds that month's card bill, this line marks it paid.", "12. Set each account's balance to its statement's closing balance, dated the statement's last day. If a statement prints none, leave the balance alone and say so at the end. Never work one out yourself.", "13. Count what you wrote. If a waiting name or a yearly charge, such as a premium, may fall before the statements' first day, or the statements held only a few charges, ask for older or longer statements before guessing anything. Never write anything a second time because the longbook looks unchanged: through a sign-in or a key, your changes reach it only when the user's app is next open.", "14. In the end, when responding:", " 1. Send one table of what is now in the user's longbook, by category: how many charges and the total in each, and the names and categories you guessed. List the repeats you set, with how often and how far ahead they are planned, and every charge you could not place, with its date and amount, at the bottom.", " 2. Ask, in one message: for each charge seen once or twice that may come round, your guess of how often; what the unplaced charges were; for each waiting name you could not find, one line with your question and your best guess (\"Health insurance: which insurer, how much, which month? My guess: the premium line on 15 March\"); and anything wrong in the table, a guessed name, category or repeat included. Recommend the user answer by voice.", " 3. In the same message, explain in one sentence that longbook can remember who a payment is for, and ask whether the user wants to add anyone: a spouse, a child, a parent, or someone they employ, like a cook or a driver. First names are enough. For each person setup added by role, such as \"Maid\", ask their first name.", "15. After the user answers:", " 1. Apply the corrections and additions in one pass. Undo a repeat the user says is not one.", " 2. Set each further repeat the user confirms to continue, planned 24 months ahead unless they say otherwise. Through a sign-in or a key, set the repeats you listed too, once the rows are in the longbook; if they are not there yet, ask the user to open longbook first.", " 3. Tell the user it is done: how many commitments, what repeats and how far ahead it is planned, how many months of reports longbook will draw, the balances set, what was skipped and why, and the two or three things you noticed they may want to change. Say it is waiting in the Changes screen.", " 4. Suggest what comes next, leaving out what the user already uses: the other prompts in the Automations section; keeping statements in the longbook documents folder, which their AI can read through the Mac connection; the Siri phrases \"Add an expense in my longbook\", \"Add a commitment in my longbook\" and \"What's my next commitment in my longbook\"; the longbook widget on their iPhone, which shows the next payment; and the longbook Mac app, which shows the next payment in the menu bar." ] }, { "id": "add-my-statement", "title": "Add my statement", "group": "setup", "phrases": [ "Add my statement in my longbook", "Update my longbook from my statements", "Add my statement" ], "aliases": [ "Add my statements", "Import my statement", "Import my statements", "Read the bank statement and add it as charges and reports in my longbook" ], "attachments": "bank or card statements, as a PDF with text, an .xlsx or a CSV. A scanned PDF, a photo or an older .xls file in the documents folder cannot be read: save it as .xlsx or CSV, or attach it in the chat.", "result": "Every charge on the statement recorded as paid, money in kept apart, the account's balance updated, the charges that clearly repeat set to continue, and the rest once you confirm them.", "writes": true, "chapter": "importing-statements", "procedure": [ "1. Check that you are allowed to write to the user's longbook. If not, tell the user which setting to switch on, and stop.", "2. Find the statements: in the chat first, then, through the Mac connection, in the longbook documents folder. If there are none, ask the user to attach them, and stop.", "3. Before reading a line, say which account and which days each statement covers, and today's date.", "4. Read what the user's longbook already holds: commitments, charges, accounts, members, categories, and the names still waiting to be filled in from setup.", "5. Look for the waiting names in the statement first, loosely, and record each one under exactly the name the user picked (\"Cook salary\", not \"Ramesh\"), so it leaves the waiting list.", "6. Put the statement on the account it belongs to. If setup added that account by its kind (\"Savings account\", \"Credit card\"), rename it to the statement's account (\"HDFC savings\", \"Amex 1007\", the last four digits at most) rather than adding a second one.", "7. Record every line that is a charge, however small, as paid, on that account. A line that belongs to something already in the longbook is recorded on it, never as a second copy. Name each new one the way the user would say it (\"Netflix\", not the bank's reference), and put a detail that matters, such as a lender or a policy number, in its notes.", "8. Guess by how much a wrong guess would cost. Copy the amount, the date, the account and the currency exactly as the statement prints them; never guess those. Guess the name, the category, and which commitment a line belongs to, write them, and show them in the table at the end. Ask before writing who a payment is for.", "9. Set a charge to repeat when the statement shows the same payee at least three times, a steady month, quarter or year apart, still going at the statement's end: plan it 24 months ahead, set its price to its latest amount if that changed, and show it in the table. Through a sign-in or a key, the rows you wrote reach the longbook only when the user's app is next open, so list these repeats in the table as ones you will set, and set them after the user answers. Record a repeat that stopped before the statement's end as stopped. A charge seen once or twice that may repeat, such as a yearly premium, is not set to repeat: put your guess of how often in the questions.", "10. Record money in (salary, a refund, interest, cashback) as money in, kept apart from spending.", "11. Skip movements between the user's own accounts: card bill payments, ATM withdrawals, transfers to their own savings, wallet top-ups. One exception: when the longbook already holds that month's card bill, this line marks it paid.", "12. Choose categories from the user's own list first, then longbook's built-in categories. Make a new one only when nothing fits.", "13. Set the account's balance to the statement's closing balance, dated the statement's last day.", "14. In the end, when responding:", " 1. Send a table of what was added, grouped by category, with the charges under each, the names and categories you guessed, and the repeats you set. Put the ones you could not place at the bottom.", " 2. Ask, in one message, what the statement could not tell you: what an unknown payee was, who a payment was for, and how often each charge seen once or twice comes round, with your guesses. Ask the user to correct anything you guessed wrong. Recommend the user answer by voice.", "15. After the user answers:", " 1. Apply the answers in one pass. Undo a repeat the user says is not one.", " 2. Set each further repeat the user confirms to continue, planned 24 months ahead unless they say otherwise. Through a sign-in or a key, set the repeats you listed too, once the rows are in the longbook; if they are not there yet, ask the user to open longbook first.", " 3. Report how many charges were added, what now repeats and how far ahead it is planned, what was skipped and why, and the balance set, or that the statement printed none.", " 4. Say it is waiting in the Changes screen." ] }, { "id": "categorise-my-longbook", "title": "Categorise my longbook", "group": "setup", "phrases": [ "Categorise my longbook" ], "attachments": "none.", "result": "Every commitment without a category gets one. Your AI shows you the ones it guessed, so you can correct any.", "writes": true, "chapter": "categorise-my-longbook", "procedure": [ "1. Check that you are allowed to write to the user's longbook. If not, tell the user which setting to switch on, and stop.", "2. List every commitment without a category, past one-off charges included (the app shows them under \"No category\"), with what each has been charging. The charges are often the clue.", "3. Read the user's own category names first, then longbook's built-in categories.", "4. Where the name says what it is, set it: Netflix is streaming, Airtel is telecom, a person paid on the 1st of each month is a salary.", "5. Intelligently guess a category for the rest or the ones that do not fit.", "6. In the end, when responding:", " 1. Say which ones you set, and that they are waiting in the Changes screen.", " 2. Send one table of the categories you guessed: name, date, amount, and the category you chose. Ask the user to correct any that are wrong, and recommend they answer by voice.", "7. After the user answers:", " 1. Apply the corrections in one pass. Keep a category the user names in their own words.", " 2. Say it is waiting in the Changes screen." ] }, { "id": "add-a-month-report-in-my-longbook", "title": "Add a month report in my longbook", "group": "setup", "phrases": [ "Add September month report in my longbook" ], "template": "Add {month} month report in my longbook", "attachments": "the bank and card statements that cover the month.", "result": "The month's statements recorded, the charges they prove confirmed, and each account's balance set. longbook draws that month's report, with \"Not yet confirmed\" beside the total until every charge in it is confirmed.", "writes": true, "chapter": "month-report", "procedure": [ "1. Check that you are allowed to write to the user's longbook. If not, tell the user which setting to switch on, and stop.", "2. Say which month you are working on, and today's date.", "3. Read the month's charges, and note the passed ones nobody has confirmed: no statement, mail or word from the user behind them. They are what makes the month's report say \"Not yet confirmed\".", "4. Find the month's statements: in the chat first, then, through the Mac connection, in the longbook documents folder. If any are missing, ask the user to attach them.", "5. Import each statement as in \"Add my statement\". A charge nobody had confirmed is confirmed by the statement line that proves it, in place, never as a second copy.", "6. Set each account's balance to its statement's closing balance, dated the statement's last day.", "7. Never write the report yourself, and never fill a gap with an estimate. longbook draws the report from the charges.", "8. In the end, when responding:", " 1. Say what was added and what was confirmed.", " 2. Say longbook draws the month's report the next time the app opens, with \"Not yet confirmed\" beside the total until every passed charge in the month is confirmed.", " 3. Say it is waiting in the Changes screen." ] }, { "id": "add-email-invoices-in-my-longbook", "title": "Add email invoices in my longbook", "group": "current", "phrases": [ "Add email invoices in my longbook" ], "attachments": "none. The user's mail must be connected to their AI.", "result": "This month's bank alerts, receipts, bills and money in from your mail, each recorded once, with nothing doubled.", "writes": true, "needs": [ "mail" ], "chapter": "daily-email-round", "procedure": [ "1. Check that you are allowed to write to the user's longbook. If not, tell the user which setting to switch on, and stop.", "2. Check that you can read the user's mail. If not, say a mail connector is needed, and stop.", "3. Search the mail from the 1st of this month to today for money that moved or is due.", "4. Read what the longbook already holds: accounts with their last four digits, members, commitments, and charges since the 1st. A mail whose amount and day are already recorded is skipped.", "5. From each mail, take only: the amount and its currency; the day the money moved, which is not always the day the mail arrived; who it went to or came from, as a plain name, never a UPI ID or payment address; the account whose last four digits the mail shows; a category; and a member only when the longbook holds them.", "6. Record each mail once, by its kind:", " 1. A bank or card debit alert is a paid charge. When it pays a commitment the longbook holds, it is that commitment's payment, not a new one.", " 2. An autopay chain (consent, OTP, \"deducted\", \"paid\") is one payment, recorded from the mail that says the money left. A pre-debit notice naming a new amount for a commitment is mentioned in the report.", " 3. A receipt or invoice from a seller is usually the same money as an alert. Record it once and let the receipt give the better name, category and note. A receipt paid in cash is a charge of its own.", " 4. A bill that is due: when the longbook holds it, check its next charge's date and amount, and add nothing. Otherwise, add an unpaid charge at the due date.", " 5. Money in, once the bank says it was credited, is money in. A notice that a refund is on its way is not.", " 6. An insurance or renewal notice: when the longbook holds it, check the next charge against it, and correct it only when the notice comes from the payee itself; otherwise, mention the difference. When the longbook does not hold it, add one unpaid charge at the due date, and propose how often it repeats in the report.", " 7. A credit card statement is one card bill, named for the card and the month it falls due (\"Coral card bill, October 2026\"), at the total due, on that card, unpaid, at its due date, recorded as a transfer, never as spending. A bill already recorded for that month is corrected, never added twice.", " 8. A card bill payment marks that month's card bill paid.", " 9. Skip wallet top-ups, transfers to the user's own accounts, and investments, unless the longbook holds that payment as a commitment of its own, such as a monthly investment plan: then it is that commitment's payment. Skip OTPs, sign-in alerts, offers, newsletters, brokerage and fund statements, tax notices, and any mail with no amount.", "7. Use the last four digits of a card or account only to match. Never write a card or account number, an OTP or a tax ID.", "8. In the end, when responding:", " 1. Say how many charges were added, and which mails were skipped and why, in a line.", " 2. Say what needs the user's word: something that looks recurring, or an account the longbook does not hold.", " 3. Say it is waiting in the Changes screen." ] }, { "id": "set-up-a-daily-longbook-email-round", "title": "Set up a daily longbook email round", "group": "current", "phrases": [ "Go to longbook.app/mcp and set up a daily email round for my longbook, as longbook recommends" ], "aliases": [ "Go to longbook.app/mcp and set yourself up for a daily longbook email round, as longbook recommends", "Set yourself up for a daily longbook email round" ], "attachments": "none. The user's mail must be connected, and their AI's app must support scheduled tasks.", "result": "Your AI reads your mail every morning at 6 and records the money that moved, so your longbook stays current without you asking.", "writes": true, "needs": [ "mail", "scheduler" ], "chapter": "daily-email-round", "procedure": [ "1. Check that you are allowed to write to the user's longbook. If not, tell the user which setting to switch on, and stop.", "2. Check that you can read the user's mail. If not, say a mail connector is needed, and stop.", "3. Create a scheduled task that runs every day at 6 in the morning, in the user's time zone. Its instruction: read longbook's daily email round method from the longbook connector, then do one round. Each morning then follows the method as it stands that day.", "4. If your app has no scheduled tasks, say so, and offer to run the round whenever the user asks.", "5. Run the first round now, so the user sees in the Changes screen what a morning looks like.", "6. Each round:", " 1. First fix anything from an earlier round that the app could not apply, using the real names in the longbook, and file it again in place of the failed one.", " 2. Read the last day of mail, 36 hours to be safe, and record it as in \"Add email invoices in my longbook\".", " 3. Only add, and mark paid what a mail proves. Never cancel, never change a price unless the notice comes from the payee itself, and never decide that something repeats; propose those in the report.", " 4. When a mail marks a charge paid and nothing is planned after it, plan the next one, one cycle on, at its current price, and say so in the report.", " 5. End with a short report: what was added, what was skipped, what needs the user's word, and that it is waiting in the Changes screen. Then stop.", "7. In the end, when responding:", " 1. Say the round is set for 6 every morning, show what the first round added, and say it is waiting in the Changes screen." ] }, { "id": "add-document-invoices-in-my-longbook", "title": "Add document invoices in my longbook", "group": "current", "phrases": [ "Add document invoices in my longbook" ], "attachments": "invoices, receipts and bills: attached in the chat, or kept in the longbook documents folder as a PDF with text, an .xlsx or a CSV. A photo or a scanned receipt can be read only when attached in the chat.", "result": "The invoices, receipts and bills you attach, or keep in the longbook documents folder, recorded as charges with the file's name in their notes, without doubling what your statements or mail already recorded.", "writes": true, "chapter": "document-invoices", "procedure": [ "1. Check that you are allowed to write to the user's longbook. If not, tell the user which setting to switch on, and stop.", "2. Find the files: in the chat first, then, through the Mac connection, in the longbook documents folder. Look in the Mac's own Documents and Downloads folders only if your app can read files there. Otherwise, ask the user to attach them.", "3. Treat each invoice or receipt as one charge. It is paid on the day it names when it says paid or that day has passed. It is unpaid at its due date when the due date is ahead.", "4. Name it the way the user would say it (\"Plumber, kitchen tap\"), never by the invoice number. Take the amount, the currency and the day only as printed.", "5. Search the longbook first. A charge already recorded from a mail or a statement, for the same amount and day, is the same money: the invoice gives it a better name and note, never a second copy. When the payee is a commitment the longbook holds, the invoice is that commitment's payment.", "6. Name the file in the charge's notes. Never copy its contents.", "7. In the end, when responding:", " 1. List what was added or updated.", " 2. Say it is waiting in the Changes screen." ] }, { "id": "add-a-commitment-or-an-expense", "title": "Add a commitment or an expense", "group": "current", "phrases": [ "Add a commitment in my longbook", "Add an expense in my longbook", "Add my new gym membership to my longbook" ], "attachments": "none. A receipt or a sign-up mail helps, if the user has one.", "result": "A new commitment planned ahead, or a one-time expense recorded, on the account and for the person you name.", "writes": true, "chapter": "working-method", "procedure": [ "1. Check that you are allowed to write to the user's longbook. If not, tell the user which setting to switch on, and stop.", "2. Search the longbook first. If it already holds this commitment, update that one; never add a second.", "3. Ask, in one message, for what is missing: the name as the user says it, the amount and currency, how often it repeats or whether it is one time, the first or only charge day, which account pays it, and who it is for. Ask for a category only if you cannot tell. Recommend the user answer by voice.", "4. Add a repeating commitment with its first charge, planned 24 months ahead unless the user says otherwise. An expense is one charge, with nothing planned. Money the user receives, such as a salary or rent from a tenant, is added as money in, kept apart from spending.", "5. Use only the accounts and members the user names. Add a new one only when the user names one the longbook does not hold.", "6. Add the three details that matter for its kind, as listed in the Notes chapter of longbook's guide, as far as the user stated them.", "7. In the end, when responding:", " 1. Say what was added, and how far ahead it is planned.", " 2. Say it is waiting in the Changes screen." ] }, { "id": "what-do-i-pay-next", "title": "What do I pay next?", "group": "reading", "phrases": [ "What's my next commitment in my longbook", "What do I pay next?" ], "attachments": "none.", "result": "The next day you owe something, and what is due that day. Nothing in your longbook changes.", "writes": false, "procedure": [ "1. Read the nearest day anything is still owed, and every charge on it.", "2. Quote longbook's figures as they are: per currency, never converted, never recalculated.", "3. In the end, when responding:", " 1. Answer in two or three lines. List card bills and other transfers between the user's own accounts apart, never added in.", " 2. Write nothing." ] }, { "id": "what-is-coming-in-the-next-30-days", "title": "What is coming in the next 30 days?", "group": "reading", "phrases": [ "What is coming in my longbook in the next 30 days?", "What is coming in the next 30 days?", "What do I owe this month?" ], "attachments": "none.", "result": "Everything due in the next 30 days, or the period you name, by day, with the total per currency. Nothing in your longbook changes.", "writes": false, "procedure": [ "1. Read the charges due in the period the user names, the next 30 days if they do not say.", "2. Note any commitment whose plan runs out inside that period.", "3. In the end, when responding:", " 1. Group the charges by day, name the large ones, and give the total per currency.", " 2. List card bills and other transfers between the user's own accounts apart, with their own total, never added in.", " 3. If a plan runs out inside the period, say so, and offer to plan it further ahead.", " 4. Write nothing." ] }, { "id": "what-did-i-spend-in-a-month", "title": "What did I spend in a month?", "group": "reading", "phrases": [ "What did I spend in July in my longbook?", "What did I spend in July?" ], "template": "What did I spend in {month} in my longbook?", "aliases": [ "What did I spend in {month}?" ], "attachments": "none.", "result": "What you spent in that month, and what is not yet confirmed. Through the Mac connection this comes from longbook's report; otherwise from your charges, including ones nobody has confirmed yet. Nothing in your longbook changes.", "writes": false, "chapter": "reading-reports", "procedure": [ "1. Through the Mac connection, read the report for the month the user names, and quote its total, its number of charges and its money in. Never recalculate them.", "2. If the report says \"Not yet confirmed\", say the total is what longbook can account for so far, and offer \"Add a month report in my longbook\" for that month.", "3. If the report shows no change against the month before, say longbook would not draw one: the month is not over, one of the two months is short of confirmed charges, or the month before has no confirmed spending in this currency. Never read that as nothing spent, and never work out a change yourself.", "4. If there is no report for that month, say why: nothing in it is confirmed yet. Offer \"Add a month report in my longbook\".", "5. Without the Mac connection, read that month's spending from longbook, and say it counts every charge written for the month, including ones nobody has confirmed and, for a month still running, the ones still to come.", "6. In the end, when responding:", " 1. Answer with the figures, and what they leave out.", " 2. Write nothing." ] }, { "id": "what-renews-this-year", "title": "What renews this year?", "group": "reading", "phrases": [ "What renews this year in my longbook?", "What renews this year?", "Which premiums are due before March?" ], "attachments": "none.", "result": "Your yearly, half-yearly and quarterly payments due in the next 12 months, or before the day you name, in date order. Nothing in your longbook changes.", "writes": false, "procedure": [ "1. Read what falls due in the period the user names (the next 12 months for \"this year\") and does not repeat monthly: insurance premiums, whether yearly, half-yearly or quarterly, plus domains, annual memberships, school fees and licences.", "2. Note which of them have nothing planned after their next charge.", "3. In the end, when responding:", " 1. Give each one's next charge day and amount, in date order.", " 2. Say which have nothing planned after their next charge, and offer to plan them further ahead.", " 3. Write nothing." ] }, { "id": "make-my-weekly-longbook-page", "title": "Make my weekly longbook page", "group": "reading", "phrases": [ "Make my weekly longbook page", "Give me my longbook week" ], "attachments": "none.", "result": "One page for the week: what is due in the next 7 days, what you spent last week, what renews in the next 30 days, and anything waiting for you. Nothing in your longbook changes.", "writes": false, "procedure": [ "1. Read what is due in the next 7 days, and every charge on each of those days.", "2. Read last week's charges, Monday to Sunday, and this month's spending so far, up to today, per currency.", "3. Read what falls due in the next 30 days and does not repeat monthly: insurance premiums, memberships, domains, yearly subscriptions.", "4. Check what needs the user: names still waiting to be filled in from setup, plans running short, and suggestions the app could not apply.", "5. Quote longbook's figures as they are: per currency, never converted, never recalculated. List card bills and transfers between the user's own accounts apart, never added in.", "6. In the end, when responding:", " 1. If your app can make a page, such as a Claude artifact, make one page with four parts: Due this week, Last week, Renewing soon, Needs you. Otherwise, give the same four parts as short sections.", " 2. If your app has scheduled tasks, offer to make the page every Monday morning, in the user's time zone.", " 3. Write nothing." ] }, { "id": "create-a-report-in-my-longbook", "title": "Create a report in my longbook", "group": "reports", "phrases": [ "Create a report in my longbook" ], "attachments": "none.", "result": "A report over the days, accounts, people and categories you choose, on the Reports screen the next time the app is open. It counts confirmed charges only.", "writes": true, "chapter": "create-a-report", "procedure": [ "1. Check that you are allowed to write to the user's longbook. If not, tell the user which setting to switch on, and stop.", "2. Ask, in one message: a name for the report; its first and last day (the first is today or earlier, the last may be ahead, and it covers 366 days at most); which accounts and which members (choosing none means everyone); and categories, only if the user wants to narrow by them. Recommend the user answer by voice.", "3. Read the real names of the user's accounts, members and categories, and use them exactly as the longbook holds them. Never create anything to fit a report.", "4. Ask longbook to draw the report, once. Never state its figures yourself.", "5. In the end, when responding:", " 1. Say it appears on the Reports screen the next time the app is open, counting confirmed charges only, like every report.", " 2. Say nothing waits in the Changes screen. To change what the report says, fix the charges behind it, and longbook redraws it." ] }, { "id": "make-a-report-of-my-trip", "title": "Make a report of my trip", "group": "reports", "phrases": [ "Make a report of my Goa trip in my longbook", "Make a report of my Goa trip" ], "aliases": [ "Make a report of my {trip} trip in my longbook", "Make a report of my {trip} trip", "Make me a report of my {trip} trip", "Make me a report of the {trip} trip" ], "attachments": "none.", "result": "A report of your trip's spending on the Reports screen, filling in as the trip's charges are confirmed.", "writes": true, "chapter": "create-a-report", "procedure": [ "1. Check that you are allowed to write to the user's longbook. If not, tell the user which setting to switch on, and stop.", "2. Ask for the trip's name, its first and last day, and which accounts and members it covers. For a trip still under way, the last day is the day the user comes home. Recommend the user answer by voice.", "3. Ask longbook to draw it as in \"Create a report in my longbook\", named for the trip.", "4. Do not also suggest trip mode in the app: it starts from today, and would draw a second report of the same trip.", "5. In the end, when responding:", " 1. Say it appears on the Reports screen, and fills in as the trip's charges are confirmed." ] }, { "id": "tidy-my-longbook", "title": "Tidy my longbook", "group": "housekeeping", "phrases": [ "Tidy my longbook" ], "attachments": "none.", "result": "Doubled charges, bank-style names and odd categories found, and fixed once you approve each change.", "writes": true, "chapter": "working-method", "procedure": [ "1. Check that you are allowed to write to the user's longbook. If not, tell the user which setting to switch on, and stop.", "2. Read every commitment and charge, past and planned.", "3. Find what looks doubled: one payee under two names, or one charge recorded twice, from a mail and from a statement.", "4. Find names written the bank's way rather than the user's, and categories that have an equivalent among longbook's built-in categories.", "5. Change nothing on your own.", "6. In the end, when responding:", " 1. Propose each change in one table, and ask. Recommend the user answer by voice.", "7. After the user answers, apply the answers in one pass:", " 1. For one charge recorded twice, keep the copy on the commitment the longbook already holds, give it the better name and note, and remove the other.", " 2. For one payee under two names, give both the user's name, or copy the twin's charges onto the main one exactly as they are, then delete the twin only when the user says so, naming its paid charges first.", " 3. Never lose a charge that happened.", " 4. Say it is waiting in the Changes screen." ] }, { "id": "set-up-a-morning-brief", "title": "Set up a morning brief", "group": "housekeeping", "phrases": [ "Set up a morning brief for my longbook", "Set yourself up for a longbook morning brief" ], "attachments": "none. The user's AI's app must support scheduled tasks.", "result": "A short summary every morning of what is due today and in the next 30 days. Nothing in your longbook changes.", "writes": false, "needs": [ "scheduler" ], "chapter": "unattended-runs", "procedure": [ "1. This brief only reads, unlike the fuller brief in longbook's guide, which also files the day's mail. For that, use \"Set up a daily longbook email round\".", "2. Ask what time the user wants the brief, and create a scheduled task for that time in their time zone. If your app has no scheduled tasks, say so, and offer to give the brief whenever the user asks.", "3. Each morning:", " 1. Read what is due today and in the next 30 days, and give the lines the user asked for: the next payment, the large charges this week, any plan running short.", " 2. Through a sign-in or a key, say how many suggestions are waiting for the app to pick them up, and name any it could not apply, with the reason. Through the Mac connection, say anything waiting is already in the Changes screen.", " 3. Write nothing.", "4. In the end, when responding:", " 1. Say what time the brief is set for, and give today's brief once, so the user sees what it looks like." ] }, { "id": "find-subscriptions-from-my-email", "title": "Find subscriptions from my email", "group": "email", "phrases": [ "Find subscriptions from my email and add them in my longbook" ], "attachments": "none. The user's mail must be connected to their AI.", "result": "Your subscriptions found in the last 12 months of your mail: each one with its receipts as charges, the ones that clearly repeat planned ahead, and trials and price changes as the mails state them.", "writes": true, "needs": [ "mail" ], "chapter": "daily-email-round", "procedure": [ "1. Check that you are allowed to write to the user's longbook. If not, tell the user which setting to switch on, and stop.", "2. Check that you can read the user's mail. If not, say a mail connector is needed, and stop.", "3. Search the period the user names; if they do not say, the last 12 months. Look for subscription receipts and renewals (App Store, Google Play, streaming, software, cloud storage, memberships), trial starts, price-change notices and cancellation confirmations.", "4. Read what the longbook already holds: accounts with their last four digits, members, commitments, and charges in that period. A mail whose amount and day are already recorded is skipped, and a mail for a commitment the longbook holds goes on it, never as a second copy.", "5. Copy the amount, the currency and the day the money moved exactly as the mail states them; never guess those. Name each one the way the user would say it, never by a payment handle or an order number. Use the last four digits of a card or account only to match, and never write a card or account number, an OTP or a tax ID.", "6. What each mail becomes:", " 1. Each subscription is one commitment, named the way the user would say it (\"Netflix\"), with every receipt a paid charge at its date and amount.", " 2. A trial that starts is the subscription marked as a free trial, with its first charge on the day the trial ends, at the price the mail states.", " 3. A price-change notice from the provider changes the price from the day it names. A cancellation confirmation ends the subscription on the day it names.", "7. Guess the category and which commitment a mail belongs to, write them, and show them in the table at the end. Set something to repeat only when the mails show it at least three times, a steady month, quarter or year apart, or a mail from the provider states how often it is billed; otherwise put your guess in the questions. Through a sign-in or a key, list those repeats in the table and set them after the user answers, once the rows are in the longbook. Ask before writing who a payment is for.", "8. In the end, when responding:", " 1. Send one table of what was added, grouped by category, with the names and categories you guessed and the repeats you set, and one line on what was skipped and why.", " 2. Ask, in one message, about anything you could not place, and how often each one seen once or twice comes round, with your guesses. Recommend the user answer by voice.", " 3. Say it is waiting in the Changes screen.", "9. After the user answers:", " 1. Apply the answers in one pass.", " 2. Set each further repeat the user confirms to continue, planned 24 months ahead unless they say otherwise. Through a sign-in or a key, set the repeats you listed too, once the rows are in the longbook; if they are not there yet, ask the user to open longbook first.", " 3. Say it is waiting in the Changes screen." ] }, { "id": "find-expenses-from-my-email", "title": "Find expenses from my email", "group": "email", "phrases": [ "Find expenses from my email and add them in my longbook" ], "attachments": "none. The user's mail must be connected to their AI.", "result": "This month's spending from your mail's bank alerts and receipts, each recorded once as a paid charge.", "writes": true, "needs": [ "mail" ], "chapter": "daily-email-round", "procedure": [ "1. Check that you are allowed to write to the user's longbook. If not, tell the user which setting to switch on, and stop.", "2. Check that you can read the user's mail. If not, say a mail connector is needed, and stop.", "3. Search the period the user names; if they do not say, this month. Look for bank and card debit alerts, UPI payment confirmations, and receipts for money spent.", "4. Read what the longbook already holds: accounts with their last four digits, members, commitments, and charges in that period. A mail whose amount and day are already recorded is skipped, and a mail for a commitment the longbook holds goes on it, never as a second copy.", "5. Copy the amount, the currency and the day the money moved exactly as the mail states them; never guess those. Name each one the way the user would say it, never by a payment handle or an order number. Use the last four digits of a card or account only to match, and never write a card or account number, an OTP or a tax ID.", "6. What each mail becomes:", " 1. Each payment is one paid charge at its real date and amount. When it pays a commitment the longbook holds, it is that commitment's payment, not a new one.", " 2. A receipt that matches an alert is the same money: record it once, and let the receipt give the better name.", " 3. Skip money in, transfers between the user's own accounts, wallet top-ups, OTPs and offers.", "7. Guess the category and which commitment a mail belongs to, write them, and show them in the table at the end. Set something to repeat only when the mails show it at least three times, a steady month, quarter or year apart, or a mail from the provider states how often it is billed; otherwise put your guess in the questions. Through a sign-in or a key, list those repeats in the table and set them after the user answers, once the rows are in the longbook. Ask before writing who a payment is for.", "8. In the end, when responding:", " 1. Send one table of what was added, grouped by category, with the names and categories you guessed and the repeats you set, and one line on what was skipped and why.", " 2. Ask, in one message, about anything you could not place, and how often each one seen once or twice comes round, with your guesses. Recommend the user answer by voice.", " 3. Say it is waiting in the Changes screen.", "9. After the user answers:", " 1. Apply the answers in one pass.", " 2. Set each further repeat the user confirms to continue, planned 24 months ahead unless they say otherwise. Through a sign-in or a key, set the repeats you listed too, once the rows are in the longbook; if they are not there yet, ask the user to open longbook first.", " 3. Say it is waiting in the Changes screen." ] }, { "id": "find-invoices-from-my-email", "title": "Find invoices from my email", "group": "email", "phrases": [ "Find invoices from my email and add them in my longbook" ], "attachments": "none. The user's mail must be connected to their AI.", "result": "The invoices and receipts in the last 12 months of your mail, each recorded once as a charge, paid or due.", "writes": true, "needs": [ "mail" ], "chapter": "daily-email-round", "procedure": [ "1. Check that you are allowed to write to the user's longbook. If not, tell the user which setting to switch on, and stop.", "2. Check that you can read the user's mail. If not, say a mail connector is needed, and stop.", "3. Search the period the user names; if they do not say, the last 12 months. Look for invoices, tax invoices and receipts from sellers and service providers, and \"payment received\" mails.", "4. Read what the longbook already holds: accounts with their last four digits, members, commitments, and charges in that period. A mail whose amount and day are already recorded is skipped, and a mail for a commitment the longbook holds goes on it, never as a second copy.", "5. Copy the amount, the currency and the day the money moved exactly as the mail states them; never guess those. Name each one the way the user would say it, never by a payment handle or an order number. Use the last four digits of a card or account only to match, and never write a card or account number, an OTP or a tax ID.", "6. What each mail becomes:", " 1. Each invoice or receipt is one charge: paid on the day it says it was paid, or unpaid at its due date when that day is ahead.", " 2. Name it by what was bought or who it was from (\"Plumber, kitchen tap\"), never by the invoice number.", " 3. An invoice that matches a charge already recorded from a bank alert or a statement gives it a better name and note, never a second copy.", "7. Guess the category and which commitment a mail belongs to, write them, and show them in the table at the end. Set something to repeat only when the mails show it at least three times, a steady month, quarter or year apart, or a mail from the provider states how often it is billed; otherwise put your guess in the questions. Through a sign-in or a key, list those repeats in the table and set them after the user answers, once the rows are in the longbook. Ask before writing who a payment is for.", "8. In the end, when responding:", " 1. Send one table of what was added, grouped by category, with the names and categories you guessed and the repeats you set, and one line on what was skipped and why.", " 2. Ask, in one message, about anything you could not place, and how often each one seen once or twice comes round, with your guesses. Recommend the user answer by voice.", " 3. Say it is waiting in the Changes screen.", "9. After the user answers:", " 1. Apply the answers in one pass.", " 2. Set each further repeat the user confirms to continue, planned 24 months ahead unless they say otherwise. Through a sign-in or a key, set the repeats you listed too, once the rows are in the longbook; if they are not there yet, ask the user to open longbook first.", " 3. Say it is waiting in the Changes screen." ] }, { "id": "find-insurances-from-my-email", "title": "Find insurances from my email", "group": "email", "phrases": [ "Find insurances from my email and add them in my longbook" ], "attachments": "none. The user's mail must be connected to their AI.", "result": "Your insurance policies found in your mail: each with its premiums as charges, its next premium planned, and its policy details in its notes.", "writes": true, "needs": [ "mail" ], "chapter": "daily-email-round", "procedure": [ "1. Check that you are allowed to write to the user's longbook. If not, tell the user which setting to switch on, and stop.", "2. Check that you can read the user's mail. If not, say a mail connector is needed, and stop.", "3. Search the period the user names; if they do not say, the last 12 months. Look for policy issued and renewed mails, premium receipts and renewal reminders from insurers and their apps.", "4. Read what the longbook already holds: accounts with their last four digits, members, commitments, and charges in that period. A mail whose amount and day are already recorded is skipped, and a mail for a commitment the longbook holds goes on it, never as a second copy.", "5. Copy the amount, the currency and the day the money moved exactly as the mail states them; never guess those. Name each one the way the user would say it, never by a payment handle or an order number. Use the last four digits of a card or account only to match, and never write a card or account number, an OTP or a tax ID.", "6. What each mail becomes:", " 1. Each policy is one commitment, named the way the user would say it (\"Health insurance\"), with every premium receipt a paid charge.", " 2. Set it to repeat on the cycle the policy states: yearly, half-yearly, quarterly or monthly. A renewal reminder is the next premium, unpaid, at its due date and amount.", " 3. Its notes hold the policy number, the policy's official name and the insurer. A policy number 13 to 19 digits long reads like a card number and is refused: write its last four digits.", "7. Guess the category and which commitment a mail belongs to, write them, and show them in the table at the end. Set something to repeat only when the mails show it at least three times, a steady month, quarter or year apart, or a mail from the provider states how often it is billed; otherwise put your guess in the questions. Through a sign-in or a key, list those repeats in the table and set them after the user answers, once the rows are in the longbook. Ask before writing who a payment is for.", "8. In the end, when responding:", " 1. Send one table of what was added, grouped by category, with the names and categories you guessed and the repeats you set, and one line on what was skipped and why.", " 2. Ask, in one message, about anything you could not place, and how often each one seen once or twice comes round, with your guesses. Recommend the user answer by voice.", " 3. Say it is waiting in the Changes screen.", "9. After the user answers:", " 1. Apply the answers in one pass.", " 2. Set each further repeat the user confirms to continue, planned 24 months ahead unless they say otherwise. Through a sign-in or a key, set the repeats you listed too, once the rows are in the longbook; if they are not there yet, ask the user to open longbook first.", " 3. Say it is waiting in the Changes screen." ] }, { "id": "find-purchases-from-my-email", "title": "Find purchases from my email", "group": "email", "phrases": [ "Find purchases from my email and add them in my longbook" ], "attachments": "none. The user's mail must be connected to their AI.", "result": "Your orders from the last 3 months of your mail, each recorded once as a paid charge named for what you bought.", "writes": true, "needs": [ "mail" ], "chapter": "daily-email-round", "procedure": [ "1. Check that you are allowed to write to the user's longbook. If not, tell the user which setting to switch on, and stop.", "2. Check that you can read the user's mail. If not, say a mail connector is needed, and stop.", "3. Search the period the user names; if they do not say, the last 3 months. Look for order confirmations and invoices from shops and marketplaces.", "4. Read what the longbook already holds: accounts with their last four digits, members, commitments, and charges in that period. A mail whose amount and day are already recorded is skipped, and a mail for a commitment the longbook holds goes on it, never as a second copy.", "5. Copy the amount, the currency and the day the money moved exactly as the mail states them; never guess those. Name each one the way the user would say it, never by a payment handle or an order number. Use the last four digits of a card or account only to match, and never write a card or account number, an OTP or a tax ID.", "6. What each mail becomes:", " 1. Each order is one paid charge at its total, named for what was bought (\"Amazon, running shoes\").", " 2. A cancelled order is skipped. A refund is money in, kept apart from spending.", " 3. An order that matches a bank or card alert is the same money: record it once.", "7. Guess the category and which commitment a mail belongs to, write them, and show them in the table at the end. Set something to repeat only when the mails show it at least three times, a steady month, quarter or year apart, or a mail from the provider states how often it is billed; otherwise put your guess in the questions. Through a sign-in or a key, list those repeats in the table and set them after the user answers, once the rows are in the longbook. Ask before writing who a payment is for.", "8. In the end, when responding:", " 1. Send one table of what was added, grouped by category, with the names and categories you guessed and the repeats you set, and one line on what was skipped and why.", " 2. Ask, in one message, about anything you could not place, and how often each one seen once or twice comes round, with your guesses. Recommend the user answer by voice.", " 3. Say it is waiting in the Changes screen.", "9. After the user answers:", " 1. Apply the answers in one pass.", " 2. Set each further repeat the user confirms to continue, planned 24 months ahead unless they say otherwise. Through a sign-in or a key, set the repeats you listed too, once the rows are in the longbook; if they are not there yet, ask the user to open longbook first.", " 3. Say it is waiting in the Changes screen." ] }, { "id": "find-bills-from-my-email", "title": "Find bills from my email", "group": "email", "phrases": [ "Find bills from my email and add them in my longbook" ], "attachments": "none. The user's mail must be connected to their AI.", "result": "Your bills from the last 3 months of your mail: what you paid recorded, what is due planned, and each card's monthly bill kept apart from spending.", "writes": true, "needs": [ "mail" ], "chapter": "daily-email-round", "procedure": [ "1. Check that you are allowed to write to the user's longbook. If not, tell the user which setting to switch on, and stop.", "2. Check that you can read the user's mail. If not, say a mail connector is needed, and stop.", "3. Search the period the user names; if they do not say, the last 3 months. Look for electricity, water, gas, phone, internet and rent bills, due or paid, and credit card statements.", "4. Read what the longbook already holds: accounts with their last four digits, members, commitments, and charges in that period. A mail whose amount and day are already recorded is skipped, and a mail for a commitment the longbook holds goes on it, never as a second copy.", "5. Copy the amount, the currency and the day the money moved exactly as the mail states them; never guess those. Name each one the way the user would say it, never by a payment handle or an order number. Use the last four digits of a card or account only to match, and never write a card or account number, an OTP or a tax ID.", "6. What each mail becomes:", " 1. A bill the longbook already holds is that commitment's charge: mark it paid when the mail says so, or check the next charge's date and amount when it is due.", " 2. A new bill is a charge of its own: paid when the mail says so, or unpaid at its due date.", " 3. A credit card statement is one card bill for that month, named for the card and the month (\"Coral card bill, October 2026\"), at the total due, unpaid, recorded as a transfer, never as spending. A card bill payment marks it paid.", "7. Guess the category and which commitment a mail belongs to, write them, and show them in the table at the end. Set something to repeat only when the mails show it at least three times, a steady month, quarter or year apart, or a mail from the provider states how often it is billed; otherwise put your guess in the questions. Through a sign-in or a key, list those repeats in the table and set them after the user answers, once the rows are in the longbook. Ask before writing who a payment is for.", "8. In the end, when responding:", " 1. Send one table of what was added, grouped by category, with the names and categories you guessed and the repeats you set, and one line on what was skipped and why.", " 2. Ask, in one message, about anything you could not place, and how often each one seen once or twice comes round, with your guesses. Recommend the user answer by voice.", " 3. Say it is waiting in the Changes screen.", "9. After the user answers:", " 1. Apply the answers in one pass.", " 2. Set each further repeat the user confirms to continue, planned 24 months ahead unless they say otherwise. Through a sign-in or a key, set the repeats you listed too, once the rows are in the longbook; if they are not there yet, ask the user to open longbook first.", " 3. Say it is waiting in the Changes screen." ] }, { "id": "find-loans-and-emis-from-my-email", "title": "Find loans and EMIs from my email", "group": "email", "phrases": [ "Find loans and EMIs from my email and add them in my longbook" ], "attachments": "none. The user's mail must be connected to their AI.", "result": "Your loans and EMIs found in your mail: each loan with its EMIs as charges, planned ahead to its end when the mails state it.", "writes": true, "needs": [ "mail" ], "chapter": "daily-email-round", "procedure": [ "1. Check that you are allowed to write to the user's longbook. If not, tell the user which setting to switch on, and stop.", "2. Check that you can read the user's mail. If not, say a mail connector is needed, and stop.", "3. Search the period the user names; if they do not say, the last 12 months. Look for EMI debit alerts, loan statements, sanction letters and loan closure mails.", "4. Read what the longbook already holds: accounts with their last four digits, members, commitments, and charges in that period. A mail whose amount and day are already recorded is skipped, and a mail for a commitment the longbook holds goes on it, never as a second copy.", "5. Copy the amount, the currency and the day the money moved exactly as the mail states them; never guess those. Name each one the way the user would say it, never by a payment handle or an order number. Use the last four digits of a card or account only to match, and never write a card or account number, an OTP or a tax ID.", "6. What each mail becomes:", " 1. Each loan is one commitment, named the way the user would say it (\"Car loan\"), in the EMI category, with every EMI a paid charge.", " 2. Set it to repeat monthly when the mails show the EMI at least three times, or a loan letter states the EMI. When a mail states when the loan ends, nothing is planned past that day.", " 3. Its notes hold the lender, when the loan ends, and the last four digits of the loan account, never the whole number.", "7. Guess the category and which commitment a mail belongs to, write them, and show them in the table at the end. Set something to repeat only when the mails show it at least three times, a steady month, quarter or year apart, or a mail from the provider states how often it is billed; otherwise put your guess in the questions. Through a sign-in or a key, list those repeats in the table and set them after the user answers, once the rows are in the longbook. Ask before writing who a payment is for.", "8. In the end, when responding:", " 1. Send one table of what was added, grouped by category, with the names and categories you guessed and the repeats you set, and one line on what was skipped and why.", " 2. Ask, in one message, about anything you could not place, and how often each one seen once or twice comes round, with your guesses. Recommend the user answer by voice.", " 3. Say it is waiting in the Changes screen.", "9. After the user answers:", " 1. Apply the answers in one pass.", " 2. Set each further repeat the user confirms to continue, planned 24 months ahead unless they say otherwise. Through a sign-in or a key, set the repeats you listed too, once the rows are in the longbook; if they are not there yet, ask the user to open longbook first.", " 3. Say it is waiting in the Changes screen." ] }, { "id": "find-travel-bookings-from-my-email", "title": "Find travel bookings from my email", "group": "email", "phrases": [ "Find travel bookings from my email and add them in my longbook" ], "attachments": "none. The user's mail must be connected to their AI.", "result": "Your bookings from the last 12 months of your mail: flights, trains, hotels and cabs, each recorded as a paid charge with where and when.", "writes": true, "needs": [ "mail" ], "chapter": "daily-email-round", "procedure": [ "1. Check that you are allowed to write to the user's longbook. If not, tell the user which setting to switch on, and stop.", "2. Check that you can read the user's mail. If not, say a mail connector is needed, and stop.", "3. Search the period the user names; if they do not say, the last 12 months. Look for flight, train, bus, hotel and cab bookings, and their cancellations.", "4. Read what the longbook already holds: accounts with their last four digits, members, commitments, and charges in that period. A mail whose amount and day are already recorded is skipped, and a mail for a commitment the longbook holds goes on it, never as a second copy.", "5. Copy the amount, the currency and the day the money moved exactly as the mail states them; never guess those. Name each one the way the user would say it, never by a payment handle or an order number. Use the last four digits of a card or account only to match, and never write a card or account number, an OTP or a tax ID.", "6. What each mail becomes:", " 1. Each booking is one paid charge at its total, on the day the money moved, in the travel category.", " 2. Its notes hold where, the travel dates, and where it was booked.", " 3. A cancellation refund is money in. When several bookings belong to one trip, offer \"Make a report of my trip\".", "7. Guess the category and which commitment a mail belongs to, write them, and show them in the table at the end. Set something to repeat only when the mails show it at least three times, a steady month, quarter or year apart, or a mail from the provider states how often it is billed; otherwise put your guess in the questions. Through a sign-in or a key, list those repeats in the table and set them after the user answers, once the rows are in the longbook. Ask before writing who a payment is for.", "8. In the end, when responding:", " 1. Send one table of what was added, grouped by category, with the names and categories you guessed and the repeats you set, and one line on what was skipped and why.", " 2. Ask, in one message, about anything you could not place, and how often each one seen once or twice comes round, with your guesses. Recommend the user answer by voice.", " 3. Say it is waiting in the Changes screen.", "9. After the user answers:", " 1. Apply the answers in one pass.", " 2. Set each further repeat the user confirms to continue, planned 24 months ahead unless they say otherwise. Through a sign-in or a key, set the repeats you listed too, once the rows are in the longbook; if they are not there yet, ask the user to open longbook first.", " 3. Say it is waiting in the Changes screen." ] }, { "id": "find-money-in-from-my-email", "title": "Find money in from my email", "group": "email", "phrases": [ "Find money in from my email and add them in my longbook" ], "attachments": "none. The user's mail must be connected to their AI.", "result": "Your salary, refunds, interest and other money in from the last 12 months of your mail, kept apart from spending.", "writes": true, "needs": [ "mail" ], "chapter": "daily-email-round", "procedure": [ "1. Check that you are allowed to write to the user's longbook. If not, tell the user which setting to switch on, and stop.", "2. Check that you can read the user's mail. If not, say a mail connector is needed, and stop.", "3. Search the period the user names; if they do not say, the last 12 months. Look for salary credits, refunds, interest, dividends, cashback and reimbursements, once the bank says the money arrived.", "4. Read what the longbook already holds: accounts with their last four digits, members, commitments, and charges in that period. A mail whose amount and day are already recorded is skipped, and a mail for a commitment the longbook holds goes on it, never as a second copy.", "5. Copy the amount, the currency and the day the money moved exactly as the mail states them; never guess those. Name each one the way the user would say it, never by a payment handle or an order number. Use the last four digits of a card or account only to match, and never write a card or account number, an OTP or a tax ID.", "6. What each mail becomes:", " 1. Each credit is money in, kept apart from spending, at its real date and amount.", " 2. A notice that money is on its way is not money in. Wait for the credit.", " 3. Set a salary to repeat when the mails show it at least three times a steady month apart.", "7. Guess the category and which commitment a mail belongs to, write them, and show them in the table at the end. Set something to repeat only when the mails show it at least three times, a steady month, quarter or year apart, or a mail from the provider states how often it is billed; otherwise put your guess in the questions. Through a sign-in or a key, list those repeats in the table and set them after the user answers, once the rows are in the longbook. Ask before writing who a payment is for.", "8. In the end, when responding:", " 1. Send one table of what was added, grouped by category, with the names and categories you guessed and the repeats you set, and one line on what was skipped and why.", " 2. Ask, in one message, about anything you could not place, and how often each one seen once or twice comes round, with your guesses. Recommend the user answer by voice.", " 3. Say it is waiting in the Changes screen.", "9. After the user answers:", " 1. Apply the answers in one pass.", " 2. Set each further repeat the user confirms to continue, planned 24 months ahead unless they say otherwise. Through a sign-in or a key, set the repeats you listed too, once the rows are in the longbook; if they are not there yet, ask the user to open longbook first.", " 3. Say it is waiting in the Changes screen." ] } ] }