59 prompts, ready to paste

Loads the whole book at once, up to 50 per call, with each client extracted as an entity you can ask about later.

Save each of these to JustOnce as a separate memory — one per client — keeping my wording: who they are, my day-to-day contact, what we actually do for them, what they are sensitive about, and the billing arrangement.

[PASTE ONE LINE PER CLIENT]

Builds a brief for that account out of your own memories. The "say so" instruction is the bit that stops an assistant inventing an account history.

I have a call with [CLIENT] in ten minutes. Pull everything JustOnce has on them — the contact, what we have delivered, what was promised, what they are touchy about — and give me a one-page brief. If something is missing, say so rather than filling the gap.

Keeps the commitment verbatim alongside the distilled version, so the exact sentence survives — not somebody’s paraphrase of it.

Save this to JustOnce word for word: on today’s call with [CLIENT] I committed to [WHAT], by [DATE], and I said [SCOPE OR PRICE] was included. [WHO ELSE] was on the call.

Returns the original text stored on each memory — the thing you need when a customer says "we were told X would be included".

What have we committed to [CLIENT]? Give me the raw wording of each commitment and the date it was made, not a summary.

Turns a two-minute post-call dump into structured account memory. Nothing is captured automatically — this is you telling your assistant, once.

Save these to JustOnce as separate memories about [ACCOUNT], in my words: who was on the call, what they said their priority is now, the risk they raised, the number they quoted, and the thing they are unhappy about.

Reconstructs the account as it stood at a date, then diffs it — so prep starts from what changed instead of rebuilding the account from scratch.

Show me what JustOnce had on [ACCOUNT] as of [DATE OF THE LAST QBR], then everything saved about them since. I want the delta, not the whole story.

Extracts each person and company as an entity and records the relationships between them, which is what makes the next prompt possible.

Save these to JustOnce as separate memories: at [COMPANY], [NAME] is [ROLE] and is the one who signs. [NAME] is [ROLE] and is our champion. [NAME] blocked the last renewal because [REASON]. [NAME] came over from [PREVIOUS COMPANY].

Walks the entity graph outwards from a company, surfacing connections you never wrote down as a single fact.

Start from [COMPANY] and show me everyone and everything in my vault connected to them, two levels out — people, projects, other companies. Then tell me which of those people I have actually spoken to.

Creates the space, shares those memories in, and sends the invitation. Two honest caveats: the person must already have a justonce.ai account, and they read the space in the web app — memories another member shares in do not come back in your assistant’s search yet.

Create a shared space called "[TEAM] — decisions" and add every memory I have about decisions we have made and why, including the approaches we tried and rejected. Then invite [EMAIL].

Your real address is in Settings — "vault-" plus 16 characters, unique to you. It is the credential, so treat it like one. Forward a confirmation, an invoice or a whole thread to it and the body is stored word for word, then distilled into memories. Requires a paid plan and a connected Anthropic, OpenAI or Google key.

vault-[YOUR 16 CHARACTERS]@ingest.justonce.ai

Recalls everything those forwarded confirmations became, months after you forwarded them and forgot about them.

I fly to [CITY] on [DATE]. What have I got booked — flights, hotel, car, confirmation numbers — and what is still not sorted?

Searches the memories your forwarded invoices produced and lets the assistant do the arithmetic. The duplicate-spotting is your assistant reading the results, not a feature watching your invoices.

Find every supplier invoice in JustOnce connected to [JOB OR PROJECT] and give me a table: supplier, invoice number, amount, date, what it was for. Total it, and point out anything that looks like it was billed twice.

Reads back the memories the thread produced and writes one distilled decision alongside them. The original text stays exactly as it arrived.

I forwarded the "[SUBJECT]" email thread to JustOnce this morning. Read what came out of it, work out what was actually decided, and save that as one clear memory in plain language so I never have to re-read the thread.

Every attachment on a forwarded email is kept as a linked document — up to ten per email — so your assistant can pull the actual file back later.

Pull up the attachment that came in with the email I forwarded from [SENDER] about [SUBJECT], and read me [THE SECTION YOU WANT].

Supersedes the old value. Nothing is deleted — the previous answer stays in the history, with the dates it was true.

Update JustOnce: I am not at [OLD COMPANY] any more. I started at [NEW COMPANY] on [DATE] as [ROLE]. Correct the existing fact rather than adding a second one next to it.

