Call the Salesforce view your team actually works
Turn a supported Lightning report, object list view, or due call-Task list into a Trellus power or parallel session. Keep the resolved record with the call, then return the activity and callback to Salesforce.
Where Trellus works in Salesforce
See Trellus work from Salesforce
The walkthrough shows Trellus entering the rep's Salesforce report and list-view workflow. The exact report type, fields, permissions, required fields, and validation rules still belong in the rollout check.
The Salesforce surfaces Trellus uses
The page names the actual worklist instead of promising a vague CRM sync.
Use supported report rows as the calling audience while retaining the available report columns and resolved Salesforce record context.
Start from supported Lightning list views for Contacts, Leads, Accounts, Opportunities, or an approved object workflow when the visible phone and record fields resolve.
Use supported native call Tasks as the worklist and keep the exact Task identity available for completion after the call result is saved.
Make a supported one-off call from an exact record context. Trellus does not claim that every Salesforce object or page layout is a calling surface.
Keep the territory, stage, and ownership logic intact
A Salesforce admin has often done the important audience work before a rep opens a call block. The report owns the territory. The list view owns the stage. The Task list says what is due. Trellus uses that supported surface rather than rebuilding the audience elsewhere.
Priya opens a report named Northeast renewals — 30 days. It contains Contacts and related Accounts, the standard Phone field, and a custom Direct Line field. Trellus presents the mapped phone choices and works the eligible rows. After a connected call, a Salesforce Task carries the selected disposition, summary, and available Trellus transcript or recording link. A requested callback returns as a dated Task on the same person and permitted related record.
The report must expose resolvable records and eligible phone data. Summary-only layouts, inaccessible fields, unsupported relationship combinations, and custom validation can change or block the result.
From Salesforce worklist to finished Activity
Open the worklist
Start from a supported report, Lightning list view, due call-Task list, or exact approved record workflow.
Confirm phone mapping
Use standard phone fields and approved custom phone fields, exclude fax fields, and respect mapped DNC data.
Choose power or parallel dialing
Call one record at a time or run an eligible Trellus parallel session while retaining the Salesforce record context.
Return the activity
Save the call Task with the available disposition and summary, then create a record-linked callback when needed.
Salesforce has a native calling path
Sales Engagement provides cadences and a prioritized Work Queue, and Salesforce recommends Salesforce Voice for teams that want telephony owned inside Salesforce.
Choose Sales Engagement with Salesforce Voice when the team wants Salesforce to own the cadence, calling administration, telephony, and activity workflow end to end. Salesforce's older Sales Dialer is scheduled for retirement.
Consider Trellus when the team wants the Trellus calling and coaching experience while keeping a supported Salesforce report, list view, or due call-Task list as the source worklist.
The value is not “Salesforce cannot dial.” The value is choosing the calling workflow without abandoning the Salesforce view.
Sales Engagement overview · Salesforce Voice with Sales Engagement · Sales Dialer status
The person and related business record have different jobs
Salesforce uses person and related-record associations on Activities. Trellus keeps that distinction visible.
Contacts and Leads resolve as people. Accounts, Opportunities, and selected custom-object context can be retained when Salesforce permits the relationship. The person called and the related business record are not interchangeable.
Lead associations, sharing rules, required fields, custom objects, and org configuration can change which combinations Salesforce accepts. The rollout test should use the same objects and fields reps will use in production.
What Trellus saves to Salesforce
For a supported resolved call, Trellus creates an Activity record that stays in Salesforce.
If Salesforce rejects an optional field such as CallDisposition or a related-record association, Trellus can retry without that optional field when the remaining Activity is still accurate. Writes that cannot be completed are reported; a rejected field is not described as synchronized.
Return follow-up to the same Salesforce context
When somebody asks for Tuesday afternoon, Trellus can create a dated Salesforce callback Task with the available summary, person association, and allowed related record.
Activity permissions, ownership, required fields, validation rules, customized Task statuses, and valid person/related-record combinations can block or alter the callback. Trellus reports the failed write instead of creating an ownerless private reminder.
Salesforce and Trellus
Where does Trellus work in Salesforce?
Trellus works from supported Lightning reports, object list views, due call-Task lists, and selected exact record workflows. Support is workflow-specific rather than a promise about every Salesforce screen.
Can Trellus dial from a Salesforce report?
Yes, when the supported report exposes resolvable rows and mapped phone columns. Trellus removes duplicate numbers, excludes fax fields, and carries the available record context into the call.
Can Trellus use a Salesforce list view or Task list?
Yes, on supported Lightning surfaces. The current list or due call Tasks can remain the worklist while Trellus retains resolved record and Task identity.
Which Salesforce objects does Trellus support?
The implementation includes Contacts, Leads, Accounts, Opportunities, and selected custom-object context. Exact support depends on the surface, fields, associations, permissions, and org configuration.
What does Trellus log in Salesforce?
A supported call can create a Task with a subject, summary or available Trellus transcript/recording link, CallDisposition when Salesforce accepts it, and valid person or related-record associations.
Can Trellus create a Salesforce callback Task?
Yes, when the owner, person, due date, permissions, required fields, status, and related-record association resolve. Otherwise the failed write is reported.
Will this work with our validation rules?
Not automatically. Required fields, validation rules, custom statuses, and Activity permissions differ across orgs. Test your production-shaped workflow with synthetic records before rollout.
Try Trellus on one Salesforce worklist
Bring the actual report, fields, objects, permissions, validation rules, and callback behavior your team uses. We will show exactly what returns to Salesforce.
