Manage customer success and accountable account plans

Give each customer a clear next step#

Customer Success organizes internal relationship work over an exact existing CRM customer. Choose a published manual success profile, assign a current responsible person, prepare a plan and record what demonstrates progress. Use actions for accountable next work and check-ins for communication that already happened.

Health is a human-reviewed assessment of the profile’s criteria and supporting dates. Missing evidence stays unknown. A renewal review is a local task; it does not renew a subscription, collect money, contact a customer or change a CRM record.

1. Review the CRM and business prerequisites.
2. Prepare and publish the first success profile.
3. Save the customer-data purpose, privacy review and operating access.
4. Enroll an exact active CRM customer and choose its responsible person.
5. Prepare plans, objectives and actions; record actual check-ins and evidence.
6. Publish a reviewed manual health assessment and revisit stale findings.

Set up the original CRM deliberately#

Use a corporate workspace with Customer Success installed and licensed, CRM configured and the customer role enabled. Installation never silently adds another app or copies records, staff, entitlements or paid allowances between workspaces.

The original CRM customer must remain available under current source permission. Invoicing, Helpdesk, Customer Subscriptions and other finance or service apps are not queried by this scope. Their installation does not add private data to health.

Choose access, a published default and working timezone#

An owner or administrator can prepare and publish a non-customer success profile before the app is configured. Then choose that published default in setup, review customer-data purpose and save the operating settings. This order avoids an artificial setup cycle.

The default profile applies to new enrollment only. Changing it does not rewrite earlier account profiles or published health. Working timezones are explicit; UTC timestamps and date-only deadlines keep their distinct meaning.

Review the purpose and source-notice facts#

Record why customer-success data is needed, the reviewed basis, the relevant notice reference and the decision about indirect-source notice. This review is separate from marketing consent. A customer record, purchase, meeting or health finding never grants marketing permission.

A pending source-notice decision or overdue applicable privacy review blocks fresh identified work until reviewed. Keep free text necessary and proportionate; this app does not provide a special-category, children’s-data or regulated-sector clearance.

Publish a manual profile without rewriting history#

A draft contains lifecycle stages, health criteria, freshness periods and reusable plan templates. Review and publish the exact definition. Published semantic content remains fixed and can be referenced by enrolled accounts and historical assessments.

Prepare a new revision to change the process. Applying it to an existing account is a separate reviewed decision that chooses a valid stage and makes current health unknown. Retiring a profile prevents new selection where allowed; it does not erase historical references.

Move through allowed stages with exit evidence#

Stage keys identify stable workflow steps; labels are the names people see. Each stage declares its permitted next stages and any required exit checks. Open and closed are lifecycle categories, separate from archiving an account.

Choose an allowed next stage, review each required check and attach the actual observation or permitted account evidence. Record why the transition is appropriate. A renamed label, a healthy assessment or a completed action cannot silently move the lifecycle stage.

Define explainable findings and freshness#

Use criteria with a clear label, practical guidance, required status and a freshness period. Findings are criterion met, watch, at risk or unknown. They are categorical manual judgments, not a prediction of churn or an automated decision about customer access.

A known concern remains visible. Missing, stale, changed or removed required evidence prevents a current healthy result. Evidence dates are reviewed against the actual server clock and the pinned profile.

Review a reusable plan and its relative dates#

Profile templates contain a plan purpose, objectives with acceptance criteria and practical actions. Relative due dates are calculated from the explicitly chosen start date in the selected working timezone.

Preview the exact generated plan, objectives, action titles and dates before confirming. Applying a template creates local work once; it does not send reminders or alter the original customer. Subsequent changes use the actual current work versions.

Enroll the exact existing customer#

Search the authorized CRM customer choices and select the precise active record. The review binds its current minimal identity facts rather than guessing a CRM version or matching another person by email similarity. Choose a published profile and deliberately review the privacy purpose.

Each original customer has one retained Customer Success account in the workspace. Repeated requests do not create duplicate accounts. An archived account is restored through its reviewed workflow rather than reenrolled as a new relationship.

Name a current accountable person#

Choose a current eligible staff user and exact workspace membership. A person’s name is not sufficient authority. The responsible person is separate from a staff grant; assignment alone does not give a member access to Customer Success or the original CRM.

