Dora is Kerdora's advisor-only AI workspace inside each client file. Advisors can use Dora to read and explain saved client data, prepare planning work, analyze attached files, create editable client Guides, import supported data, and draft proposed changes for approval.

Open Dora in the client navigation for a full-page workspace. From another advisor page, select Ask Dora to work beside the current screen. Dora conversations stay scoped to the client file that is open, and clients do not see Dora in the portal.

An advisor opens Dora from the main client navigation or from the Ask Dora button in an advisor workspace. The full-page Dora view includes a prompt box, suggested starting prompts, a New chat button, and the client's conversation list.

Clients cannot open Dora, read Dora threads, approve proposals, or see the advisor's prompts in the portal. A client sees only the separate portal areas and client-visible content the advisor chooses to share, such as visible Guides, assigned Changes, assigned Tasks, and applicable Profile or Documents data.

Each Dora thread belongs to one client. Dora cannot use one client's thread to compare or update another household. Confirm the client name before asking a question or approving a proposal.

Dora works best when the advisor names the task, source, time period, and expected output. Common requests include:

A specific prompt produces a safer result. “Summarize the 2026 Current Tax Scenario and list the inputs that most affect total tax” is better than “What should we do about taxes?” When the answer depends on a document, name the file and the applicable year.

Dora answers from the saved client file, the specific scenario or record selected in the request, any attached file it has been asked to examine, and permitted external research when the request requires it. A Dora answer is only as current as those sources.

For a year-sensitive question, include the year in the prompt and verify the year shown on the source record. Tax scenarios display their tax year. Documents and imported tax returns can also carry a document or tax year. If Dora uses the wrong year:

Dora can return text and visual cards based on the client's live data. Cards can summarize the household, meeting prep, next actions, cash flow, investments, Goals, Tasks, Changes, insurance, estate information, debt, and Taxes. Open the linked Kerdora page from a card when an action is available, then confirm the underlying record.

Dora may also cite external web sources when it researches a current fact. A source link supports the researched fact; it does not validate the client's saved data or turn a planning estimate into a quote.

Dora does not assign one universal confidence score to every chat answer. Confidence labels can appear in specialized extraction, matching, or import workflows, where they describe how strongly Kerdora matched an extracted value or record.

Treat confidence as a review cue, not proof. Compare the proposed owner, account, amount, date, category, or tax year with the source. Low confidence needs extra review, but high confidence can still be wrong when the source is incomplete or ambiguous.

When Dora wants to change supported client data, it normally creates a proposal instead of silently applying the events. The approval panel shows the records or differences Dora wants to create, update, or remove.

Before selecting Approve:

Select Reject when the proposal is wrong, incomplete, or unnecessary. Rejection leaves the proposed data changes unapplied. Tell Dora the specific correction and ask for a revised proposal.

A thread can pause while a proposal is pending. Approve or reject the pending proposal before expecting the conversation to continue normally. After approval, open the affected product page and verify the saved result.

Dora-created client Guides are the deliberate exception to the normal approval gate. A Guide is a separate editable deliverable, so Dora can create it directly without changing the underlying plan data.

After Dora builds a Guide, use Open Guide to review it. The Guide appears under the client's Guides and is owned by that client file, not by the practice template library. The advisor can add or remove components, rewrite text, change settings, adjust client visibility, or delete the Guide without altering the source plan or practice template.

Review every row, component, custom explanation, Change, Task, and visibility setting before delivery. Auto-created does not mean client-ready.

An advisor can attach a supported file when the request depends on a statement, policy, tax return, image, or transaction file. State whether Dora should analyze the file, extract proposed data, save it to Documents, or import supported records.

An attachment alone does not authorize client-data changes. If the advisor has not made the intended action clear, Dora can ask whether to extract the data into Kerdora or keep the file in the document vault.

For general client-document extraction, Upload & Extract can provide the clearest source-by-source review path. Use Dora when the file is part of a broader conversation, a supported tax-return workflow, or a transaction import.

Dora uses specialized proposals and background jobs for supported transaction and tax-return imports. For a transaction file, Dora identifies or asks for the source account, prepares an import proposal, and shows the transaction count, date range, inflows, outflows, and net totals when available.

After the advisor approves the import proposal, the background status can move through queued, classifying, importing, and complete, or stop at failed or needs attention. Verify the resulting transactions in Planning → Spending and review the date range, account, totals, categories, transfers, and possible overlaps.

For tax returns, verify the taxpayer, tax year, included forms, mapped entities, and resulting tax scenario before using it in Tax Plan. Keep transaction-import and tax-return proposals separate from unrelated data updates.

Each Dora conversation is a thread within the current client file. Use New chat when the purpose changes materially. Threads receive automatic titles based on the first request, and the advisor can rename, pin, archive, restore, or delete them from the conversation list.

Use a focused thread for a single planning question, document, import, or change set. This makes the source context and approval history easier to understand later. Dora can also remain in an attached, floating, or minimized workspace while the advisor opens a source page.

Dora cannot replace advisor judgment, source-document review, or qualified tax, legal, investment, and insurance professionals. It cannot guarantee that an answer is complete, use facts that are absent from its available sources, or silently change normal client data without approval.

Dora also cannot expose its advisor workspace to a client or move a thread across households. Long, multi-step requests may require several focused turns. A document must be explicitly examined before the advisor assumes Dora used it.

Dora does not automatically review every completed document extraction in the current verified workflow. Open the extraction result or start a Dora thread when an advisor wants a follow-up analysis.

Keep passwords, multifactor codes, and unnecessary full account numbers out of prompts and attachments.

When a Dora answer looks wrong, do not approve a related proposal.

If the same reproducible problem remains, contact Kerdora Support with the household, Dora thread, prompt, visible result, expected result, and approximate time. Do not send credentials or more client data than is necessary to investigate the issue.

Use Dora as a fast research and drafting partner, with the advisor as reviewer and decision-maker: