Calls and SMS, in your CRM.
OAuth-connect HubSpot, Salesforce, or Pipedrive once. Calls and SMS log automatically as activities on the right contact. Click-to-call from any phone field in the CRM. Inbound caller-ID lookup overlays the contact card on the agent's phone before pickup. Available on Team Pro.
CRM integrations on Kelir.
Kelir CRM integrations connect the call-and-message activity on your team's cellular eSIM lines to HubSpot, Salesforce, or Pipedrive — three integrations available at launch on Team Pro. The integration runs bidirectionally: calls and SMS logged automatically into the CRM as activities; click-to-call from CRM phone fields placed through the user's Kelir line; caller-ID lookup runs on inbound to overlay contact context.
Setup is OAuth-based. Admin connects the CRM at app.kelir.io → Integrations, authorizes Kelir against the CRM's OAuth scope (typically "calls", "messages", "contacts" read/write), and the integration is live. Per-user mapping is automatic for users whose CRM email matches their Kelir login; admins can override mappings for users whose emails differ.
What logs automatically: every call (inbound and outbound) appears as a Call activity on the matched contact's record, with timestamp, duration, direction, and a deep-link to the recording (if recording was enabled and stored). Every SMS thread appears as Message activities, with the message text, direction, and timestamp. Voicemail logs as a special activity type with the transcript text inline.
Click-to-call works from any phone field in the CRM that exposes the standard tel: link or the CRM's native click-to-call surface (HubSpot: Sales tab call button; Salesforce: Lightning Voice; Pipedrive: deal-page call icon). Click triggers an outbound call from the user's Kelir line — their phone dials the number on cellular VoLTE. The call logs back to the CRM record automatically when complete.
Caller-ID lookup is the inbound side. When a call comes in, Kelir queries the CRM by the caller's number, finds the matching contact (if one exists), and overlays the contact card on the agent's phone — name, company, last interaction, deal stage. Pre-pickup context for the agent. The lookup happens in <100ms before the line rings.
RingCentral, Dialpad, 8x8, Vonage Business, and Nextiva all ship CRM integrations of varying depth. Functionally similar — auto-logging, click-to-call, caller-ID overlay. The difference on Kelir: the click-to-call destination is a real cellular eSIM line that rings on the user's actual phone via the native dialer, and the caller-ID lookup overlay reaches the user's phone before the cellular ring lands.
Setup walkthrough.
Configured from Admin portal at app.kelir.io. The setup below assumes a working Kelir account and an active eSIM.
- 1
Open app.kelir.io as an admin and navigate to Integrations.
- 2
Pick the CRM: HubSpot, Salesforce, or Pipedrive. Click Connect.
- 3
Authorize via OAuth — Kelir requests access to calls, messages, and contacts (read/write). Approve in the CRM's OAuth screen.
- 4
User mapping happens automatically for users whose CRM email matches their Kelir login. Override mappings for users whose emails differ from the user mapping screen.
- 5
Pick what to log: calls (default on), SMS (default on), voicemails (default on). Optionally exclude internal calls between teammates.
- 6
Configure the recording deep-link behavior — whether the call activity in the CRM links to the recording (Team Pro) or just the call metadata.
- 7
Enable caller-ID lookup on inbound — when a call rings, Kelir queries the CRM by phone, surfaces the contact card on the agent's mobile app pre-ring. Toggleable per user (some users may not want auto-lookup on personal calls).
- 8
Test: place a click-to-call from a contact in the CRM; verify the call rings on the user's Kelir eSIM line; verify the activity logs back when complete.
- 9
Roll out to the team. Per-user opt-in is configurable for users who want to control which calls log to the shared CRM.
Where crm integrations earns its keep.
Sales rep — auto-logged demo calls
Rep clicks call from the prospect's Salesforce record; their Kelir eSIM dials the number; recording starts (if enabled); call activity logs to the deal at completion with duration and recording link. Rep doesn't manually log anything.
Inbound with full context
Inbound from a known contact rings — agent's phone shows the standard cellular caller-ID plus the Kelir mobile app overlays the CRM contact card with name, company, last interaction, and deal stage. Agent picks up knowing exactly who's calling.
SMS thread visible to the team
Two-way SMS thread with a customer logs as message activities on the contact record. Other team members reviewing the deal see the conversation history without forwarding from the original rep.
Voicemail with transcript on the deal
Customer leaves voicemail. Activity logs with audio link and transcript inline. Whoever opens the deal sees the message text immediately, decides whether to call back tonight or assign to someone.
Pipeline-correlated activity report
Admin pulls the Activity report — call counts by deal stage, average call duration in won deals vs lost. Useful for sales coaching and pipeline-velocity analysis.
The same feature.A real cellular line.
CRM integrations are universal in mid-tier UCaaS. The integration depth and setup friction vary; functionally similar across vendors. Kelir's distinctions sit in delivery and plan tier.
- Click-to-call dials from a real cellular eSIM line on the user's actual phone — not a softphone session in the CRM browser tab.
- Inbound caller-ID lookup overlays the contact card on the user's Kelir mobile app pre-ring (sub-100ms), before the cellular line rings.
- Auto-logged activities link to recordings (when enabled) — the recording is stored in Kelir's encrypted storage, the CRM activity has the deep-link.
- OAuth setup at the org level once; user mapping is automatic by email match.
- HubSpot, Salesforce, and Pipedrive at launch — broader CRM coverage on the Phase 3 public API roadmap.
- On Team Pro at $39.99/seat — the same plan tier most softphone competitors require for comparable CRM depth.
Common questions
HubSpot, Salesforce, and Pipedrive at launch on Team Pro. These cover the majority of SMB and mid-market CRM deployments. Additional CRMs (Zoho, Microsoft Dynamics, Copper, etc.) are on the Phase 3 public-API roadmap — once the public API ships, any CRM that supports OAuth + webhooks can integrate.
No. CRM integrations are a Team Pro feature ($39.99/seat). Team Starter ($29.99/seat) supports CSV export of call data — useful for batch import to a CRM, but not the live integration. The live auto-logging, click-to-call, and caller-ID lookup require Pro.
Each call (inbound or outbound) generates a Call activity on the matched contact's record at call end. The activity includes timestamp, direction (inbound/outbound), duration, the user who handled the call, and a deep-link to the recording if recording was enabled. Failed-to-match calls (number not in the CRM) log to a generic Kelir Activity feed for review.
On standard CRM surfaces, yes — HubSpot Sales tab call button, Salesforce Lightning Voice click-to-dial, Pipedrive deal-page call icon. Some custom field configurations may require the admin to map the field to the click-to-call action.
Inbound rings — Kelir queries the connected CRM by the caller's number. If a contact matches, the Kelir mobile app shows an overlay card on the agent's phone before the line rings: contact name, company, last interaction date, current deal stage (if applicable), and a link to the full record. Sub-100ms — pre-ring context for the agent.
Yes. Per-user opt-out is supported — users can toggle CRM logging off for personal-style calls they don't want logged to the shared CRM. Default is logging on; opt-out is per-call or session-based.