Preview reassignment with the current person, new person and open work counts. Confirming changes the assignment generation and accountable open work together. Removed memberships, changed roles and revoked grants take effect before later reads and changes.

Review changed or unavailable original customer facts#

When the original CRM identity changes, Customer Success marks the source as changed and stops dependent fresh work. Select the current original CRM record, review its actual current identity and give a reason before accepting the new identity facts. The account stays bound to that exact original customer. Existing health becomes unknown until reviewed again.

If CRM or the original record is unavailable, retained identity and child content remain restricted according to source access. An owner can inspect permitted Customer Success metadata and protection decisions; recovery does not grant unrestricted CRM access.

Prepare an outcome-focused success plan#

Give a plan a useful title, purpose, start date, optional target date, timezone and concise working notes. Choose onboarding, adoption, relationship or renewal review to explain the work’s purpose. A plan has a current accountable person inherited from account responsibility.

Move a plan through draft, active, paused, completed or cancelled with a reason. Completion must agree with current child outcomes. Pausing or cancelling local work is separate from closing the customer, ending a subscription or changing payment status.

Define success before recording progress#

Attach an objective to the exact current plan. Write acceptance criteria, an optional target date and a measure. Choose a binary outcome, whole-number target or exact decimal target with a unit. Decimal values remain decimal strings; they are not money or hidden financial metrics.

Record the actual observed value, time and supporting evidence. Achieving an objective is an explicit outcome transition with current child work and evidence checks. Updating a value does not silently declare the outcome achieved.

Keep next work accountable and specific#

Prepare a clear action with useful details, optional due date and timezone. It may stand alone or belong to a current plan and, optionally, an objective from that same plan. Select current parent references rather than guessing hidden versions.

Use todo, in progress, blocked, done or cancelled. Record why an outcome changed and provide required actual completion evidence. A blocked action is visible work needing attention; no automatic message, financial effect or customer restriction follows.

Plan and record communication accurately#

A check-in records a meeting, phone conversation, email already exchanged or other communication. An optional scheduled time is a local planning fact; this app does not send email, calendar invitations or reminders.

When communication happens, record the actual occurrence time, summary and outcome. Correct a recorded check-in with a reason, preserving metadata history and invalidating stale evidence versions. Cancelling a planned check-in does not report that a customer was contacted.

Review each criterion against actual evidence#

Prepare a draft from the account’s exact pinned published profile. For each criterion, record an unknown reason or a current finding with actual evidence. Its observation time follows the manual evidence date or the selected record’s actual recorded time; an old record cannot be made fresh by typing a new date. Evidence may be a bounded manual observation or an authorized objective, action or recorded check-in from this account.

Review the explainable overall result and exact evidence dates, then publish the prepared assessment. The person who last saved the draft must publish it. A current owner or different permitted reviewer first opens, reviews and explicitly saves the draft under their own identity; merely opening a page never refreshes preparation proof or expiry. Publishing rechecks current source, assignment, privacy, profile and evidence versions. A stale review cannot be repaired by editing a hidden hash or reusing another account’s evidence.

Separate historical assessment from current health#

Published assessments keep their historical findings and reviewer. Current health additionally considers evidence freshness, source changes, withdrawn or redacted reviews and changes to linked evidence. A historical healthy review may therefore be stale while current health is unknown.

Withdraw an assessment with a reason when it should no longer support current health. Withdrawal preserves the original assessment metadata; it does not silently replace its earlier findings or issue a new review.

Combine current roles, grants, visibility and assignment#

Owners and administrators manage setup, profiles, assignment and privacy decisions. Members need the exact current app grant and source access; authoring additionally requires the configured team ceiling and current assignment. Viewers cannot write, even when an old grant contains a write permission.

Assigned visibility and team visibility are separate choices. A team-reading grant cannot expand a configured assigned-only ceiling. Export permission is separate from reading. Search, counts, selectors, child details, history and CSV enforce the same current scope as the account.

Preview an exact local CSV before committing#

Download the sample for the chosen purpose. Customer enrollment uses existing current customer/profile/assignee references. Action imports use exact current account and optional parent fences. Keep the closed headers, explicit dates, timezone and required versions; do not substitute display names for IDs.

Preview validates the whole file, preserves row numbers and reports invalid or duplicate facts. It makes no account or work changes. Confirm the exact encrypted preview before its expiry. Commit rechecks current permission, source, settings, assignment and every row fence atomically; no partial successful import is presented.

