Skip to main content
Chert for Salesforce is a Managed 2GP package that lets reps send iMessage from Lead, Contact, and Account records. Replies are written back to Salesforce as Chert_Message__c rows and mirrored onto the Activity Timeline as standard Tasks.
Salesforce Lead record page with the Chert Conversation component visible in the right rail

The chertConversation Lightning Web Component on a Lead record page.

​
When to use it

Use the Salesforce package when your sales team works primarily from Salesforce and needs iMessage activity recorded on the CRM record.

​
What gets installed

| Item | Where it shows up | What it does | |---|---| | Managed 2GP package | Installed Packages, namespace Chert | Current version 0.1.0-2; coordinate version changes with Chert. | | chertConversation LWC | Lead, Contact, Account record pages | Conversation pane for sends, replies, status, and campaign context. | | ChertSendIMessage | Flow action / Apex invocable | Sends an outbound iMessage and returns the Chert message ID. | | ChertInboundRest | Apex REST endpoint | Receives inbound replies from Chert. | | Chert_Message__c | Custom object | Append-only inbound and outbound message log. | | Chert_Endpoint + Chert_Tenant__mdt | Setup | Stores the Chert API endpoint, tenant slug, signing secret, and inbound token. | | Chert_Messaging_User | Permission Set | Grants end users package object, field, Apex, and Named Credential access. |

​
Requirements

​
Minimal Flow example

Add an Action element in Flow Builder, search for Chert Send iMessage, and bind: Treat duplicate = true as success. The send was already accepted within the deduplication window.

​
Next steps

Onboarding

Seven-step setup from package install to first verified send.

Configuration

Wire up the Named Credential, Custom Metadata, and Permission Sets.

Architecture

Component map, sequence diagrams, and entity relationships.

Security

Trust boundary, HMAC signature format, and data handling.