We actually read these.
Ideas submitted here go to the product team, not into a void. Add yours, vote on others, and comment on what matters to your business.
Talk to our Product Managers live: every other Monday, 1:00–2:00 PM ET → https://www.d-tools.com/cloud-product-office-hours
Individual contact records carry first name, last name, job title, and company — but no salutation or honorific (Mr., Mrs., Dr., Prof., etc.). For customer-facing communications (proposals, invoices, service notifications), the convention "Dr. Smith" matters; "Smith" alone reads as informal. In client populations where a contact's spouse uses a different honorific, the distinction matters at the household level too.
A salutation / prefix field on the individual contact record — initially free text, with a sensible default list (Mr., Mrs., Ms., Mx., Dr., Prof., Rev., Hon., etc.) that account admins can extend.
The field surfaced in the contact create / edit form and on the contact detail view.
Salutation rendered consistently in proposal, invoice, work-order, and service-notification templates wherever a contact name appears.
Per-contact storage so a primary client and a spouse on the same household can carry different honorifics.
Optional default in mail-merge templates so users don't have to insert it manually each time.
Custom integration is a relationship business, and high-end residential clients in particular notice when a $40k proposal addresses them as "Smith" instead of "Dr. and Mrs. Smith." Today the workaround is editing the proposal PDF or invoice manually before sending, which kills the value of templated documents. The data model gap forces every customer-facing document into a manual review step, and salutation conventions are different enough across regions and client populations that hard-coding "Mr./Mrs." into templates isn't a substitute.
