Nothing in the rail folds: every page is in the same place on every page.
The company picker
Almost every page is about one client’s books, and the sidebar’s picker scopes them all. All companies shows the whole firm. Every page has a real address, and the address carries the company:/knowledge?company=Ridgeline%20Properties%20LLC. Send a colleague the link
rather than a sequence of clicks.
Today
The page the console opens on: a short brief of what needs your decision and what has changed, written by your assistant, beside a work queue of what is waiting, due or overdue. Each subject gives a takeaway and the next step, with the evidence under Details. See Today.Inbox
Bills, receipts, and statements that have arrived by email or upload, waiting for somebody to say whose books they belong to and what they are. See the firm inbox.Bank feeds
Every staged bank and card line for the picked client, whatever door it came in by — a bank connection, an imported statement, a company card — with its payee, category and class, whether the ledger already holds it, and whether a claim is riding on it. A suggestion shows greyed in its own column, tagged suggested; it does not post until someone sets it. The tabs are the questions a bookkeeper asks: needs a category, suggested, ready to plan, claims to review, awaiting cardholder, linked. What a person does here: Exclude a line with a reason, or restore one; Link a line the scan matched to a ledger entry; Approve or Send back a submitted claim; Import statement. Nothing on the page sets a category or builds a plan — those come from rules, history, and the assistant. See the queue and expense claims. Cardholders get their own narrow page instead.Plans
The review queue, and the middle of the product. A plan lists every proposed entry with its date, counterparty, amount, account, class, source, and the verdict preflight reached — ready, worth checking, blocked, already posted. Work down it, decide lines, and record an approval or a rejection in your own words. Both are decisions and both leave a trace pinned to the exact plan that was read. One line under the plan’s stage says the next move. The same list holds every single change your AI has asked to make outside a plan (editing, voiding or deleting one document, emailing an invoice, a company setting) that nobody has decided yet. Each sits above the plans, marked awaiting approval, and opens its own approval page. The number beside Plans in the rail counts both. In Claude and ChatGPT the same page is drawn inside the conversation, under the message that made the plan. Strike a line and say why, approve or reject in your words, post: what you click there reaches your AI as your own message, so it carries on from your decision without you repeating it. The console page shows the same plan and the same record either way.
Runs
Every apply and every reversal, newest first: what posted, what was skipped and why, what failed with QuickBooks’ own message, and the QuickBooks id each entry became. Reversals appear in the list like any other run, linked to the run they undo.Work log
What was done and why, by company and period. Add entries directly — the log is a record for people, and a person can write in it as well as an agent can. The run journal records what was posted in enough detail to reverse it. It cannot say what was decided or what is still open. That is what this is for.Knowledge and rules
The two things the workspace has been taught, each readable and editable by the person whose judgement they encode. Knowledge is what a bookkeeper knows about a client’s books that no rule can express, anchored to the names it is about so it surfaces when those names come up. Entries land as drafts; confirming one is what makes it start surfacing. Each entry says whether it is used: not until confirmed, always, when its names come up, or never, when it has no names to match. Rules are mechanical: this descriptor means that account. Each shows what it matches, what it fills, whether it fills automatically or only suggests, how many times it has been used, and when it last applied.Clients
The firm’s client companies, their connection state, and how fresh each read model is. Add a QuickBooks company runs the Intuit consent flow. After the first sync, each client’s row links to its Check-up, what Zeno found in the books, and its Profile.Business profile
Once a client’s books are read, your assistant writes the client’s business profile: twelve short sections covering the business, entity and tax, the systems it uses, money in, money out, accounts, coding habits, class and location, the close, people, what’s off, and open questions. Zeno gives the assistant the figures; the assistant decides what they mean and writes each section in plain words, with the evidence it stands on and whether it came from the books, from you, or both. Each section is a draft until a person confirms it. Confirm a section, or all the drafts at once, on the client’s Profile page, or say so in the chat and approve the request your assistant sends. Clear takes a section off so your assistant writes it again. The console never edits a section. A confirmed profile is what your assistant reads before it works on that client. A section your assistant rewrites with different words becomes a draft again; one it rewrites unchanged stays confirmed. A view-only connection can read the profile but cannot write or confirm it. The same page lists the client’s Recurring templates, read live from QuickBooks Online, with the ones that post on their own first. Each shows its type, schedule, next date, amount, and whether Zeno made it (with links to the plan and the run) or someone made it in QuickBooks Online. The list is for reading: a change goes through your assistant as a plan. See Recurring templates. Disconnecting lives here too, beside connecting. Zeno stops syncing and can neither read nor write those books until somebody reconnects. The roster and mirrored books remain in place, as do the work log, plans, verdicts, and runs. Remove appears after a company is disconnected. It removes the company from the roster and deletes the mirrored books. Plans, verdicts, runs, and work log entries stay readable.Get started
The page a new workspace lands on, and the only one that leaves the sidebar when it is finished. Two steps: connect the AI you already use, then connect a QuickBooks Online company. The AI step ticks itself off when a client completes authorization. For ChatGPT, choose Add to ChatGPT to open Zeno’s approved listing. Install the plugin, connect your Zeno account and authorize it; developer mode is not required. The listing may still display Zeno while the Zeno Bookkeeper name update is in review. Other clients have their own install links or exact commands. See the ChatGPT walkthrough for the full sequence and advanced custom-server setup.AI clients
The same install links and commands, plus the MCP endpoint and the clients that have already authorized themselves, with the date each connected and a Disconnect beside each one. Disconnecting revokes that client’s access immediately and leaves everything it did on the record. See connecting an AI client and disconnecting a client.Billing
Your plan, what it includes, what you are using, and the card. Owners only.Refer someone
Your own signup link to copy, a box that has Zeno email it to someone, and everyone you have sent it to: invited, on a trial, or paid. Owners on Zeno for Business or Zeno for Firms only. When a workspace new to Zeno that you referred makes its first payment, your next charge is lowered by a month of what its plan costs, never more than that charge itself. On an annual plan it comes off your next yearly charge. Still on your trial? It runs a month longer instead. Referrals stack, and the person you refer gets the usual 3-day trial. Someone who already had a Zeno account, or is on your own team, earns nothing. See referrals on the pricing page.Setup pages
Under Clients and Firm rather than among the daily queues, because these are the pages you visit when something is being wired up rather than when work is waiting:- Connections — what feeds each client (bank logins, the documents address, Stripe and Square) and, for owners and operators, where each is set up: connect or reconnect a bank login or a processor, map an account to the QuickBooks account its money lands in, choose where payouts and their parts go. Your AI can map accounts and set up payouts from the chat too.
- Expense cards — mark a fed account as an expense card and record its cardholders.
- Notifications — choose firm emails, the local timezone and digest hour, and when a quiet scheduled agent counts as stopped. Each person controls their own opt-outs. See notifications.
- Team — who is in the firm and what each of them may do. See people and roles.