Skip to main content

Slant: Connect Your CRM, Import Households, and Sync Notes, Tasks, and Meetings

Written by Taylor Stewart

What syncs between Kerdora and Slant?

Slant in Advisor Settings → Integrations lets advisors read linked household information in Kerdora and choose which Kerdora notes and tasks go to Slant.

Kerdora reads from Slant:

  • Client, Prospect, and Past client households and their people, for reviewed import or updates: names, birthdays, contact details, household roles, and employment. A linked household's stage also follows Slant.

  • Household notes, meetings, summaries, advisor notepad content, and transcripts; Dora can also read open Slant tasks.

  • Title, due-date, and completion changes to tasks Kerdora sent (while task sending stays on), including whether someone deleted or reassigned one of those tasks in Slant. These depend on Slant's change notifications reaching Kerdora.

Kerdora sends to Slant when enabled:

  • Eligible General notes, each as a separate household note. Internal notes qualify; Client visible notes need “Include notes visible to the client”.

  • Eligible advisor-assigned Kerdora tasks, plus later title, due-date, and completion changes. Notes and tasks include a link back to Kerdora.

What doesn't sync as records:

  • Slant tags, custom fields, email messages, financial accounts, and policies don't become Kerdora planning data. Tasks created in Slant don't become Kerdora tasks.

  • Kerdora's plan, accounts, goals, Guides, What matters, Plan notes, and document notes aren't sent to Slant.

For details, see “Which Kerdora notes are sent to Slant?”, “Which Kerdora tasks are sent to Slant?”, and “Does Kerdora read Slant tags, custom fields, or emails?”.

What does the Slant integration actually do?

Slant in Advisor Settings lets every Kerdora advisor connect a Slant login, import Slant households (clients, prospects, and past clients), and link Slant households to existing Kerdora clients. Linked households give advisors access to Slant notes and meetings inside Kerdora, plus read-only Slant research through Dora.

You can also turn on sending for Kerdora notes and advisor-assigned tasks. Kerdora shows whether each send is pending, successful, or refused. Changes to tasks Kerdora sent can come back when Kerdora receives Slant's change notifications; this isn't a general two-way copy of both systems.

Start by connecting Slant, reviewing household matches, and importing a small group. For missing records or failed sends, see Slant Troubleshooting: Missing Households, Notes, Tasks, or Meetings.

How do I connect Slant?

Connect Slant from Advisor Settings → Integrations using your own Slant sign-in; you don't need a Slant API key.

  1. Open your account menu and choose Integrations. Kerdora opens Settings on its Integrations tab.

  2. Under CRM, select Slant's row or its Connect button. A Connect Slant pop-up lists what you get. What Kerdora reads and sends opens its details.

  3. Select Connect Slant. "Opening…" means Kerdora is sending your browser to Slant.

  4. Complete Slant's sign-in and return to Kerdora. Finish within 10 minutes; start again from Settings if sign-in expires.

During Practice setup, you can also connect from Connect your tools → CRM → Slant → Connect. It opens the same pop-up.

What Slant access does Kerdora use?

Slant in Advisor Settings connects separately for each advisor, using that advisor's Slant login. One advisor's connection doesn't connect an entire firm or give colleagues that advisor's household links.

Kerdora checks which Slant account signed in and shows that account's name, or email when a name isn't available, under “Slant” in Slant's drawer in Settings → Integrations. Kerdora requests household and book records using that login, so review which account appears before importing.

Kerdora saves your Slant sign-in and tries to renew expiring access, so you don't need to sign in for every read. If Slant stops accepting that access, reconnect in Advisor Settings → Integrations.

Kerdora uses the same Slant connection to read households and to send notes and tasks. Each sent note and task shows its own send status in Kerdora.

What happens right after I connect Slant?

After an advisor completes Slant sign-in, Kerdora returns to Settings → Integrations, or to Practice setup if you started there. The Connect Slant pop-up then says “Slant is connected” and asks “Send notes and tasks to Slant?”

Both send switches start off on a first connection.

  1. Leave sending off, or turn on Send general notes to Slant or Send tasks to Slant. Each change saves immediately.

  2. Select Import clients to open Import from Slant, or Not now to close the pop-up. Saved switch changes stay either way.

  3. On your first visit to Import from Slant, Kerdora starts reading Slant households on its own. Reading alone doesn't create Kerdora clients.

Afterward, Slant's row in Settings → Integrations shows a check. Select that row to open Slant's drawer, which holds Disconnect, Import clients, and both send switches.

What does Kerdora read when I import Slant households?

For advisors, “Import from Slant” reads Slant households whose type is Client, Prospect, or Past client, and the people Slant includes in those households. Kerdora also reads Slant books to suggest which households belong to your work.

People can bring names, preferred names, birthdays, Male/Female sex values, household roles, email addresses, phone numbers, and current employment. Current employment uses the most recently started job that has no end date and isn't marked inactive; a person's job title fills a missing role.

For an address, Kerdora uses a head of household's primary address, or that person's first address. If no head exists, Kerdora uses the first person returned by Slant for this address lookup.

Kerdora removes fields named as government IDs, such as SSN, tax ID, driver's license, and passport, before saving household import records. This is a field-name filter; it doesn't remove sensitive text someone typed into an unrelated field. Other returned household information can remain in Kerdora's stored import records.

What doesn't a Slant household import bring into Kerdora?

“Import from Slant” doesn't populate financial accounts, balances, holdings, insurance, trusts, businesses, or custom fields as Kerdora planning records. Households of other Slant types aren't read. Household members Slant marks as deceased aren't imported; Kerdora's Review your import page lists them as “Not imported (deceased)”.

