Intakes and checks
Create and advance records directly in Data views.
An intake is a section of grid views in Data, with each view showing one step on the same table. Edit the existing row; do not create another record each time it advances. This CRM uses Data views for registration, daily work and review.
Start in the right table
| Task | Entry view | What to complete |
|---|---|---|
| Name a shared person | People → Step 1 - Name the person | First Name* and the known Last Name |
| Add contact details | People → Step 2 - Add a way to reach them | Email, then Telephone and notes when known |
| Identify a shared company | Companies → Step 1 - Name the company and its site | Legal Name*, Alternate Name* and known Website°; review missing source facts |
| Start a lead | Deal → Step 1 - Say who the client is | Company° or People° |
| Assign the seller | Deal → Step 2 - Set who is accountable | Accountable (Company), then Accountable (Person) |
| Complete a proposal | Deal → Step 3 - Complete the proposal | Product*, Value* and Expected Close Date* at Proposal Sent or Negotiation |
| Advance or close | Deal → Step 4 - Advance or close the deal | Deal Stage*, then Won, Lost or Abandoned once Deal Check is clear |
| Work open leads | Deal → Leads | Deal Stage* as the conversation advances |
Search the Directory before adding identities. Core owns People and Companies. The visible intake does not establish a verified two-way sync contract; correct the source when the mirror does not allow editing. Manage deals explains identity reuse and accountability.
Advance the same row
Fill the inputs shown in the current step. Intake Step is calculated from record values and determines the next matching queue. A row can disappear immediately after an edit because it now matches another step. Find it in the next step or the table’s reference view; disappearance is not deletion.
Deal moves through client, accountability, proposal data (only at Proposal Sent or Negotiation) and advancement/outcome. Check - Deal exceptions collects any Deal, open or closed, with a Deal Check warning or missing data. A campaign has no intake of its own in the CRM: pick it in Campaign° on the Deal. Read the check beside the relevant status before changing that status.
Separate checks from intake steps
Interaction has Check 1 - Complete event data, Check 2 - Upcoming meetings and Check 3 - Record meeting outcome. These are work/check queues, not a separate form. Create a manual contact or update an existing booking in the table, then use the queues to complete and review it.
Campaign (mirror) has availability, monitoring, exception and history views. A valid campaign is not linked to any lead until a Deal picks it in Campaign°. See Manage campaigns.
Recognize completion and exceptions
* marks an expected business input and ° an optional input. A field label is not a database constraint. A blank Intake Step means the record no longer matches a step; it does not certify all business checks. Review Deal Check or the relevant event check and confirm the intended state in a reference view.
Interaction next-action fields are not copied anywhere; the next action of a sale lives in Tasks. Closed deals leave the intake, including a disqualified lead set to Lost. These are current routing details, not instructions to duplicate the record.
Maintain the view contract
Follow the adopted Intake views rule: a section of grid steps, one routing formula, only the necessary columns and a final validation/status decision. The entity references record current formulas; the rule describes the intended pattern and does not prove every existing view conforms. Keep filters aligned with the formula labels after any change.
Use Data views for the full catalog and direct links, and Troubleshooting when a record is missing or remains in a check.