A pipeline you can trust

Every report is already right.

Synced tools hand you a call log that argues with your CRM: totals that do not match, records that lag an hour behind. WorkDial calls become Salesforce records the second they end, so your pipeline report is the call report. Nothing to reconcile.

Start your trial See it live

Salesforce · Twilio transport · WhatsApp · ValueText

managed package · in salesforce

Common question

What does it mean that WorkDial runs inside Salesforce?

WorkDial is a Salesforce-native CTI platform. It writes every call as a native Call__c object the instant it ends, with the transcript on Transcript__c, the AI sentiment score on Sentiment__c, and the recording reference on Recording__c. You report on them in the Salesforce report builder, trigger Flow from them directly, and govern them with the sharing and field-level security you already run. Nothing syncs in, so there is nothing to reconcile.

The objects

Four native objects. One system of record.

Every call produces four records inside your Salesforce org. They are standard native objects governed by your permissions, your flows, and your reports. No copy to sync, no second store to drift. For the VP who signs off on the number: this is why the pipeline report in your board deck is never a guess.

Call__c. The call record: direction, duration, outcome, and linked record. Exists from the moment the call ends. No manual entry.

Transcript__c. The full transcript, written to the record and queryable the moment transcription completes. Not a link to an external page.

Sentiment__c. The AI sentiment score, written directly to the record. Surfaceable in reports, dashboards, and flows without leaving Salesforce.

Recording__c. The recording reference. You choose where the audio lives: as native Salesforce Files in your own org, in your own Twilio, or in your own cloud storage. WorkDial keeps no copy of its own.

Native objects inherit your sharing rules, field-level security, and permission sets. No second data model to govern.

See the AI objects

Automation

Salesforce Flow triggers on call events directly.

Because Call__c is native, any Flow fires the moment a call ends. No webhook, no middleware.

Trigger on call outcome. Route a follow-up task to the rep when a call ends with a set outcome, using a standard record-triggered flow on Call__c.
Escalate on sentiment. Flag a record for manager review when Sentiment__c scores below a threshold.
Update the opportunity stage. Write a field on the related opportunity the moment a qualifying call is logged.

These are standard Salesforce flows on native objects. You write them in Flow Builder, in the org you already govern, with no new platform to learn.

A Salesforce Flow triggered by a Call__c record-changed event, open in Flow Builder — Flow Builder · record-triggered on Call__c

Security and permissions

Security inherits the Salesforce model you already run.

WorkDial adds no second permission model. Your existing Salesforce sharing rules and field-level security govern the call records and their linked objects. One audit surface, not two.

sharing rules

Your org's sharing rules apply to call records

A rep sees the calls they own. A manager sees their team's calls. An admin sees everything. No configuration in WorkDial: it follows the Salesforce rules already in place.

field-level security

Field-level security governs what each profile sees

Restrict the transcript or sentiment field to managers only. Hide the recording reference from profiles without review rights. Standard Salesforce FLS on native fields.

one audit surface

Audit and compliance stays inside Salesforce

Salesforce field history and event monitoring cover the call objects the same way they cover any other record. There is no second vendor store to vet at audit time. See the full security posture.

Reporting

Reports run in Salesforce, on your own data, with no export step.

Because call records are native objects, every Salesforce Reports and Dashboards feature applies to them without any configuration or data export. Your pipeline report is already the call report.

Build a calls-by-outcome report the same way you build any Salesforce report. Call__c is a standard object in the report builder.

Cross-object reports work out of the box. Relate call volume to opportunity stage, account tier, or lead source because the relationships are native.

Sentiment trend dashboards run on Sentiment__c without any third-party analytics tool. The data is already there.

Your reports show what happened, not what got typed. Every call logs itself. The gap between calls placed and calls in the CRM is zero.

Synced tools leave data behind a vendor boundary your reports cannot cross. WorkDial's data is already inside, so they can.

See the dialer

What it touches

A short, honest list.

WorkDial runs inside Salesforce, so this is a small grid, not a connector marketplace. Live tiles use the accent.

live

Salesforce

The platform WorkDial runs inside. Every call is a native object, governed by your flows and permissions.

live

Twilio

Bring your own account. It carries the call at carrier rates with no markup, and the recordings stay in the account you own.

live

WhatsApp voice through the same layer as your calls, routed and logged identically inside Salesforce.

live

ValueText

The Salesforce-native messaging layer from the same team. Together: the complete native stack.

The boundary

Call records live inside Salesforce. One line leaves the org.

Call records and app logic are native Salesforce objects in your org. Recordings go where you choose: Salesforce Files, your own Twilio, or your own storage. WorkDial keeps no copy of its own.

Your Salesforce Call__c Recording__c Transcript__c Sentiment__c

transport

Questions

Works inside Salesforce, answered

What does it mean that WorkDial works inside Salesforce?

WorkDial is a Salesforce-native CTI platform. It runs inside Salesforce rather than alongside it, so each call is written as a native Call__c object in your org the moment it ends, with the transcript on Transcript__c and sentiment on Sentiment__c. There is one system of record and nothing to sync in from a vendor cloud.

Which Salesforce objects does WorkDial write?

Native objects in your own org: Call__c holds the call record, Transcript__c the transcript, Sentiment__c the AI sentiment score, and Recording__c the recording reference. They are written in real time as the call happens, not mapped in from a vendor database afterward.

Does WorkDial store a copy of my call data?

No. WorkDial operates no external customer data store. Your call records are native Salesforce objects in your org, and you choose where the recording audio lives: native Salesforce Files in your own org, your own Twilio account, or your own cloud storage. WorkDial keeps no copy of its own.

Does Salesforce Flow trigger on WorkDial calls directly?

Yes. Because Call__c is a native object, a record-triggered Flow fires the moment a call ends, with no webhook or middleware in between. You can route a follow-up task on a call outcome, escalate when Sentiment__c scores below a threshold, or update the related opportunity, all in Flow Builder.

How is access to call records controlled?

By the Salesforce security model you already run. Sharing rules decide who sees which calls, field-level security governs the transcript, sentiment, and recording fields per profile, and Salesforce field history and event monitoring audit the call objects like any other record. WorkDial adds no second permission model.

Can I report on calls in Salesforce without an export?

Yes. Because the call records are native objects, Call__c is a standard object in the Salesforce report builder. You can build calls-by-outcome reports, relate call volume to opportunity stage or lead source in cross-object reports, and run sentiment dashboards on Sentiment__c with no third-party analytics tool.

How is this different from an integrated Salesforce CTI?

An integrated CTI runs the call in a vendor platform and syncs a copy into Salesforce afterward, so Salesforce holds a mirror of the truth. WorkDial writes the call as a native Salesforce object directly, so Salesforce holds the truth. This is the native versus integrated question at the center of the Salesforce CTI decision.

What does WorkDial cost?

WorkDial is per user, per month, published on the pricing page from Core at $28 per user per month billed annually. Telephony is bring your own Twilio at carrier cost with no markup. The 14-day Professional trial needs no card.

Get started

Run your calling inside Salesforce.

Start your trial See it live

4.97★ across 116 AppExchange reviews · from the team behind ValueText, the Salesforce-native messaging platform