Slant notes, tasks, and meetings aren't converted into Kerdora records by household import. Slant notes and meetings have separate advisor-only reading views after linking. Slant's own open tasks are available to Dora, rather than becoming rows in a Kerdora task list.

Add missing planning information through Kerdora's normal data-entry and intake workflows. See How Client Data and Connections Work in Kerdora for those other intake methods. Review imported household details before relying on a client's planning results; creating a household doesn't establish that client's complete financial picture.

How does Kerdora suggest household matches?

For an advisor on Import from Slant, Kerdora compares household names and people's names, birthdays, and adult-or-child types to suggest an existing Kerdora client. Each household's dropdown in the In Kerdora column starts filled in with Kerdora's suggestion for you to change.

  • A Slant client household with a suggested match starts linked to that Kerdora client. A household with the same name as one of your clients is suggested even when nothing else matches. The dropdown's Suggested section says why.

  • A Slant client household with no match starts at Create new client.

  • A Slant prospect or past client starts at Skip, unless it matches one of your clients well.

  • A household in a Slant book where you aren't principal starts at Skip. If Slant names none of your books, Kerdora treats every household as yours.

On Review your import, a weak match says “Check this match”. A message such as ‘You already have a client named "Whitfield Household".’ warns about a duplicate name; it doesn't catch differently named duplicates.

No suggestion creates or links a client until you import. Check people and birthdays, then pick a link instead of creating a duplicate.

How do I import or link Slant households?

Use Import from Slant to choose which Slant households become new Kerdora households or links to existing clients, then review and import them.

  1. Open Advisor Settings → Integrations, select Slant's row, and choose Import clients in its drawer.

  2. Check each household's dropdown in the In Kerdora column. Choose Create new client (or Create new prospect or Create new past client, matching its Slant stage), Skip, or one of your clients under Your clients. Use Search clients to find a client. A client under Already linked belongs to another household and can't be chosen.

  3. Select Review and import N in the page header. This opens Review your import, not an immediate import.

  4. Review its groups: Linked to existing clients, New clients, New prospects, and New past clients. To finish after import lists gaps such as a missing birthday or state.

  5. Select a linked household's row to check its people. Choose Same as Dana Whitfield, for example, or Add as a new person.

  6. Select Skip or Skip all to leave households out, or Back to return to your list. Select Import N households to confirm.

What do the Slant import filters and counts mean?

On Import from Slant, the controls above its household list only change which households you see. Review and import always takes every household set to come in, across every view, stage, and book, up to 1,000 at a time.

  • The book dropdown shows All books, My books (when only some are yours), or one book. It appears when you have more than one Slant book.

  • Clients, Prospects, and Past clients show one Slant stage at a time, each with a count.

  • All shows every household in that stage and book. Ready shows households set to be created or linked. Skipped shows households that won't come in. Imported shows households already created or linked.

  • Search households matches household and person names.

“Slant household” names each household, with a link to open it in Slant. “People” lists its members. “In Kerdora” shows your choice, or the client an imported household became.

Select rows' checkboxes to act on many at once: Create N new clients (or prospects, or past clients, in those views), Skip, or Back to suggested. Create and Skip leave a household linked to a client alone; change that link in its own row.

Can I import Slant prospects and past clients into Kerdora?

Yes. Import from Slant reads Slant households whose type is Client, Prospect, or Past client. Each comes into Kerdora at its Slant stage.

  1. On Import from Slant, select Prospects or Past clients above the list. Those buttons appear only when Slant has households at those stages.

  2. A prospect or past client starts at Skip unless it matches one of your clients well, so nothing comes in by accident. Open a household's dropdown in the In Kerdora column and choose Create new prospect or Create new past client, or link it to a Kerdora client.

  3. To bring in many at once, select their checkboxes and choose Create N new prospects or Create N new past clients. Pick a book first to take one book's prospects.

  4. Select Review and import N, check New prospects or New past clients, then select Import N households.

A new household lands in Kerdora's Clients page under Prospects or Past clients. Linking a Kerdora client to a Slant prospect changes that client's stage to Prospect. Wealthbox import reads clients only.

What does a new Kerdora client get from Slant?

A new household created through Import from Slant gets imported people, an address when available, its Slant stage (Client, Prospect, or Past client), and Kerdora's normal new-client defaults. Kerdora uses Slant's household name, falling back to member names if needed.

Your default new-client templates, change categories, Giving setting, spending categories, and default document folders are applied through Kerdora's new-client setup. Only the importing advisor is granted access by this import; importing doesn't invite clients to their portal.

Kerdora allows at most 2 people of type Client. Those Clients start with retirement age 65 and calculated life expectancy; imported Children don't automatically get education goals.

A head and spouse who both become Clients give a new household Married Filing Jointly status. A partner alone doesn't establish that status; other cases start as Single.

After import, open that household → Profile → Household and check State and Filing. These fields save when changed.

If no US state was imported, that household keeps Kerdora's Alabama default, even though Review your import said “No state”.

What changes when I link an existing Kerdora client?

When an advisor links a client from Import from Slant, Kerdora keeps matched people's existing Kerdora values, with a limited exception for empty email, phone, or employment details. Slant fills those details only when a matched Kerdora person has none.

Unmatched Slant people are added. Existing Kerdora people without a Slant match remain. Linking doesn't replace household address, state, or filing status. It does set that client's stage to match Slant, so linking a Kerdora client to a Slant prospect makes it a Prospect.