Answers from the value that was valid on that date — what you need when you are reconstructing an old invoice, a tax year or a contract.

As of [DATE], what did JustOnce have on file for my [job / address / rate / stack]? I want what was true then, not what is true now.

Returns the whole chain of values for one fact, with dates. Nothing had to be overwritten to get there.

Show me the full history of what I have told you about my [rate / job title / address] — every version, when each one was true, and when it changed.

Records the new rate as a correction with a start date, so both numbers stay queryable instead of one replacing the other.

Save to JustOnce: from [DATE] my rate for [CLIENT OR WORK TYPE] is [AMOUNT], up from [OLD AMOUNT]. Keep the old rate in the history — I still invoice against it for work done before that date.

A soft, reversible invalidation. It stops coming back in recall, and you can bring it back if you were wrong.

I have cancelled the [SERVICE] subscription. Mark what JustOnce knows about it as no longer current, but do not delete it — I want the history.

Two questions in one: the state at a date, and the delta. Useful when the argument is about what was agreed before the change.

Reconstruct what we knew about [PROJECT] as of [DATE] — the scope, the budget, who was on it, what had been agreed — then tell me what has changed since.

One bulk write, and the household admin stops living in one person’s head.

Save each of these to JustOnce as its own memory: our electricity retailer, plan and account number; the gas one; the internet plan and when the contract ends; the council rates reference; the water account; and who the strata or body corporate manager is.

[PASTE YOUR DETAILS]

Everything you need to make the phone call, without the drawer, the shoebox, or the other person in the house.

[UTILITY] has billed us [AMOUNT] and it looks wrong. What does JustOnce have on that account — the plan, the rate, the account number, when the contract ends — and what should I be asking them?

The verdict is the part everybody forgets to write down, and the only part that matters in two years.

Save to JustOnce: our [TRADE] is [NAME] at [BUSINESS], [PHONE]. Used them on [DATE] for [JOB], charged [AMOUNT]. [WHAT I THOUGHT OF THEM]. I [WOULD / WOULD NOT] use them again.

The two-year-old recommendation you would otherwise be asking a group chat for.

Who did we use for [THE JOB] last time, what did they charge, and did I say I would use them again? Give me the number.

Registration, insurance and service history as facts, so the next booking starts from what the mechanic actually told you.

Save these to JustOnce: our car is a [YEAR MAKE MODEL], rego [PLATE] due [DATE], insured with [INSURER], policy [NUMBER]. Last serviced [DATE] at [KILOMETRES] by [MECHANIC], and they said [WHAT NEEDS DOING NEXT TIME].

Turns "something about the brakes, I think" back into the thing they actually said.

I am booking the car in. What did the mechanic say needed doing at the last service, what was the reading on the odometer, and when are the rego and the insurance due?

One space with the slice they need and nothing else. They read it in the JustOnce web app and need an account of their own; close the space when they are done and that access ends.

Create a shared space called "House sitting — [DATES]" and add what you know about the bins, how the alarm works, the vet and emergency contacts, the pet feeding routine, and which neighbour has the spare key. Then invite [EMAIL].

The five-second audit. If a category has grown in a way you did not expect, you can go and look at it.

List every category in my JustOnce vault with how many memories are in each, then show me the ten most recent things you saved about me.

Recall returns a confidence tier per memory — verified is 0.90 and up, high confidence 0.70 to 0.89 — so you can hold a form-filling assistant to the reliable ones.

Look up what JustOnce has for my [current employer / address / rate] and tell me the confidence tier on each one. I only want to act on the ones marked verified or high confidence.

A supervised clean-up pass. Corrections supersede and retirements are reversible, so nothing you do here is destructive.

Search JustOnce for everything about [PERSON, PROJECT OR COMPANY] and read them back to me one at a time. I will tell you which ones to correct and which to retire.

Walks the entity graph so you can see the inferences, not just the facts. Worth doing once, because this is the part of a memory layer people most expect to be a black box.

Start from [PERSON OR COMPANY] and show me everything in my vault connected to them two levels out — people, projects, organisations — and tell me how it made each connection.

Every memory keeps your exact wording alongside the distilled version. The tool name is self-reported by whichever client wrote it, so read it as a label rather than as proof.

Pull up the memory about [THING] and show me the raw version — my original words, not the summary — plus when it was saved and which tool saved it.