Keep the Close Smart View. Choose the calling layer.
Close already has capable Power and Predictive Dialers. Trellus is an alternative for teams that want its power or parallel calling and coaching while keeping a supported Smart View, Lead, Contact, Call Activity, Outcome, and callback around the work.
Where Trellus works in Close
Watch Trellus call a Close Smart View
The verified walkthrough shows where Trellus enters the Close call block. Test the team's own Smart View, Outcomes, permissions, and callback behavior before rollout.
Verified Trellus walkthrough. It demonstrates the workflow, not universal support for every private Smart View or Outcome configuration.
The Close surfaces Trellus uses
The audience, selected Contact, and active call all need exact Close context.
Keep the saved Lead filter, sharing, sort, and paging context that defines the worklist.
Use Contact-focused saved filters where the current query and record context resolve.
Resolve a specific Contact, Lead, company, title, and phone choice for a supported one-off call.
When Close places the call, the active Call Activity and dialed number are stronger evidence than an unrelated Lead page in the background.
Close filters are flexible. The exact private or complex Smart View a team plans to call still needs a synthetic rollout test.
The Smart View remains the audience
Open the supported Smart View
Use the Lead or Contact filter, sharing, and sort the team already maintains in Close.
Review the Contact and number
Keep the resolved Contact, Lead, title, company, and available phone values with the call.
Choose the calling layer
Use Close's native dialers when they fit, or Trellus power or eligible parallel calling when the team wants the Trellus workflow.
Return the result to Close
Create the supported Call Activity, apply a matching active Outcome, and create a callback Task when needed.
Close already solves calling
Close's Power Dialer works through a Smart View, and its Predictive Dialer can dial multiple numbers and route an answer to a rep. For many Close teams, that is the right choice. Trellus matters when the buyer specifically wants the Trellus calling and coaching experience without abandoning the supported Close audience.
Choose Close's dialers when
- You want the native Close calling and administration experience
- Close's Power or Predictive workflow already fits the team
- Keeping the calling stack entirely in Close is the deciding requirement
Consider Trellus when
- The Smart View should stay the audience
- The team wants Trellus power or eligible parallel calling
- Trellus coaching and the reviewed Close write-back fit the operating model
A Smart View is not a static export
Records can enter or leave as ownership, activity, status, Tasks, and other fields change. Trellus keeps the supported saved-view and paging context, and can surface newly eligible top records without restarting from a stale spreadsheet.
Jordan opens “Renewals — local time open.” A new Lead becomes eligible during the block; another leaves after a callback Task changes its follow-up state. The queue stays tied to the Smart View rather than the initial screen.
Use the exact Smart View. Flexible or private search shapes should not inherit a blanket promise from a synthetic example.
Keep Call Activity and Outcome state separate
A truthful result model matters more than a generic “syncs to Close” claim.
The Call Activity may save while a selected Outcome does not match an active Close Call Outcome. Trellus reports that outcome failure and does not pretend it was applied or duplicate the accurate Activity.
Return follow-up as a Close Task
With the required Lead, current Close user, due time, authenticated session, and record access, Trellus can create a Lead-linked Trellus Callback Task and later surface it as dialable work.
If the Lead, current user, due time, permission, or authenticated Close context is missing, Trellus reports the failure instead of producing an unassigned reminder.
Close CRM and Trellus
Where does Trellus work in Close?
Trellus works on supported Lead or Contact Smart Views and supported Lead or Contact records. During native Close calls, it uses the active call context rather than guessing from an unrelated page.
Doesn't Close already have a power or multi-line dialer?
Yes. Close offers Power and Predictive Dialers. Use them when the native Close workflow fits. Trellus is an alternative for teams that want its power or parallel calling and coaching around a supported Close audience.
Can Trellus dial a Close Smart View?
Yes, on supported Lead or Contact Smart Views. The exact saved query, sort, sharing, paging, and dynamic membership should be verified on the view the team plans to use.
What does Trellus log to Close?
Trellus can create a supported Close Call Activity with the Contact, Lead, number, duration, note or summary, dial mode, and transcript link, then attempt to apply a matching active Call Outcome.
What happens if the Outcome does not match?
The Call Activity may still be accurate and saved. Trellus reports the Outcome as a partial failure and does not pretend it was applied.
Can Trellus create callbacks in Close?
Yes, when the Lead, current user, due time, authentication, permissions, and record access resolve. The callback is a Lead-linked Trellus Callback Task that can later return as dialable work.
Does Trellus work with every Close Smart View?
No blanket claim is appropriate. Close supports flexible filters, so the exact Smart View needs a current synthetic test before team rollout.
Compare one real Close call block
Bring the Smart View, Outcomes, phones, permissions, callbacks, and coaching requirements your reps use. Evaluate Close and Trellus against the same work.