Before confirming a link, select that household's row on Review your import and check each pairing. A choice such as Same as Dana Whitfield joins a Slant person to an existing Kerdora member; Add as a new person creates a member. A label such as “Already in Kerdora (Client)” identifies a matched member.

One Kerdora client can link to only 1 Slant household through your Slant connection. There isn't an individual unlink control after import, so check a suggested link before confirming it.

Can I leave while Kerdora reads or imports Slant households?

Yes. Import from Slant keeps reading or importing after you leave its page.

“Getting your households from Slant” gathers import records. “Starting…” means queued work; “Connecting to Slant…” comes before a count such as “12 households found”. While it reads, the page says nothing changes in Slant and nothing comes into Kerdora until you import.

“Importing N households” applies your confirmed choices, with progress such as “8 of 12 imported”.

Return through Advisor Settings → Integrations → Slant → Import clients to check progress. Kerdora runs only 1 read or import at a time for your connection.

When an import finishes, the page says how many households were imported and lists any To finish in Kerdora gaps. Select Go to clients to open your client list, or Back to Import from Slant. If it says some households changed since your review or couldn't be linked, they're still in the list; review them again. If the import stopped partway through, choose Resume if Import from Slant shows it. If you left the page and see no Resume, don't start another import for those households; see Slant Troubleshooting: Missing Households, Notes, Tasks, or Meetings.

How do I get the latest Slant households into Kerdora's import list?

Use Get latest from Slant on Import from Slant to update Kerdora's import list. New Slant households aren't added to that list on a schedule.

  1. Open Advisor Settings → Integrations, select Slant's row, and choose Import clients.

  2. Select Get latest from Slant in the page header. The header shows when Kerdora last read Slant. Before a first successful read, the page offers Get households from Slant or Try again instead.

  3. Review new households and changed suggestions, then review and import any households you want.

Your choices survive a reread. “No longer in Slant” means Slant didn't return a previously read household; Kerdora doesn't delete an existing Kerdora client because of that badge.

Reading again doesn't apply changes to people already in a linked Kerdora client. For those updates, open that client → Profile → Household and use Check for changes.

How do I check a linked client for changes in Slant?

For advisors, “Check for changes” on a client's Profile → Household reads that client's linked Slant household and offers updates to Kerdora. It doesn't update Slant.

  1. Open a linked client → Profile → Household. In “Household Members”, look for “Linked to Slant”.

  2. Choose Check for changes. “Reading Slant…” means Kerdora is fetching that household.

  3. In “Changes from Slant”, review proposed Address, State, Name, Birthday, Sex, Emails, Phones, and Employment changes. The dialog compares current values with values saved at import or your last applied review.

  4. Kerdora preselects applicable changes made only in Slant and each person it can add under “New in Slant”. Clear any checkbox for a change or person you don’t want, then confirm using a counted button such as Update 2 fields · add 1 person. “Updating…” means Kerdora is saving your choices.

“Updated from Slant” confirms an applied update. “Cancel” closes without applying your selections; “Close” dismisses a check with nothing to apply.

“Nothing changed since you last checked.” or “Nothing changed since the import.” means no differences were found in compared fields.

Does a linked Kerdora household's stage follow Slant?

Yes. Stage is the one field Slant changes in Kerdora without a review. When a linked household's type changes in Slant, for example from Prospect to Client, Kerdora sets that household's stage to match.

Kerdora applies the change soon after Slant reports it. Check for changes on Profile → Household also catches a change Kerdora missed.

You can still change a linked household's stage in Kerdora, from Clients or from Stage under Household Details on Profile → Household. Kerdora keeps your choice until that household's type changes in Slant again; then Slant's stage wins.

Linking a Kerdora client during import also sets its stage to the CRM's: Slant's stage, or Client for Wealthbox. After import, Wealthbox doesn't change Kerdora stages.

How do I choose between conflicting household changes?

When an advisor reviews “Changes from Slant” on Profile → Household, Kerdora preselects changes made only in Slant and keeps Kerdora's value selected when both systems changed a field differently. Review each choice before saving.

“Updated in Slant” lists changes offered from Slant. Use all from Slant selects that group's fields.

Under “Changed in both”, choose between competing values with “Edited in Kerdora” and “From Slant”; “Was” shows a previous value. Emails and phones can combine separate, nonconflicting entry changes.

“New in Slant” lists people with labels such as “Add Alex as a child”. Each person Kerdora can add starts selected. Clear anyone you don’t want added; confirming records unselected people as declined, so later checks won’t offer them again.

“No action needed (N)” expands differences Kerdora won’t apply, including removed people and required fields Slant cleared.

If you clear every change and person, confirm with Keep Kerdora's, stop asking. It saves your review without taking Slant values; “Kept Kerdora's values” confirms it. Unlike Cancel, it marks those values as reviewed, so Kerdora won’t offer them again until Slant changes them.

Does Kerdora change Slant household details or delete missing people?

An advisor's Slant household import and Profile → Household change review only change Kerdora. Editing a person's name, phone, job, or household address in Kerdora doesn't send that edit to Slant.

If Slant removes a person, “Changes from Slant” names that person in a message such as “Dana Whitfield is no longer in Slant. They stay in Kerdora.”

If Slant no longer returns a linked household, for example because it was deleted or its type isn't Client, Prospect, or Past client, Kerdora says, “Slant no longer lists this household as an active client. Nothing in Kerdora was changed.”

Kerdora also keeps a required State or Sex value when Slant clears it, explaining that Kerdora needs a value. Review those records manually before removing or changing anything in a financial plan.

Keep Slant contact information current in Slant, then use Check for changes on each linked Kerdora client when you want to review those changes.

Can I unlink just one Slant household?

