Walkthroughs

What you want. You are out on jobs all day and the useful things get said in trucks and on phones. You want one place that holds them, so Friday does not arrive with three things you half remember.

What you type. Sign in, press “Wake up”, and start telling it the day. One thing per message is easiest.

“Our vac truck is $245 an hour with a four hour minimum, and $310 for the combo unit. That's the 2026 rate.”

“The Safe Storage job needs a hot work permit before we cut anything. Their safety guy is Ruben and he wants 48 hours notice.”

“I told Kevin I'd get him the Safe Storage quote by Friday.”

“Malcolm at the recycling yard owes us the weight tickets from last Thursday.”

What happens. After each message the conversation shows what it did: “Kept that.” for the facts, “Noted the promise.” for the last two. Tomorrow's Wake up brings the Friday quote back with how long you have, and Malcolm's weight tickets as something owed to you.

What it asks you to approve. The rates and the permit rule are company facts, not personal ones. If you are in a team world, each one comes as a small card under the reply, because your crew would want them too. Nothing is shared by a card appearing.

Press ✅ on one and it names who would see it — “Add to United Environmental? Kevin and Javier will see it, and so will anyone in a moon of it that reads from it.” — and the yes is “Yes, add it”, directly under that sentence. “Not this one” keeps it to you, and it is not asked again.

Later the same day. Ask for any of it back in plain words. You do not have to use the words you used the first time.

“What do we charge for the combo unit?”

“What do I need before we cut at Safe Storage?”

And when something is done, say so and it closes the promise.

“Sent Kevin the Safe Storage quote.”

Close the day. Press “Goodnight” at the top. It looks back over the day, tells you where the open promises stand, and tidies anything it wrote twice.

What it remembers afterwards. The rates, the permit rule and Ruben's 48 hours, all privately. Malcolm's weight tickets, still open and still owed to you. Kevin's quote, closed. Tomorrow morning, Wake up leads with whatever is still open.

A person to call. If you ask about something one of your own people has already handled, and Nirvaana knows about it from something you told it, it should say so and suggest you call them. It only knows what it has been told. It cannot look up your contacts, your email or anything online.

What you want. You have a recording or a set of notes from a call, and you need something you could actually send or act on.

What you type. Paste the text and say what you want out of it. Say who it is for; that changes the answer more than anything else.

“Here's the notes from the call with Ruben at Safe Storage. Pull out what we agreed, what we still owe them, and anything with a date on it. Write it so I could send it to Kevin. [paste the notes]”

Keep it under about 8,000 characters per message. That is a few pages. If it is longer, send it in pieces and say so:

“That's part one of three. Wait for the rest before you answer.”

You have to paste the words in. There is no way to upload a file or a recording today.

What happens. It gives you back the clean version. Then push on it, the way you would with a person:

“Too long. Half that, and lead with the date.”

“Drop the pricing paragraph. Kevin already knows that part.”

What it asks you to approve. Nothing goes anywhere. It cannot send, post or share anything today. You copy the text out and send it yourself. If dates or commitments came out of the notes, those may turn up as cards under the reply, facts for a shared world, and they wait (at the top of the day, under “Waiting on your ✅”) until you say yes to the sentence naming who would see them.

What it remembers afterwards. What was in the notes, not the draft itself. So the dates, the agreements and the names carry into tomorrow. If you want a commitment tracked properly, say it as one:

“From that call: we owe Ruben the updated scope by the 30th.”

Three more are written and waiting on features that do not exist. We would rather leave them out than describe something that does not work:

• Directing a photo edit — needs the cloud computer.
• Drafting a post or campaign and approving it before it goes out — needs hands, and a yes it can act on.
• Being taught from your slides, and held to knowing it — needs uploads and the teaching behaviour.

They will appear here the day they work.