1. Download the current purpose-specific sample.
2. Use authorized current references from the app or permitted export.
3. Choose or paste the UTF-8 file and inspect every reported error.
4. Review the exact valid rows and expiry.
5. Confirm once and inspect the current result before another decision.

Export only the records you can currently read#

Exports are bounded to the supported accounts, plans, objectives, actions, health or history purpose and your current filters and permissions. Default exports omit free-text, contact channels, raw evidence and financial fields. They are local downloads, not email or provider jobs.

Cells that spreadsheet software might interpret as formulas are neutralized. A downloaded file remains the recipient’s responsibility; removing a staff grant cannot retract an earlier authorized download. Do not treat an export as marketing permission.

Understand the decision trail without archiving private text#

History shows the actor label, time, record type and version, changed field names and an appropriate reason. It does not copy the full earlier private note, raw review body or hidden original-source data into an audit archive.

The current record and historical decision metadata answer different questions. Private text removed by redaction is not recovered through events, operation receipts, lists or exports.

Review and redact selected Customer Success copies#

Select the exact groups: account identity snapshot, plan text, objective text, action text, check-in text or health explanations. Preview the affected records and current-health effect, then confirm the scope and reason.

Redaction changes Customer Success copies only; it does not change the original CRM customer. Selected private text cannot be restored. Operational IDs, necessary state and metadata history remain. Identity redaction stops fresh work, and privacy-generation changes invalidate stale account reviews and evidence.

Review retention before keeping or archiving work#

The owner chooses an appropriate review interval and records the purpose and basis for continuing to retain account data. The interval is an operating review date, not a universal lawful period or an automatic purge promise. Review actual country, sector and rights-request facts.

Archive stops fresh customer-success work while preserving retained records. It does not delete the original CRM customer. Restore requires current prerequisites, source identity, profile and assignment review and does not recreate redacted text. If an unredacted archived account’s earlier profile was retired, review a published replacement before restoring work. A permanently redacted identity copy remains archived.

Protect retained records when fresh work is unavailable#

The dedicated retained-recovery page is available only to the current workspace owner or administrator. It can show permitted retained Customer Success records and support reviewed archive, redaction and assessment withdrawal without silently reinstalling the app.

Current CRM/source restrictions still apply. Recovery cannot enroll customers, create or publish work, publish profiles or health, assign staff, restore grants or turn a retained source reference into private CRM access. Reinstallation uses the ordinary app and prerequisite workflow.

Resolve a changed or uncertain request deliberately#

A validation response keeps the relevant draft fields available so you can correct them. A conflict means the reviewed record, source, assignment, profile or permission changed; reopen the current record and prepare a new decision.

If the response cannot establish whether the original request completed, the form keeps its original request ID locked. Check that request’s receipt. A confirmed completion opens the current guarded record; it does not re-enable the stale create form. Do not repeatedly submit a replacement command or assume a missing receipt proves that nothing happened.

Review actual country and source-purpose requirements#

Business country comes from the workspace’s declared reviewed facts. A customer’s country, working timezone, interface language and original source are separate facts. Country selection records context; it does not provide statutory approval or a universal privacy certification.

Review applicable national, provincial, state, sector and free-zone rules for Australia, New Zealand, the United Kingdom, EU/EEA, United States, Canada, Saudi Arabia, United Arab Emirates, Qatar, Kuwait and Pakistan. New Zealand indirect-collection notice, Canadian province, US state/sector and Gulf free-zone or sector applicability need actual facts. Customer-success notes must never become marketing eligibility automatically.

Use the official sources below for the applicable review. The manual health workflow provides access, evidence and retention controls; it does not automate consequential customer decisions or certify legal compliance.

Official references: Australia: OAIC Australian Privacy Principles ↗ · New Zealand: Privacy Commissioner principles ↗ · United Kingdom: ICO principles ↗ · EU/EEA: EDPB basic principles ↗ · United States: California privacy rights and applicability example ↗ · Canada: OPC business privacy guidance ↗ · Saudi Arabia: SDAIA PDPL ↗ · United Arab Emirates: government data-protection overview ↗ · Qatar: NCSA guidance hub ↗ · Kuwait: CITRA current regulation index ↗ · Pakistan: MOITT legislation register ↗