No. “Import from Slant” has no control to unlink or replace an already imported household's link. An imported row opens its Kerdora client instead of offering Create, Skip, or Link choices.

If you linked the wrong household, turn off the note and task switches in Slant's drawer in Advisor Settings → Integrations, then contact Kerdora Support before making a broad reset. Turning off sending doesn't undo data already imported or copies already sent.

The only reset is “Also delete the households and people read from Slant” when you disconnect, and it removes every household link for your connection. See “What does 'Also delete the households and people read from Slant' remove?” for that reset’s scope and recovery steps.

Which Kerdora notes are sent to Slant?

Only General notes can be sent to Slant: the notes listed as General on a client's Office → Notes page. You make them with Notes in the client's header, with New note on Office → Notes, with Add note on a Slant meeting page, or by approving a Dora note proposal. An older “General note” carried over from Kerdora's earlier single notes field is listed as General but isn't sent.

Each eligible Kerdora note becomes its own Slant household note, rather than one combined note.

Notes on accounts, goals, and other records (Plan notes), notes on documents, and What matters are never sent by note syncing.

“Send general notes to Slant” in Slant's drawer controls sending for all households linked through your Slant connection. It starts off and doesn't send an older note for the first time just because you edit that note.

  1. Open Advisor Settings → Integrations and select Slant's row to open its drawer.

  2. Turn on Send general notes to Slant. Kerdora saves immediately and starts eligibility from that time.

  3. A General note is Internal or Client visible. Include notes visible to the client starts off; select it to send eligible Client visible General notes too, or leave it off to send Internal General notes only.

Kerdora waits 90 seconds after a note's last edit before attempting a send. A note must also belong to a linked client and remain eligible. If Slant refuses a write, Kerdora shows “Couldn't send to Slant” rather than a successful send.

What happens when I change Slant note sending?

In Advisor Settings → Integrations, Slant note-sending changes affect future sends and updates; existing Slant copies stay.

Making a sent note client-visible while client-visible sending is off stops further updates to that note; its Slant copy stays. Clearing Include notes visible to the client has the same effect on Client visible notes already sent. Such a note can still show “In Slant” even though Kerdora no longer updates it, so check its copy in Slant.

Turning a send switch off leaves existing Slant copies. Turning Send general notes to Slant back on sends edits you made while it was off to notes already in Slant, replacing their Slant text.

For notes never sent, turning the switch back on starts a new cutoff. There isn't a send-history button for older notes.

Are colleagues' notes and tasks sent through my Slant connection?

Yes, when they qualify. Sending follows the households linked through your Slant connection, regardless of who wrote a note or created a task.

A colleague's eligible General note on a client you linked can go to Slant through your connection. An advisor-assigned task created by a colleague can go too, and Kerdora assigns that copy to your connected Slant login.

If 2 advisors link the same client and both turn on sending, each connection can send its own copy. Agree with colleagues on sending before more than 1 advisor links a shared client.

Which Kerdora tasks are sent to Slant?

“Send tasks to Slant” in Slant's drawer in Advisor Settings → Integrations attempts to send new advisor-assigned Kerdora tasks on households linked through your connection. Tasks assigned to household members aren't sent for the first time.

  1. Open Advisor Settings → Integrations and select Slant's row to open its drawer.

  2. Turn on Send tasks to Slant. This saves immediately.

  3. For eligible older open tasks, review “N open tasks from before you turned this on are only in Kerdora.” Choose Send them, or Send it for 1 task, if you want that group sent too.

Kerdora queues tasks without a note's 90-second wait. “Sending N tasks to Slant…” confirms queuing, not acceptance by Slant. Completed older tasks aren't included in that offer.

For a task already sent, Kerdora sends later title, due-date, and completion changes. Reassigning that Kerdora task to a household member doesn't stop those updates or reassign its Slant copy away from your connected Slant login.

Title, due-date, and completion changes made in Slant can also come back for tasks Kerdora sent, while task sending remains on and Slant's change notifications reach Kerdora. Tasks created in Slant don't become Kerdora tasks. If someone deletes a sent task in Slant, its drawer shows “Deleted in Slant” and Kerdora stops sending its changes; choose Send again to make a new copy. See “Which Slant task changes can come back to Kerdora?”.

What does Kerdora send in a Slant note?

For an eligible note in an advisor's Kerdora note editor on a linked client, Kerdora sends a household note to Slant containing a title marked for bold text, readable note text, and an “Open in Kerdora” link. Slant's handling of that request determines whether a copy is created.

Kerdora converts rich text in a note body to plain text. Paragraph breaks, line breaks, and bullet text remain; bold, italics, and embedded link destinations don't carry over as rich formatting. Put a needed web address into visible note text if that address must travel with the note.

In Kerdora's note editor, “In Slant” means Kerdora recorded a successful send. Its tooltip says, “In the household's notes in Slant. Edits here update it there.”

The In Slant link uses a household destination, not a direct note destination. If that link doesn't reach your household, find the household directly in Slant.

What does Kerdora send in a Slant task?

For an eligible Kerdora task in an advisor's task drawer, Kerdora sends Slant a task on its linked household and book, assigned to your connected Slant login. The request uses an all-day deadline, the Kerdora task text as a title, and a description beginning “From Kerdora:” followed by a Kerdora link.

An empty title falls back to “Task from Kerdora”. Kerdora sends completed tasks as done and other tasks as to-do. These describe what Kerdora requests; check for “In Slant” to confirm a successful send.

The task drawer's “CRM” field shows sending status. A Slant logo also marks followed tasks in Kerdora task rows; don't use that logo alone as proof that a send finished. Open the task drawer to inspect “Sending to Slant…”, “In Slant”, or a failure.

