GuideCRMStandard adminv2.0.0source-verified

Create a lead and record the customer context

Enter company and primary contact details, set ownership and source, and verify the new lead before adding more activity.

For
sales-operator
Owner
CRM documentation owner
Applies to
Feeding Frenzy source inspected 2026-09-10
Reviewed
2026-09-10
LeadIDSalesRepresentativeIDSourceID

Before you start

  • Permission to insert leads and access the resulting record.
  • Search company, email and phone first to avoid a second record for the same customer.
  • Know the appropriate configured source and starting status.

Open in your admin application

Use your installation’s admin address with one of these routes. Replace {id} with the actual record identifier.

/leads/lead-insert/lead?LeadID={id}/lead-edit?LeadID={id}
01

Create the record

  1. Open Create Lead

    Navigate to /lead-insert. The form has Company Info and Primary Contact sections.

  2. Identify the company and owner

    Enter Company. Select a Sales Representative, or leave None if the record should remain unassigned. Choose Priority: Hot, Warm, Normal or Cold. Normal is the initial selection.

  3. Record qualification and attribution

    Enter Opportunity Size when known. Choose Lead Status and Source from the configured lists. Source initially selects Self Generated when that source is available; replace it when a more specific source applies.

  4. Enter the address and contact

    Fill Address, Address 2, City, State and Zip Code. Under Primary Contact enter First Name, Last Name, Phone and Email. Check the phone/email formatting before saving.

  5. Create and open the resulting lead

    Choose Create, then open /lead?LeadID={id} for the created record. Confirm the person, company, owner and source. Review any potential-duplicate warning before proceeding.

  6. Add context after creation

    Use Notes → Add Note for the conversation and next action; set Follow Up Date and choose Save Note. Use Contacts → Add Contact for other people. These are related records added after the lead exists, not fields on the initial insert form.

Product proof

These Phase 1 frames are capture specifications, not application screenshots or runtime evidence.

published proofNorthline lead detail showing Avery Chen, Jordan Lee and the linked commerce account.
Verified Northline lead context and linked commerce account.Synthetic Northline fixture evidence; no customer message or live record was used.Runtime evidence northline-launch-proof-2026-09-16 · northline-proof-checkpoint-2026-09-16

Fields & records

Field / recordMeaning or use
CompanyOrganization or trading name; primary contact fields describe the person.
Sales RepresentativeAssignment, not the company account. None leaves the lead unassigned.
PriorityHot = 1, Warm = 2, Normal = 3, Cold = 4 in the insert form.
Lead Status / SourceConfigured reference values; do not replace these with free-text notes.
Opportunity SizeNumeric opportunity estimate; enter a value only when meaningful.

Verify the result

  • Reopen the lead and check the persisted fields, not just the success message.
  • Confirm the assigned representative can find the lead in the intended queue.
  • Confirm the new note and follow-up are visible on the detail record.

Troubleshooting

What you seeWhat to check or do
Save reports invalid contact dataCorrect the phone or email field on the form; do not discard the rest of the customer context.
Lead missing from My LeadsCheck assignment. An unassigned lead belongs in the unassigned queue, not a representative’s personal queue.
Existing customer foundEdit the existing lead instead of creating another one; review duplicate relationships separately.

Version & scope

Procedure checked against current Feeding Frenzy forms and services. Source verification is not a claim that a live payment, message, customer transaction or full operator run occurred.

Public guides describe shared controls, records and configuration boundaries using fictional data. Tenant URLs, credentials, customer records, provider identifiers and installation-only procedures belong in customer-controlled documentation and are excluded from public pages and search.

Version
2.0.0
Change source
Current Feeding Frenzy forms/services plus reconciled Wiki topics
Feedback key
guide:lead-context
Was this guide helpful?

Feedback records only the page, guide ID and yes/no choice. It never records documentation search text.

Implementation references (4)
  • FeedingFrenzy.Admin/wwwroot/kScripts/Leads/Lead.Insert.ks.html
  • FeedingFrenzy.Admin/wwwroot/kScripts/SimpleObjectInsert.ks.html
  • FeedingFrenzy.Admin/wwwroot/kScripts/Leads/Lead.Edit.ks.html
  • FeedingFrenzy.Admin/wwwroot/kScripts/Leads/Lead.Details.ks.html
← All documentationSoftware feature map ↗