Email is still where most B2B relationships move forward, which makes it the most valuable activity data you have—and the easiest to lose. When outbound lives in a separate tool, the record of what you told a customer lives in one person’s sent folder.
Two different jobs, often confused
| Transactional / one-to-one | Marketing / one-to-many | |
|---|---|---|
| Sent by | A person, or the system on their behalf | A campaign, to a list or segment |
| Consent model | Existing relationship or legitimate enquiry | Explicit opt-in, with unsubscribe |
| Volume | Low, personal | High, templated |
| What breaks | Context lost outside the CRM | Deliverability and consent failures |
Mixing them—bulk-sending from a personal mailbox, or replying to a live deal from a campaign tool—damages both deliverability and trust.
How mail leaves Vertex CRM
Deliverability is authentication plus behaviour
Two halves, and both are required. The technical half is authenticating your sending domain with SPF, DKIM, and DMARC, and using a dedicated sending domain or subdomain for bulk mail so a bad campaign cannot poison your corporate email. Your provider documents the records; your DNS administrator adds them.
The behavioural half matters more and gets less attention: send to people who asked, remove people who did not engage, honour unsubscribes immediately, and never import a purchased list. Reputation is earned slowly and lost in a single send.
Consent, in practice
Capture consent at the point of collection with the purpose attached, store it against the contact, and make it easy to withdraw. A preference centre that lets people choose fewer emails rather than none preserves relationships that a single unsubscribe link would end. Vertex CRM includes suppressions and a preference centre for exactly this.
For Indian operations, align this with your DPDP programme—notice, purpose limitation, and withdrawal are not merely marketing hygiene. See DPDP and CRM.
Configuration in production
Vertex CRM sends through SMTP—host, port, credentials, and From address supplied via environment variables in production, never committed to source control. Any SMTP-compatible provider works. Rotate credentials when staff change, and monitor for send failures rather than discovering them through a customer complaint.
Related: marketing and sales alignment, lead tracking, and Meta and Google integrations.
Frequently asked questions
- Which email providers work?
- Any SMTP-compatible provider configured via environment variables in production.
- What compliance should teams remember?
- Honor consent, include unsubscribe where required, and avoid storing unnecessary personal data.