The tooltip on “In Slant” in a task drawer’s “CRM” field says, “On the household in Slant, assigned to you.” That means your connected Slant login, not a household member.

Why does an undated task get a Slant due date?

For advisors sending tasks from Kerdora to Slant, a task without a due date uses its creation day as a fallback. That day is calculated in US Eastern time, so an undated task can appear overdue in Slant even though you didn't enter a deadline in Kerdora.

For an explicit Kerdora due date, Kerdora sends that day as an all-day task. Timed deadlines returned from Slant are interpreted in US Eastern time; returned all-day deadlines use separate date handling. These task rules differ from meeting times displayed in your browser's time zone.

Set an explicit due date in a Kerdora task before sending when timing matters. If a date comes back differently, compare that task in both apps and report the dates and your time zone to Kerdora Support. Don't assume a timed Slant deadline will preserve its hour in Kerdora.

Which Slant task changes can come back to Kerdora?

In an advisor's Kerdora task drawer, completion, reopening, title, and due-date changes can return from Slant for a task Kerdora previously sent. This requires “Send tasks to Slant” to remain on and Slant's change notifications to reach Kerdora.

A received change can appear in a Kerdora task drawer with a message such as “Completed in Slant · 2 minutes ago”, “Reopened in Slant · 5 minutes ago”, or “Edited in Slant · 10 minutes ago”. If both apps changed a field and Kerdora receives a qualifying Slant update, Kerdora takes Slant's changed value for that field.

A message such as “Assigned to Jordan Lee in Slant” reports a different Slant assignee without changing the Kerdora task's assignee. New tasks created in Slant don't enter Kerdora's task list through this process.

The tooltip on a task row’s Slant logo says, “In Slant. Changes here go there, and changes made there come back.”

Confirm the actual task value in Kerdora before relying on a return update. If it hasn't arrived, update the Kerdora task directly and contact Support.

Can I edit a sent Kerdora note in Slant?

Advisors should edit a sent note in Kerdora's note editor to preserve their work through later Kerdora updates. A later Kerdora edit sends that note’s whole content again and replaces its Slant copy, including changes someone made directly in Slant.

Slant edits to a sent note don't come back into the original Kerdora note. Kerdora sends note content as a single field, so a later Kerdora edit doesn't protect a paragraph someone changed in Slant.

If someone already added useful text in Slant, copy that text into your Kerdora note before editing and resending. Alternatively, use Stop sending in the Kerdora note editor and maintain its Slant copy separately. Stopping sends leaves existing Slant text in place; resuming can send Kerdora's current content again.

Does deleting a Kerdora task delete its Slant copy?

No. When an advisor deletes a sent task in Kerdora, that deletion leaves its Slant copy as it was, whether open or complete. Kerdora doesn't send a Slant task-delete request.

If work is complete and you want both apps to show completion, complete the Kerdora task while Slant sending is active, then check that this task’s drawer shows “In Slant” in its “CRM” field before deleting anything. Completion is a supported outgoing task change.

If you already deleted a Kerdora task, open Slant directly and complete or delete its remaining copy there. Don't expect a later reread or reconnect to remove that Slant task. A task disappearing from Kerdora doesn't mean someone finished the work in Slant.

Does deleting a Kerdora note delete its Slant copy?

No. When an advisor deletes a note in Kerdora, that deletion leaves any note copy already sent to Slant. Neither deleting a Kerdora note nor turning off Slant note sending removes that existing Slant copy.

If a note should also be removed from Slant, find and remove the Slant copy directly after reviewing your firm's recordkeeping needs. Don't use disconnecting as a way to delete notes in Slant; disconnecting stops Kerdora access and sends but leaves Slant records.

If your aim is to stop updates while keeping both notes, open the Kerdora note editor and choose Stop sending instead. “Not updated in Slant” identifies that stopped state, and Resume can later send Kerdora's current note content again.

How do I stop or resume sending one note to Slant?

Use a Kerdora note editor's Slant status actions to stop or resume that note, without turning off sending for every linked household. “Sends to Slant” means an eligible note hasn't been attempted yet; “Sending to Slant…” means sending is pending.

  1. While a note says “Sends to Slant” or “Sending to Slant…”, choose Don't send to request exclusion. Act before sending completes if you want to prevent a copy.

  2. After a successful send, choose Stop sending beside “In Slant” to stop later updates. An existing Slant copy stays.

  3. “Won't go to Slant” offers Send to undo a before-send exclusion. “Not updated in Slant” offers Resume to undo stopped updates.

The tooltip on “Won’t go to Slant” or “Not updated in Slant” says, “You chose not to send this to Slant. Anything already there stays as it was.” Resuming uses current Kerdora content, subject to connection and note eligibility.

Tasks don't offer Don't send or Stop sending on their normal send notice. Use Send tasks to Slant in Slant's drawer in Advisor Settings → Integrations for connection-wide control.

Where can I read Slant notes in Kerdora?

Advisors can read a linked household's Slant notes in that client's Office → Notes. Slant rows are internal, read-only records; they aren't editable Kerdora notes.

  1. Open that linked client → Office → Notes. Slant rows appear with your Kerdora notes in “All”.

  2. To show only Slant rows, choose the filter button whose tooltip says Filter notes. Under “Note type”, choose Slant.

  3. Open a row to read it. “Written” and, when different, “edited” introduce that note’s Slant timestamps.

“You” identifies a note by your connected Slant login; notes by other Slant users can have no author name shown. “Open household in Slant” provides Kerdora's configured household link; if it doesn't work, find that household directly in Slant.

