Exodus Salesforce Docs
Sales User Guide

Sales User Guide

Daily Salesforce workflows for sales reps, managers, and customer-facing users

Use the Sales app in QA for customer work: https://exodus--vesper.sandbox.lightning.force.com/lightning/app/Sales_Workspace.

The Sales app includes Leads, Accounts, Contacts, Address Tracker, Opportunities, Quotes, Sales Orders, Invoices, Stock Lookup, sales dashboards, reports, tasks, events, files, and campaigns.

Operating Model

Sales users should work from the custom Lightning actions and workspace tabs, not from raw object create pages. The repo adds custom actions for converting leads, logging calls, scheduling follow-up, creating opportunities, creating quotes, submitting and reviewing quote approvals, printing quote PDFs, transferring ownership, creating payment orders, sending payment links, sending invoice emails, and sending tracking emails.

Pipeline records are automatic. Quotes and Sales Orders are linked to Opportunities by automation so users do not need to manually create pipeline records just to keep reporting accurate.

Tasks are a first-class sales data source in this project. Lead calls, follow-ups, product interest, buying signals, compliance notes, next steps, and follow-up dates feed lead activity quality fields, conversion readiness, manager reports, and sales dashboards.

Sales Flow

Common Path

  1. Qualify or create the Lead.
  2. Log the structured sales touch and schedule a follow-up when the customer is not converted immediately.
  3. Check duplicates before conversion.
  4. Convert the Lead into Account, Contact, and Opportunity.
  5. Create the Quote from the Account or Opportunity.
  6. Submit the Quote for approval when required.
  7. Convert or sync the approved Quote into a Sales Order.
  8. Send invoice, payment link, or tracking communication from the Sales Order or Invoice.
  9. Monitor customer status through Sales dashboards and reports.

Do Not Bypass

Do not use standard object new-record URLs when a custom action exists for the process. The custom actions enforce required relationships, payment-readiness messaging, approval state, ownership audit, and downstream fulfillment assumptions.

Last updated on

On this page