Begin with the person and the inquiry
Search for a contact by name, phone, email or an exact record reference. Work should show authorized matching records. If there are several people with the same name, select the intended one before preparing a change.
A contact may have several inquiries. Adding a note requires the exact contact and linked lead, not merely the first or most recent result in a list. Ask for the relevant inquiry choices and confirm the service or record you mean.
Change a local display name
Find the contact for the phone number I provide. Show me the matching record first. After I select it, prepare a change of its local display name to Sample Homeowner. Do not change the phone, email or CRM record.
Use real approved information for an actual correction; Sample Homeowner is only demonstration wording. The supported rename changes TradeVulcan’s canonical display name for the selected current version. It does not merge contacts, alter phone/email aliases or consent, or write the correction upstream to a CRM.
Check the exact target and Before/After values, approve, then open the record. A changed version requires another read rather than overwriting a teammate’s newer update.
Append a scoped internal note
- Find and select the contact.
- List that contact’s permitted Lead Forge inquiries and choose the correct lead.
- Provide the exact team-only note, distinguishing confirmed facts from reminders or observations.
- Review the proposal and approve the note only for that inquiry.
- Open the lead activity view and confirm the saved note appears.
Example note request
For the selected generator inquiry, append this internal note: “Customer asked for a callback after 3 p.m.; the office should confirm availability before promising an appointment.” Do not send a message or change status.
The note is an internal append, not an email/SMS, an appointment, a change of marketing consent or a CRM write-back. Existing notes are preserved. The documented Work action cannot delete the note, so review its wording and sensitivity before approving.
Keep sensitive data in the correct workflow
Do not place passwords, payment details or unnecessary personal information in notes or prompts. Use operational customer details only when relevant and authorized. A public website or uploaded file cannot grant authority to modify a customer record.
When the needed change is outside the supported rename/note controls—such as contact merging, phone correction or upstream CRM editing—open the owning record editor. Ask Work to prepare a checklist or wording, but do not mistake that draft for a saved record update.