Kerdora reads only the first 50 notes Slant returns and can reuse a read for 15 minutes. That isn't a guarantee of your latest 50 notes. Hidden, empty, and Kerdora-sent notes are excluded from these Slant rows; Kerdora-sent notes remain their original Kerdora notes.

Why aren't Slant's own tasks in my Kerdora task list?

Kerdora's task list doesn't import tasks created in Slant. Kerdora’s Slant connection sends eligible Kerdora tasks outward and can apply reported changes to those sent tasks; it doesn't create a general Slant task list in Kerdora.

For a linked client's outstanding Slant work, ask Dora in your advisor conversation to read that household's open Slant tasks. Dora reads up to the first 50 open tasks Slant returns, excluding tasks Kerdora already sent, and can reuse a read for 15 minutes.

Use Slant directly when you need its complete task list or current assignment details.

Where do Slant meetings show in Kerdora?

Advisors see meetings for Slant households they've linked on practice Home and inside each linked client's Office. Kerdora reads meetings starting within the last 24 months or next 90 days, up to 6,000 meetings per Slant book for a read window. Use Slant directly for meetings outside that window or beyond that limit.

  • Practice Home → Today: on a day with something scheduled, this card shows the next client meeting today, a timeline of today's meetings, and a line about tomorrow's meetings.

  • Client → Office → Home → Meetings: “Next” shows that household's next or ongoing meeting; “Last” shows its previous meeting with a few lines of Slant's summary. Select either one to open its meeting page. Select the Meetings card title to open that client's meeting list.

  • Client → Office → Meetings: “Household meetings” groups rows into “Upcoming” and “Past”. “Meeting”, “When”, and “Advisors” identify title, timing, and Slant advisors. Open a meeting row for detail.

The Slant meeting page is the only page that shows a meeting's full summary, notepad, and transcript, along with your own Kerdora notes for that meeting.

“Open household in Slant” uses a household link. If it doesn't reach the expected destination, locate your household directly in Slant.

What does practice Home's Today card show for Slant meetings?

On practice Home, the Today card shows linked Slant households' meetings for today. Its count says how many client meetings you have today.

  • The top row names today's next meeting: “Next · 2:00 PM”, “Next · in 45 min” within the hour, or “Now” while it's underway. It shows that meeting's household, title, and a call type such as “Zoom”, “Google Meet”, “Teams”, or “Video call” from Slant's stored link.

  • Open client opens that household's Office Home. Join appears when that meeting has a call link and starts within 15 minutes or is underway.

  • The timeline places each of today's meetings. Select one to see its details, then select Open meeting, or Review for a meeting that's over, to open its Slant meeting page.

  • A line at the bottom says, for example, “Tomorrow: 2 client meetings, first at 9:00 AM”, or names your next client meeting after today.

If Slant provides no end time, Kerdora treats that meeting as lasting 1 hour for these labels and for Join. Times use your browser's local time.

What's on a Slant meeting page?

A meeting opened from a client's Office → Meetings shows Slant's title, meeting type, date, time, duration when available, read-only meeting content, and a Notes panel for your own Kerdora notes. “Untitled meeting” means no title was supplied; “No date” means no start time is available.

Meeting types such as “Client review”, “Client check-in”, “Prospect”, “Internal”, “COI”, and “Other” are labels from Slant; they don't change a Kerdora client's classification.

“Attendees” lists participants once meeting detail is available; “Advisors” can appear while Kerdora has only listed advisor names. In “Advisors”, “You” is your connected Slant login; “Attendees” uses participant names supplied by Slant.

“Summary” can contain a quick summary, an AI summary, and “Advisor's notepad”, all read from Slant. “Transcript” shows speaker names, timestamps, and text when available.

Use Search in Transcript to filter that meeting's transcript. “1 match” or “N matches” counts matching displayed turns; a message such as ‘Nothing matches “Roth”.’ means that search has no match. Clear Search to return to all available text.

Use All meetings to return to that client’s Office → Meetings list.

How do I add a Kerdora note from a Slant meeting page?

Use Add note in the Notes panel on a Slant meeting page, from a client's Office → Meetings. It makes a Kerdora General note tied to that meeting, so advisors can keep prep or follow-up beside Slant's summary, before or after that meeting.

  1. Open a linked client → Office → Meetings and open a meeting row.

  2. In that page's Notes panel, choose Add note. Kerdora's Notes window opens with a line such as “For the meeting: Annual review · Tue, Mar 31”. If that window already holds an unsaved new note, Add note reopens that draft without this meeting, and it won't show on this meeting page. Save that draft, or close the Notes window to discard it, then choose Add note again.

  3. Type a title in the Note title field, note text, or both. A new note starts internal; use its eye control only if that text is ready for your client.

  4. Choose Add note in that window to save.

A saved note shows in that meeting's Notes panel and in Office → Notes. “Shared with client” marks a client-visible note. Choose a note's title to reopen it.

Do notes from a Slant meeting page go to Slant?

Yes, when sending is on. A note written with Add note on a Slant meeting page follows the same rules as other General notes, even though, before a meeting happens, the empty Notes panel says these notes “stay in Kerdora”.

With Send general notes to Slant on, an eligible note goes to Slant as a household note, not onto that Slant meeting. That Slant copy doesn't name the meeting, so put the meeting in your title if you want it there. To keep one out of Slant, choose Don't send on that note before it goes.

When can I join a Slant meeting from Kerdora?

