Why can't I find or connect Slant?
Slant is available to every Kerdora advisor through Advisor Settings → Integrations. If Slant doesn't appear there, contact Kerdora Support.
Confirm you're using your advisor account, then open your account menu → Integrations.
Look under CRM for Slant's row. A row with Connect isn't connected yet; select it to open the Connect Slant pop-up. If you have many tools, use Search tools.
For “Couldn't load your connected tools”, choose Try again. That message means Kerdora couldn't load connection information.
If Slant isn't listed, or Import from Slant says “CRM import isn't available on your account yet.”, contact Kerdora Support with your advisor sign-in email and exact message.
For setup and supported behavior, see Slant: Connect Your CRM, Import Households, and Sync Notes, Tasks, and Meetings.
Why did my Slant sign-in fail?
Retry a failed Slant sign-in from Advisor Settings → Integrations: select Slant's row, then Connect Slant in its pop-up, using your intended Slant account. After a failed sign-in, Kerdora reopens that pop-up with one of these messages. If Slant's row says Needs reconnecting, use Reconnect on that row or in Slant's drawer. If you return to Settings without a message and Slant still isn't connected, start a fresh attempt.
“Slant access wasn't granted.” means access was declined during sign-in. Retry if you want to grant access.
“Connecting Slant took too long. Try again.” means a sign-in attempt expired. Start a fresh attempt and finish within 10 minutes.
“Kerdora couldn't confirm the Slant sign-in. Try again.” means Kerdora couldn't validate that return from sign-in. Start again from Kerdora.
“Slant didn't finish connecting. Try again.” means sign-in didn't finish exchanging access. Retry once.
“Couldn't start connecting to Slant. Try again.” means Kerdora couldn't start your redirect. Retry from Settings.
“Couldn't reach Slant. Try again in a moment.” means Slant couldn't be reached. Wait briefly before retrying.
“Couldn't connect Slant. Try again.” is a general failure message.
If a fresh attempt fails, send Kerdora Support your exact message and failure time. Don't send passwords or access tokens.
Why did Slant connect but refuse to let Kerdora read my account?
“Slant connected, but didn't let Kerdora read your account. Try again.” in Advisor Settings means Slant issued sign-in access but refused Kerdora's account-identity check.
It doesn't confirm a working household connection or permission to send notes and tasks.
In Advisor Settings → Integrations, choose Reconnect on Slant's row or in Slant's drawer. If Slant's row shows Connect, select it and choose Connect Slant.
Confirm you're signing in to the Slant account you intend to connect.
If refusal repeats, contact Kerdora Support with your connected-account identity, message, and failure time. Check your Slant account access with your Slant administrator or Slant Support as needed.
Kerdora's screen doesn't identify a required Slant role or offer a permission selector that repairs this refusal. Don't switch Slant accounts at random or assume a different role is required solely from this message.
Why isn't a Slant household in my import list?
Import from Slant shows households from Kerdora's last read of Slant: households whose type is Client, Prospect, or Past client. A household created in Slant since that read, or one of another type, won't appear.
Open Advisor Settings → Integrations, select Slant's row, and choose Import clients.
Check the stage buttons above Import from Slant's list. Clients, Prospects, and Past clients each show one stage, and appear when Slant has prospects or past clients; a prospect isn't under Clients. If a book dropdown shows, choose All books.
Select All and clear Search households. “No households match these filters.” means your current view or search has no matching rows.
Select Get latest from Slant, then search for the household or a person's name.
Check directly in Slant that your connected login can read that household and that its type is Client, Prospect, or Past client.
Skipped can contain a household Kerdora suggested skipping: one in a Slant book where you aren't principal, or a prospect or past client with no strong match. Review that row before changing Skip.
“No longer in Slant” means Slant didn't return a previously read household. It doesn't delete an existing Kerdora client.
Why can't Kerdora read my Slant import?
On Import from Slant, a read failure means Kerdora hasn't finished gathering household records; a disconnected account needs connecting before another read.
“Slant isn't connected” on that page means reads are off.
Choose Reconnect it in Settings beside “Slant isn't connected”, or open Advisor Settings → Integrations yourself.
Choose Reconnect on Slant's row. If Slant's row shows Connect, select it and choose Connect Slant.
Return to Import clients. With an active connection and no household records read yet, a first read starts on its own.
For other messages on Import from Slant:
“Connect Slant first” offers Open Settings; choose it and connect Slant in Advisor Settings → Integrations.
“There's no import for this tool” means your import address isn't supported. Choose Open Settings, then Import clients in Slant's drawer.
“Couldn't get your households from Slant”, or “Getting your households from Slant did not finish.”, means a read failed. Address any reason shown, then choose Try again.
“Couldn't load your Slant import” with “Check your connection and try again.” means import-page data couldn't load. Choose Try again.
“Reconnect Slant in Settings → Integrations first.” and “Slant stopped accepting Kerdora's access. Reconnect it in Settings → Integrations.” require reconnection. A failed read doesn't mean Kerdora imported new clients.
Why does my Slant import review show warnings?
On Review your import, warnings mark missing data, member decisions, or a possible duplicate. Households with warnings are listed first in each group. To finish after import counts the ones with gaps to fix after import; a duplicate-name warning isn't counted there. Check them before choosing Import N households.
“No birthday for {names}.” identifies missing birthdays. Confirm dates in Slant and choose Get latest from Slant, or correct imported details before planning.
“No state in the address.” means Kerdora couldn't find a US state. A “No state” label doesn't mean a new Kerdora household will stay blank; its default can be Alabama. After import, open that household → Profile → Household and correct State if needed; changes save immediately.
“No head of household in the CRM; {name} is the primary Client.” means Kerdora chose a primary Client from available adults. Check that choice.
“No head of household and no adult to plan for.” needs a household review before import.
“You already have a client named "{name}".” means a Kerdora client has that name. If both are the same household, choose Back, open that household's dropdown in the In Kerdora column, and pick its existing client. Review again; if these are different households, keep Create new client.
“Check this match” marks a weak suggested link. Select that row and check each person's pairing.
Select Skip to keep an unresolved household out of this import. Correct Slant data, choose Get latest from Slant, and review again.
Why did Slant members become Other Adults or stay out of Kerdora?
For advisors, Kerdora maps Slant household roles to Kerdora member types on import. On Review your import, a linked household's people show their type under In Kerdora. For a new household, Review your import shows only names and warnings, so check member types in Profile → Household after import. Review these mappings before import, because member types affect a household's planning structure.
Heads, spouses, and partners normally map to Client. Dependent children and grandchildren map to Child. Non-dependent children, other adults, and other dependents map to Other Adult, or Child if under 18.
“A plan has at most 2 Clients; {name} will be an Other Adult.” means Kerdora reached its Client limit.
“The CRM gives no household role for {name}; added as an Other Adult.” means Slant didn't supply a recognized role; without a head, Kerdora can also promote an adult to primary Client.
“Not imported (deceased): {names}.” and “Not imported” identify people excluded because Slant marks them deceased or supplies a date of death. Verify Slant's record if that is incorrect.
Select Skip for a household that needs correction, then choose Get latest from Slant and review again. For links, inspect “Same as” pairings before creating any new members.
What should I do if a Slant import stops?
On “Import from Slant”, Resume continues a stopped import's saved plan, but appears only on a page that was following that import when it stopped. Leaving or reloading loses this recovery action.
If you see “The import stopped after X of Y households”, choose Resume before leaving. Kerdora skips completed households and avoids writing the same saved changes twice.
If you left or reloaded and no longer see that message or Resume, don't import those households again yet. A new import starts a new plan and can create a second client for a partly imported household. Contact Kerdora Support with household names and import time.
If Resume repeatedly fails, give Support your progress counts and exact message. Don't delete a partly imported client as a recovery step.
A stopped import doesn't by itself mean Slant needs reconnecting. Applying an import uses household records Kerdora already read, and Resume doesn't check Slant's connection.
Why did my Slant import skip households?
When an import finishes, Import from Slant says how many households were imported. A line such as “2 changed since the review or could not be linked. They are still in the list.” identifies households that weren't imported.
Review those remaining households' choices on Import from Slant, then review and import them again.
“Some households changed in Slant since the review. Review them again.” means Kerdora's stored household records no longer match your review, so Kerdora imported none of the selected households. It doesn't mean Kerdora always reads Slant live right before importing.
“Someone you chose is no longer in that client. Review the household again.” means a person pairing is no longer valid. Pick the correct current member in a new review.
For an unresolved household, contact Kerdora Support with its Slant name, intended Kerdora client, and exact message.
What does "That client is already linked to another household" mean?
“That client is already linked to another household.” on “Import from Slant” means your chosen Kerdora client is reserved for or linked to another household through your advisor Slant connection.
In a household's dropdown, a client under Already linked shows which household has it, for example “Linked to Whitfield Household” or “Chosen for Whitfield Household”. Check existing import choices before selecting a different target. Don't choose Create new client merely to bypass this error; that can leave you with another copy of an existing household.
If an existing link is wrong, contact Kerdora Support with your Slant household name and intended Kerdora client. “Import from Slant” has no per-household unlink control.
Why does my Slant import say "Something went wrong. Try again."?
“Something went wrong. Try again.” on Import from Slant is a general error, so check your import size and Slant connection before retrying.
One review and import takes at most 1,000 households. With more set to come in, Import from Slant's header button reads, for example, “Review and import first 1000 of 1400”; import the rest in a second round. Check Advisor Settings → Integrations for a Slant reconnection message and address it if present.
If an import already started, inspect its progress before submitting another batch. Contact Kerdora Support for persistent errors with your household names, selected count, attempted action, exact message, and time.
Why does Kerdora say it's already reading or importing from Slant?
“Kerdora is already getting households from Slant or importing them. Wait for it to finish.” on Import from Slant means another read or import is active for your advisor Slant connection.
Wait for that work to finish before trying another read or import. To inspect progress, open Advisor Settings → Integrations, select Slant's row, and choose Import clients while that work is running.
If progress remains stuck, contact Kerdora Support with your Slant account label, progress counts, and when you started. Repeatedly submitting another import won't bypass an active job.
Why can't I import a Slant household again after deleting its Kerdora client?
An advisor's “Import from Slant” page can retain an Imported row after its Kerdora client has been deleted. That row can show a client link or “Open client”, even though the destination client no longer exists.
Deleting a Kerdora client doesn't clear its Slant household mapping. There is no per-household unlink control, so Get latest from Slant doesn't make that row available for another normal import.
Contact Kerdora Support before resetting your connection.
A connection-wide reset requires disconnecting with “Also delete the households and people read from Slant. Clients already imported into Kerdora stay.”, which removes all links for your connection. Reconnecting then requires linking surviving Kerdora clients again.
Don't delete any more clients to repair the list. Give Support the Slant household name and the deleted Kerdora client's former name or link.
Why didn't "Check for changes" update my Slant-linked client?
“Check for changes” on a client's Profile → Household only applies fields you confirm in “Changes from Slant”. Opening “Changes from Slant” or choosing Cancel doesn't apply Slant values.
Open that linked client → Profile → Household → Check for changes.
Inspect “Updated in Slant”, conflicting choices, and “New in Slant”. Select desired changes, then confirm with a counted action such as “Update 2 fields · add 1 person”.
For “Slant changed again while you were deciding. Check again to see the latest.”, choose Check again and review a new comparison.
“Nothing changed since you last checked.” or “Nothing changed since the import.” means no differences in compared fields.
“Check for changes” doesn't normally compare filing status or household roles.
A person you previously declined under New in Slant isn't offered again automatically. Check whether that person already exists in Kerdora before adding them manually. If you need help restoring a Slant person link, contact Support.
If “Changes from Slant” says “Something went wrong. Try again.”, Slant may not have answered. Choose Try again in a few minutes. For a reconnect message, reconnect in Advisor Settings → Integrations first.
Why didn't my Kerdora note or task send to Slant?
A missing Slant copy in a Kerdora note editor or task drawer can mean that item isn't eligible to send. Check that item's status, then review the switches in Slant's drawer in Advisor Settings → Integrations.
Confirm that this item's Kerdora client is linked to Slant under Profile → Household and that your Slant connection is active.
Check “Send general notes to Slant” or “Send tasks to Slant”. First sends normally require creation after that switch was turned on.
For a note, check whether it is client-visible. Those notes also require “Include notes visible to the client”. After editing, allow 90 seconds of no edits before a send attempt.
For a task, check whether it was advisor-assigned for its first send. Household-member tasks aren't sent for the first time.
Inspect “Won't go to Slant” or “Not updated in Slant” on an excluded note. Use Send or Resume only if you now want it sent.
For older open advisor tasks, Slant's drawer can offer Send it or Send them. There is no equivalent older-note history send. If an eligible item shows “Couldn't send to Slant”, inspect its failure tooltip before retrying.
What should I do when Kerdora says "Couldn't send to Slant"?
“Couldn't send to Slant” in an advisor's Kerdora note editor or task drawer means a send attempt failed. Its tooltip helps distinguish lost access from a temporary failure or a refused write.
If the tooltip says “Reconnect Slant in Settings → Integrations.”, reconnect there first.
“Slant didn't answer. It will be tried again.” means a temporary provider failure. Kerdora schedules retries with increasing waits; allow those attempts before retrying manually.
“Slant didn't accept it.” means Slant refused the write. Check your account's access and contact Kerdora Support if it repeats.
“Something went wrong sending it to Slant.” is a general failure. Choose Retry once; contact Support if it persists.
“Sending to Slant…” confirms a queued retry, not successful delivery.
“Couldn't retry. Check Slant in Settings → Integrations.” means that retry couldn't be queued; inspect connection status and sending choices.
In Settings, “1 note or task wasn't sent to Slant” or “N notes or tasks weren't sent to Slant” counts failed items for enabled sending. Give Support the affected household, item title, tooltip, and failure time.
Why won't my Slant send switches or older-task send save?
The controls in Slant's drawer in Advisor Settings → Integrations save as you change them. If a save fails, don't assume your requested switch state took effect.
“Couldn't load the notes and tasks switches” means Kerdora couldn't fetch sending choices. Choose Try again beside that message before changing anything.
“Couldn't save. Try again.” means a switch or note-exclusion change failed.
Retry the intended change, then reopen Slant's drawer or the affected note to inspect its current state.
“Couldn't send them. Try again.” means your older-open-task send request failed.
Check Slant's connection and task switch, then retry Send them or Send it if that offer still appears. “Sending 1 task to Slant…” or “Sending N tasks to Slant…” means Kerdora queued that request.
If failures repeat, send Kerdora Support the exact control and message. Don't repeatedly turn switches off and on: turning a switch back on resets first-send eligibility for never-sent items.
What does "Deleted in Slant" mean?
“Deleted in Slant” in an advisor's Kerdora note editor or task drawer means Kerdora found that its sent copy was removed in Slant. Kerdora retains the original Kerdora item and stops updating the removed copy.
For notes, Kerdora detects removal when a later update finds no Slant copy. For tasks, a received Slant deletion notification or a later send check can identify removal. Don't expect every deletion to appear immediately.
The note tooltip says, “Someone deleted the copy in Slant, so changes here no longer go there.” The task tooltip says, “Someone deleted it in Slant. Changes here no longer go there; delete it here too if it's done with.”
Choose Send again only if you want a new Slant copy. Otherwise, leave sending stopped and decide separately whether the Kerdora item should remain. Check your records before deleting a Kerdora task simply because its Slant copy was removed.
Why didn't completing or editing a Slant task update Kerdora?
A Slant task change only updates a Kerdora task when that task was originally sent by Kerdora, task sending remains on, and Kerdora receives a usable Slant change notification. Slant's own tasks aren't imported into Kerdora this way.
Open that Kerdora task's drawer and inspect “CRM”. Confirm that it has a successful Slant copy, rather than only a sending or failure status.
Check Send tasks to Slant in Slant's drawer in Advisor Settings → Integrations.
Reopen the task and inspect its current values. Status information is reread about every 60 seconds, but that isn't a guaranteed return-sync time.
If a required completion or deadline hasn't arrived, update the Kerdora task directly. Contact Support with both task identities and the change time.
“Completed in Slant”, “Reopened in Slant”, or “Edited in Slant” confirms a recorded return change. “Assigned to {name} in Slant” only reports Slant assignment; it doesn't reassign the Kerdora task.
Get latest from Slant and Check for changes are household actions, not task-return repair buttons.
Why are Slant notes missing or read-only in Kerdora?
For advisors, Slant rows in a linked client's Office → Notes are read-only and limited to the first 50 notes Slant returns. Kerdora excludes hidden, empty, and Kerdora-sent notes from those rows.
Open that linked client → Office → Notes and choose Slant under Note type. Check Profile → Household for your Slant link if that filter is absent.
If a recently changed note is missing, allow Kerdora's 15-minute Slant note cache to expire, then reopen Notes. A successful read doesn't display a separate Refresh button.
For a complete list or an edit, open Slant directly and find that household.
“Slant notes can't be read” with “Reconnect Slant in Settings” means access needs reconnection. “Couldn't reach Slant” means a read failed; use Retry after waiting briefly. “Slant is busy right now” calls for waiting a few minutes before choosing Retry.
“Reading…” means a retry is in progress. A missing colleague name doesn't mean a note has no author; Kerdora shows “You” for your connected login and can omit other Slant author names.
Why is a Slant meeting or the Meetings tab missing?
A client's Office → Meetings depends on your link to a Slant household. Kerdora includes meetings on linked households within its last-24-months and next-90-days window.
Check that client → Profile → Household for “Linked to Slant”. Connect Slant and import or link that household if needed.
Check Advisor Settings → Integrations for an active Slant connection.
Open Office → Meetings and inspect “Upcoming” and “Past”. Use Slant directly for meetings outside Kerdora's window or missing from a large book.
“Meetings come from Slant” with “This client isn't linked to a Slant household you can read.” means no readable connection was found. It can appear after disconnecting even if a retained link still leaves the Meetings tab visible.
“No meetings” with “Slant has no meetings for this household in the last 24 months or the next 90 days.” reports an empty available list. Verify the household association directly in Slant before concluding that no meeting exists.
“This meeting isn't on the household” with “Slant no longer lists it for this client's household.” means a previously opened meeting isn't available for that household. Return through All meetings.
Why doesn't practice Home show my Slant meetings?
Practice Home's Today card shows only today's meetings for Slant households you linked. On a day with nothing scheduled, Home shows upcoming planning dates in that place instead, so an empty day doesn't mean Slant stopped working.
Check that Slant is connected in Advisor Settings → Integrations. Without it, Home has no Slant meetings to show.
Check that your meeting's household is linked. Import or link it from Import from Slant if needed.
For a later day, open that client → Office → Meetings, which lists Upcoming and Past meetings.
Under the Today card, “Slant meetings can't be read” with Reconnect Slant in Settings means Slant needs reconnecting. “Couldn't reach Slant” or “Slant is busy right now” offers Retry and can show “meetings as of” a time.
On a client's Office Home, “No meeting booked in the next 90 days” means no next meeting was found in Kerdora's available window. Check Slant directly for missing household associations or recent changes.
Why can't Kerdora load or refresh Slant meetings?
Slant meeting pages can fail to read current records while retaining an older stored copy. Check any displayed error message before relying on a meeting time or summary.
“Couldn't load meetings” with “Check your connection and try again.”, or “Couldn't load meetings.” on a client's Office Home, offers Try again. Retry after checking your connection.
“Meetings can't be shown right now” means no meetings can be displayed from a failed read. Inspect its accompanying connection message.
“Slant meetings can't be read” with “Reconnect Slant in Settings” requires reconnecting in Advisor Settings → Integrations.
“Slant can't be read. Showing what Kerdora last read.” on a meeting page means Slant needs reconnecting and you're viewing Kerdora's stored copy. Choose Reconnect Slant in Settings.
“Couldn't reach Slant. Showing what Kerdora last read.” means a meeting page retained an older copy after a failed read. Wait briefly, then reopen that meeting or use Retry where offered. A busy message asks you to wait a few minutes and can also accompany an older copy.
“meetings as of {time}” dates a stored list. Successful reads don't show a Refresh control; a retry can also be limited to a full read every 5 minutes. Check Slant directly for urgent changes instead of relying on an older copy.
Why is a Slant summary or transcript missing or outdated?
For advisors, a client's Office → Meetings page can only show summaries and transcripts Kerdora has read from Slant. Kerdora doesn't generate missing Slant meeting content.
“This meeting hasn't happened yet” with “Slant adds the summary and transcript after it.” describes an upcoming meeting without content. This message doesn't guarantee every meeting will get a recording or summary.
“No summary” with “Slant has no summary or notes for this meeting.” means the available meeting detail lacks summary and notepad text.
“No transcript” with “Slant has none for this meeting.” means no transcript is available in that response.
Where “Slant adds it after a recorded meeting.” appears, check whether a recording and transcript actually exist in Slant.
“Loading the meeting…”, “Loading the summary…”, and “Loading the transcript…” mean reads are still underway. Wait for the result before diagnosing missing content.
Kerdora stores a transcript once, including an empty first copy, and doesn't refresh later corrections. Check Slant directly for updated text; contact Kerdora Support if Kerdora's stored copy is incomplete. Don't disconnect every household just to try to refresh 1 transcript.
Why can't Dora find a Slant record?
Dora can read Slant only in an advisor conversation for a client linked through that advisor's connection. If a record is missing, first confirm that client's household link in Profile → Household and your active Slant account in Advisor Settings → Integrations.
Dora's read failures can report:
“The Slant connection needs reconnecting (Settings → Integrations), so Slant records cannot be read right now.” Reconnect in Advisor Settings → Integrations.
“Kerdora's Slant request limit for this hour is reached, so Slant cannot be read right now. Try again in a few minutes.” Wait before asking again.
“Slant did not answer, so its records cannot be read right now. Try again later.” Retry later or inspect Slant directly.
Dora reads only the first 50 Slant notes or open tasks returned, excluding Kerdora-sent copies, and can reuse reads for 15 minutes. Meeting searches use stored transcripts and can return at most 40 matching segments. Ask about a narrower date or meeting, or use Slant's own records for a complete check.
How do I fix "Needs reconnecting" for Slant?
“Needs reconnecting” on Slant's row in Advisor Settings → Integrations means Kerdora's Slant access stopped working. Your account menu also says “A tool needs reconnecting”, and Slant's drawer explains, “Slant stopped accepting Kerdora's access. Reconnect to keep it working.”
Open your account menu → Integrations.
Choose Reconnect on Slant's row, or in Slant's drawer, and sign in to your intended Slant account.
Back in Settings, “Slant connected” confirms it. Open Slant's drawer and check the account name under Slant.
Sends wait until you reconnect. Reconnecting with the same Slant login queues eligible missed sends; a different login turns both send switches off. If reconnection repeatedly fails, contact Kerdora Support with your account label and exact sign-in message.
Why does Kerdora say "Slant is busy right now"?
“Slant is busy right now” on an advisor's Notes or Meetings view means Kerdora hit a request-budget or rate-limit condition. Slant requests from imports, sends, pages, Dora, and background meeting reads share limits; repeated refreshes won't remove that limit.
Wait a few minutes before another request.
Use Retry on the affected Notes or Meetings view when offered. A meeting detail page can say, “Slant is busy right now. Try again in a few minutes.”
If you need a record immediately, inspect it directly in Slant.
Kerdora gives outgoing sends a larger share of its request allowance than background meeting reads, but sending can still wait or fail. A busy message alone doesn't mean your Slant login needs reconnecting.
If the message persists, tell Kerdora Support which page or Dora request triggered it, your household, and when it happened. Check timestamps on any stored meetings shown during the delay.
Why does Kerdora say "Sending to Slant is paused for now"?
“Sending to Slant is paused for now” in Slant's drawer in Advisor Settings → Integrations means Kerdora has paused outgoing Slant sends for all advisors. It isn't a per-note exclusion or proof that your Slant sign-in expired.
Keep working in Kerdora and inspect item statuses later. While sending is paused, Kerdora retains its local notes and tasks. A later catch-up can queue eligible changes once sending resumes, provided your connection, switches, and household links still allow them.
Don't repeatedly reconnect or turn sending off and on to clear this message. Changing switches can change first-send eligibility without fixing a service-wide pause. If a time-sensitive record must be entered directly in Slant, track that manual copy so a later Kerdora send doesn't surprise you with another copy.
Contact Kerdora Support if you need the current pause status or help with an urgent item.
What should I do if disconnecting Slant fails?
“Couldn't disconnect. Try again.” in Slant's drawer can mean Slant disconnected but optional deletion failed, especially during a running read or import. Keep that drawer open so you can retry.
If you selected Also delete the households and people read from Slant. Clients already imported into Kerdora stay., wait a few minutes for any running read or import to finish.
In that same drawer, choose Disconnect again. Keep that deletion checkbox selected if you requested deletion, then choose Disconnect to confirm. If Slant already disconnected, Kerdora skips disconnecting again and retries deletion.
If you already closed that drawer and Slant's row now shows Connect, Slant is disconnected, but your requested deletion may be incomplete. Settings has no separate delete action. Contact Kerdora Support with your advisor email, failure time, and whether you requested deletion.
Don't reconnect just to retry deletion. Reconnecting with the same Slant login retains send switches and can queue eligible notes and tasks written while disconnected. If retrying still fails, contact Support instead of deleting Kerdora clients.
Why does "Linked to Slant" remain after disconnecting?
“Linked to Slant” on a client's Profile → Household can remain after an advisor disconnects Slant in Advisor Settings → Integrations without deleting imported source records.
Household links remain unless you select Also delete the households and people read from Slant. Clients already imported into Kerdora stay. during disconnection and deletion succeeds. “Open in Slant” and Office's Meetings tab can also remain; these labels don't mean Slant access is active.
Existing Kerdora clients and copies already sent to Slant stay. Don't delete a Kerdora client to remove its Slant badge. Contact Kerdora Support for help with a mistaken household link before considering a reset of every link through your connection.
