We use optional, privacy-safe analytics to understand which pages help visitors. Nothing optional runs until you choose. Privacy policy

Skip to content
SendiMessage
Start Pilot
CRM messaging

Your CRM already knows when to message. Let it.

Deals advance, leads arrive, cases update — your CRM sees every moment worth a message. CRM messaging turns those events into timely texts, and returns every delivery event and reply to the record where the team already works.

Try the interactive demo

The communication problems

  • Follow-up speed decided by rep memory instead of workflow triggers
  • Conversations happening off-CRM, invisible to the team
  • Email sequences with single-digit response rates
  • Replies landing in a shared inbox nobody owns

Recommended workflows

Lead follow-up
Minutes after capture, while interest is warm and consent fresh.
Deal-stage nudges
Proposal sent, renewal near, payment due — workflow-triggered.
Two-way conversations
Replies return to the record with the owner notified.
Timeline write-back
Delivery events and replies as CRM activity via your middleware.
Hi Sam, thanks for reaching out — when works for a quick call?Your proposal is ready. Questions before Thursday?Your renewal is coming up on March 1.

Architecture

How it fits together: CRM workflow, then Middleware or HTTP action, then SendiMessage API, then Customer, then CRM timeline.
  1. CRM workflowFlow, Workflows, Deluge, Power Automate…
  2. Middleware or HTTP actionApplies consent, builds the payload
  3. SendiMessage APIPOST /send-message with contact + owner ids
  4. CustomerMessage + natural reply
  5. CRM timelineWebhook events written back as activity

The API request

send message
curl -sS https://api.sendimessage.com/v1/send-message \
  -H "X-API-Key: $SENDIMESSAGE_KEY" \
  -H "X-API-Secret: $SENDIMESSAGE_SECRET" \
  -H "Content-Type: application/json" \
  -d '{
    "number": "+15555550123",
    "content": "Hi {{contact.first_name}}, your proposal is ready — any questions?",
    "status_callback": "https://your-endpoint.example.com/status?crm=your_crm&contact_id={{contact.id}}&owner_id=rep_789"
  }'
# → {
#   "status": "QUEUED",
#   "message_handle": "4e828182-a640-483f-bfe9-17ffcaa51d48",
#   "to": "+14155550123",
#   "service": null,
#   "is_outbound": true,
#   "error_message": null,
#   "date_sent": null
# }

Channel behavior and replies

Sales conversations feel native on iMessage where supported; SMS fallback keeps every contact reachable. iMessage delivery is available on supported messaging lines and destinations. Recipients without iMessage receive SMS when fallback is configured — never assume universal iMessage availability.

Metadata makes routing deterministic: the contact and owner ids you attach come back on every reply — no phone-number matching heuristics. No native CRM apps are claimed; each vendor guide shows the real mechanism.

Line setup, availability, and pricing

One line per team or brand; keep sales and support on separate lines for clean reply routing.

Line availability varies by country and channel. Run a preliminary availability check, and the team confirms final availability during onboarding review. Check preliminary availability →

Pricing is per active line, billed monthly, with usage per your agreement — confirmed for your countries and volume during managed onboarding. How pricing works →

Frequently asked questions

Which CRMs are supported?
Any CRM that can fire a webhook or HTTP request. Dedicated guides: Salesforce, HubSpot, Zoho, Pipedrive, Microsoft Dynamics 365, Freshsales, Monday, Odoo, Bitrix24.
Is there automatic CRM sync?
No — and deliberately so. Your middleware or automation platform writes events back, keeping your consent logic and data mapping in your control. The CRM brief explains the pattern.

Ready to build this?

Request the setup, or book an integration review and the team will map it to your systems.

Book an Integration Review