For advisors, practice Home's Today card and a client's Office → Home show Join when a linked Slant meeting has a call link and starts within 15 minutes or is already underway. Join disappears after Kerdora considers that meeting ended.

  1. Find that meeting at the top of practice Home's Today card, or under Meetings on that household's Office Home.

  2. Choose Join to open Slant's stored call link in a new tab.

  3. Earlier than 15 minutes before a meeting, open that client → Office → Meetings. An upcoming row can show a camera icon titled “Join the call”; that meeting’s detail page offers Join call when an upcoming meeting has a link.

Kerdora doesn't create a call link. If no join action appears, inspect the meeting directly in Slant. Reopen a Kerdora meeting view if its time-dependent controls haven't changed as a meeting approaches.

How quickly do Slant meetings refresh?

For advisors, Kerdora's Office → Meetings reads Slant again when a stored book's recent copy is at least 15 minutes old, unless Kerdora is receiving Slant notifications that replace those frequent reads. Opening a page doesn't guarantee a new Slant request every time.

A first read, or a household linked after a previous full read, can trigger a full meeting read. Background recent reads are scheduled hourly from 7:07 a.m. through 7:07 p.m. US Eastern, Monday through Friday, for books opened in the last 7 days. Full nightly reads start at 2:13 a.m. US Eastern and are spread over 4 hours.

Active Slant notifications can replace the page-triggered and hourly recent reads; nightly reads remain. Don't assume an immediate update.

If a Retry action is available, a full reread can still be limited to once per 5 minutes. Check Slant directly for urgent meeting changes.

Can I edit Slant meeting notes or transcripts in Kerdora?

No. Slant's summary, notepad, and transcript on a meeting page in a client's Office are read-only. Kerdora doesn't send edits to Slant's meeting summary, “Advisor's notepad”, or transcript back to Slant.

Write or correct meeting content in Slant. A separate Kerdora General note is different, including one written with Add note on that meeting page: if note sending is enabled and that note is eligible, Kerdora attempts to send it as a household note, not as a meeting summary or meeting notepad update.

Kerdora copies a transcript once and doesn't refresh that stored transcript after later Slant edits. Even an initially empty transcript copy can remain empty. Use Slant directly for corrected or complete transcript text.

Can Slant's AI see my Kerdora data?

Through this integration, Slant can read only the Kerdora notes and tasks that Kerdora sends to Slant. Those copies include a link back to Kerdora, labeled “Open in Kerdora” on notes. The link doesn't give Slant access to a client's plan, accounts, goals, or Guides.

Slant therefore can't inspect a Kerdora plan to find manual accounts that need new statements or read goals and progress from a Guide. Information you write into a sent note or task is part of that copy.

To draft an email using a client's plan data, ask Dora in an advisor conversation for that client in Kerdora. Dora can read the client's plan and, when linked through your Slant connection, that household's Slant notes, meetings, and transcripts. Review the draft before using it.

See “What can Dora read from Slant?” for read limits.

Does Kerdora read Slant tags, custom fields, or emails?

Kerdora doesn't look up Slant tags, custom fields, or email messages for advisors to use in a client's plan or through Dora. Contact email addresses can come with household imports; email messages and conversations don't.

Kerdora reads Client, Prospect, and Past client households and their people, including names, preferred names, birthdays, sex, household roles, email addresses, phone numbers, current employment, and an address. It also reads Slant books to suggest households during import.

For linked households, Kerdora reads household notes, open tasks for Dora, meetings, summaries, advisor notepad content, and transcripts. For tasks Kerdora sent, title, due-date, and completion changes can return while task sending is on and Slant's change notifications reach Kerdora.

See “What does Kerdora read when I import Slant households?” and “What can Dora read from Slant?” for details and limits.

Extra information bundled into Slant household responses can remain in saved import records, but Kerdora doesn't map tags or custom fields into planning fields or offer a separate Dora lookup for them. Slant's change notifications can include tag changes; Kerdora keeps those notifications for up to 30 days and doesn't use them. Meeting details include attendee email addresses. Check Slant directly for tags, custom fields, and email messages.

What can Dora read from Slant?

In an advisor conversation for a linked client, Dora can read that household's Slant notes, open tasks, meetings, summaries, notepad content, and transcripts. Dora can also search stored transcripts for the household.

For example, ask what was discussed about retirement at previous meetings, or which Slant tasks remain open. Dora's Slant access is read-only and uses your connection. Clients don't have Dora, so they can't reach Slant records this way.

Dora's coverage has limits: Slant notes and open tasks come from the first 50 records returned for each request, with reads reused for up to 15 minutes. Kerdora-sent items are excluded from those Slant lookups because their originals are already in Kerdora.

Meeting reads cover linked households within Kerdora's meeting window. A single Dora script can fetch at most 10 uncopied meetings or transcripts, and a transcript search returns at most 40 matching segments. Ask a narrower question or check Slant directly when you need complete records.

Can Dora add notes or tasks in Slant?

No. Dora's Slant tools in an advisor conversation only read records. Dora can't create, edit, delete, or reassign a Slant note, task, or meeting.

What Dora can do with Slant for a linked client:

  • Read that household's Slant notes, open tasks, meetings, summaries, and transcripts, and answer questions about them.

  • Write a meeting follow-up for you in your conversation, using a meeting's summary and that client's plan. Copy it into your own email to send it.

  • Propose Kerdora tasks from what was discussed. Nothing changes until you approve.

An approved Kerdora task goes to Slant only through normal sending: Send tasks to Slant must be on in Slant's drawer, that task's client must be linked through your connection, and that task must be assigned to an advisor. A task assigned to a household member stays in Kerdora.

A proposed task isn't tied to an existing Slant task. If you ask Dora to mirror a task already in Slant, sending that approved Kerdora task creates another copy in Slant.

