Before you start
- An existing lead and permission to maintain it.
- The person’s role and preferred contact details; the correct acquisition source for this record.
Open in your admin application
Use your installation’s admin address with one of these routes. Replace {id} with the actual record identifier.
/lead?LeadID={id}/lead-contact-insert?LeadID={id}/sources/campaignsAdd another person at the same customer
Open the lead’s Contacts tab
Choose Add Contact. The route includes LeadID so the new person is attached to the existing lead.
Complete the contact form
Check Lead, then enter Name, Position, Phone, Ext. and Email. Use Position for the person’s role, such as purchasing manager. Do not create a second company lead merely to add another person.
Save and verify the association
Save the contact and return to the lead. Confirm the person appears in Contacts and that the primary contact information still refers to the intended primary person.
Record activity and attribution
Write a useful activity note
Use Notes → Add Note. Record the interaction, decision, commitment and next action. If work is due later, set Follow Up Date and choose Save Note.
Inspect Source and Campaign
Read both on the lead detail. Source identifies origin; Campaign identifies a particular activity within that origin. The basic lead edit form exposes Source, not a universal Campaign editor. Campaign assignment may come from the import or acquisition integration.
Correct at the appropriate boundary
Change Source through the lead edit form when authorized. For incorrect Campaign attribution, inspect the originating import/integration with the operator responsible for it; do not bury the correction only in Notes.
Use configured tags consistently
Keep tags separate from status and attribution. Where tag actions are exposed, apply the agreed global or personal tag rather than inventing near-duplicate spellings. Confirm the lead appears in the intended tag-filtered view.
Fields & records
| Field / record | Meaning or use |
|---|---|
| Name / Position | Secondary contact identity and role. |
| Phone / Ext. / Email | Contact-specific details, not necessarily the primary lead’s phone/email. |
| Notes / Follow Up Date | Activity history and optional scheduled work. |
| SourceID / CampaignID | Distinct attribution relationships; campaign editing depends on the acquisition workflow. |
Verify the result
- Secondary contact is attached to the correct LeadID.
- The note is visible with the correct next-action date.
- Source and campaign match the acquisition record used by your team.
Troubleshooting
| What you see | What to check or do |
|---|---|
| New contact attached to the wrong lead | Inspect LeadID on the insert route before saving. |
| No Campaign field in the edit form | That is not a missing step: use the configured import/integration workflow. |
| Same tag appears under several names | Use the agreed tag taxonomy; do not treat free-form variants as one category. |
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:contacts-attribution
Feedback records only the page, guide ID and yes/no choice. It never records documentation search text.
Implementation references (3)
FeedingFrenzy.Admin/wwwroot/kScripts/LeadContacts/LeadContact.Insert.ks.htmlFeedingFrenzy.Admin/wwwroot/kScripts/Leads/Lead.Details.ks.htmlFeedingFrenzy.Admin/wwwroot/kScripts/Leads/Lead.Edit.ks.html