Skip to content
CRM.me

Practical workflow guides with inspectable diagrams

Each guide maps a real CRM.me workflow from trigger to proof so teams can launch Gmail tracking, pipeline hygiene, AI governance, admin setup, and mobile selling with credible product context.

Gmail tracking

Inbox-first sales reps

Set up tracked email, templates, document attachment, recipient validation, and CRM logging without claiming store approval before it is real.

Diagram

  1. Gmail compose

    Step 1

  2. Tracking controls

    Step 2

  3. Recipient validation

    Step 3

  4. CRM activity

    Step 4

  • Confirm tracking and privacy state before send.

  • Attach only approved collateral.

  • Log activity to the matching account or opportunity.

Tied to Gmail compose toolbar, side sheet, popup, and live Gmail DOM QA evidence.

Pipeline hygiene

Sales managers and RevOps

Use stage discipline, stale-deal checks, next-action review, and forecast risk cues to keep pipeline reviews useful.

Diagram

  1. Stage swimlane

    Step 1

  2. Deal risk

    Step 2

  3. Next action

    Step 3

  4. Forecast review

    Step 4

  • Filter at-risk and closing deals first.

  • Update stale stages from the pipeline view.

  • Review the next action before changing forecast posture.

Tied to CRM pipeline, mobile pipeline swimlanes, account workspace, and opportunity records.

AI CRM governance

RevOps, IT, and AI operators

Deploy AI recommendations with visible source records, confidence, approval controls, and dismiss/undo behavior.

Diagram

  1. Source records

    Step 1

  2. AI recommendation

    Step 2

  3. Human approval

    Step 3

  4. Audit trail

    Step 4

  • Inspect source records before approving AI actions.

  • Use confidence and timestamp context in reviews.

  • Keep admin audit and role permissions aligned.

Tied to source-backed evidence panels, command palette AI actions, and admin audit surfaces.

Admin setup

Workspace admins

Prepare users, roles, groups, billing, providers, system health, and privacy workflows before release.

Diagram

  1. Users and roles

    Step 1

  2. Provider health

    Step 2

  3. Security posture

    Step 3

  4. Release evidence

    Step 4

  • Preview permission diffs before role changes.

  • Verify provider health and billing readiness.

  • Attach required release evidence before final sign-off.

Tied to admin control center, roles simulator, system health, billing, and release QA guides.

Mobile selling

Field sellers and managers

Use command feed, account deep links, pipeline triage, quiet-hours notifications, and offline-safe states away from desktop.

Diagram

  1. Push alert

    Step 1

  2. Account deep link

    Step 2

  3. Mobile next action

    Step 3

  4. Queued sync

    Step 4

  • Start with urgent command-feed actions.

  • Open exact record links from alerts.

  • Confirm offline, stale, and queued states before mobile release.

Tied to mobile command feed, account detail, notifications, pipeline, settings, and device QA evidence.

Continue to documentation