Can my client see Slant data?

Slant views in Kerdora are advisor-only, but imported household details become ordinary Kerdora client information. Clients can’t use Slant connections, household links, read-only Slant notes, meetings, transcripts, or CRM send controls, and can’t connect Slant themselves.

Clients don't have Dora. An advisor can ask Dora about Slant records in an advisor conversation for a linked client, and that doesn't give the client those records.

“Include notes visible to the client” controls an outgoing copy of a Kerdora note that is already client-visible. It doesn't expose Slant notes to clients.

Review imported household details and Kerdora’s usual sharing choices before client delivery. Text an advisor copies from Slant into a client-visible Kerdora note is visible like any other client-visible note. Importing a Slant household doesn't automatically invite that client to their portal or share Slant's meeting material.

What does "Needs reconnecting" mean for Slant?

“Needs reconnecting” on Slant's row in Advisor Settings → Integrations means Kerdora's saved access isn't working. Slant can reject that access during a read or send, or Kerdora can be unable to renew expired sign-in access.

Your account menu and Settings' Integrations tab also say “A tool needs reconnecting”. Slant's drawer says, “Slant stopped accepting Kerdora's access. Reconnect to keep it working.”

While reconnection is required, Slant's drawer doesn't show Import clients or the send switches. Outgoing notes and tasks wait, and meeting pages can show previously stored records.

Choose Reconnect on Slant's row or in its drawer, and sign in with the same Slant login. See Slant Troubleshooting: Missing Households, Notes, Tasks, or Meetings for full reconnection steps and sign-in failures.

How do I disconnect Slant?

Disconnect Slant in Advisor Settings → Integrations to stop Kerdora's access and sends through your connection. Existing Kerdora clients and records already sent to Slant stay.

  1. Select Slant's row to open its drawer.

  2. Choose Disconnect at the top of that drawer. A “Disconnect Slant?” dialog opens.

  3. Read its two lines. Stops: “Notes and tasks stop going to Slant, and Slant meetings leave Kerdora.” Stays: “Clients already in Kerdora.”

  4. Decide on “Also delete the households and people read from Slant. Clients already imported into Kerdora stay.” Leave it unselected to keep imported household records and links.

  5. Choose Disconnect to confirm. “Slant disconnected” confirms completion.

Kerdora removes stored Slant meetings and their transcripts, clears stored sign-in credentials, and attempts to end Slant notifications and revoke access.

Without optional deletion, household links and send-switch choices remain. “Linked to Slant” and a Meetings tab can therefore remain after disconnecting, even though Slant reads and sends have stopped. Existing Slant notes and tasks aren't deleted.

What does "Also delete the households and people read from Slant" remove?

When an advisor selects “Also delete the households and people read from Slant. Clients already imported into Kerdora stay.” in “Disconnect Slant?”, Kerdora removes imported source records and every household link for your Slant connection.

Kerdora also removes import-run records and stored Slant meetings and transcripts. Kerdora clients already created or linked remain, including household information previously applied to those clients. The checkbox doesn't undo those planning changes or delete records from Slant.

With no household links, Kerdora can't send notes or tasks to those Slant households or show their meeting data. To restore links, reconnect, read Slant again, and choose existing Kerdora clients during import. Carefully review person matches to avoid duplicate members.

This is a connection-wide reset. For a mistaken individual link, contact Kerdora Support first. Wait for any running import to finish before attempting optional deletion.

What happens if I reconnect Slant later?

Reconnecting Slant from Advisor Settings with the same Slant login preserves your send-switch settings and queues a check for eligible work missed while disconnected or awaiting reconnection. That can include notes and tasks created during the gap if retained switches and household links make them eligible.

Don't treat disconnecting as a permanent exclusion for notes written afterward. If you want to stop future first-time sends, turn off Send general notes to Slant or Send tasks to Slant before disconnecting. Turning a switch on again establishes a new cutoff for items never sent.

A different Slant login turns both send switches off. Existing household links aren't cleared automatically; review your connected account and links before enabling sending again.

Reconnect on Slant's row returns you to Settings with “Slant connected”. Connecting again through Slant's Connect pop-up after a disconnect asks “Send notes and tasks to Slant?” again, with Not now and Import clients.

If you previously deleted imported source records and links, reconnecting alone doesn't restore those links; import and link households again.

What's different between Slant and Wealthbox in Kerdora?

In Advisor Settings → Integrations, Slant uses a sign-in flow, while Wealthbox accepts a pasted personal API token. The differences also affect what Kerdora reads and sends.

Slant supplies meetings to practice Home, Office, and Dora. Wealthbox doesn't supply meetings through Kerdora. Slant can report changes to tasks Kerdora sent when notifications reach Kerdora; Wealthbox doesn't bring those task changes back.

Deleting a sent Kerdora task leaves its Slant copy. For Wealthbox, Kerdora can delete an open sent copy; a copy already completed in Wealthbox is retained.

Kerdora sends plain-text note bodies to Slant. For Wealthbox, it sends HTML content and requests visibility to everyone in your Wealthbox workspace. Wealthbox import can bring trusts; Slant import doesn't. Slant import reads clients, prospects, and past clients, and a linked household's stage follows Slant; Wealthbox import reads clients only.

Slant disconnect attempts to revoke its sign-in grant. A pasted Wealthbox token must be revoked in Wealthbox if you want that token invalidated.

Wealthbox in Kerdora is in a pilot for selected practices. If Wealthbox isn't listed in Advisor Settings → Integrations, contact Kerdora Support to ask for access.

Did this answer your question?