Call the Unify tasks your reps already own
Start from the filtered Tasks dashboard. Trellus keeps the exact phone task attached to the Person, Sequence, step, and phone record, then completes that task with the supported note when Unify accepts the update.
Where Trellus works in Unify
Watch Trellus work the Unify Tasks list
The recording shows where Trellus enters the current Unify task workflow. Validate your own filters, assignment rules, phone coverage, and accepted result before production use.
Verified Trellus walkthrough for Unify. It does not borrow features from Unify Dialer beta or turn one-off calls into task writes.
The Unify surfaces and boundaries Trellus uses
Unify decides who belongs in the task queue and why. Trellus keeps that reason attached while the rep works the calls.
Trellus reuses the current Unify request's assignment, task type, priority, Sequence, status, search, sort, and grouping boundary rather than inventing another audience.
The supported row retains the exact task and Person IDs, company, Sequence, step, LinkedIn profile, domain, and available phone records.
Rich phone details are requested for callable tasks assigned to the signed-in Unify user. Tasks owned by another rep remain a visible assignment boundary.
A supported Person context can expose an individual call, but it does not receive the task completion and note promised for an actual phone task.
If richer phone lookup fails, an existing mobile value may remain available. Trellus does not manufacture a verified phone number when Unify has none.
Keep the task reason attached through the call
Filter the Unify Tasks view
Choose the assignment, phone-task type, priority, Sequence, status, search, sort, and grouping the rep can explain.
Review ownership and phone status
A callable row must be a non-completed PHONE_CALL task. Confirm the current owner and the exact phone record before starting.
Work the Trellus call block
The active conversation keeps the Unify Person, Sequence, step, task, phone label, and available linked-record context attached.
Add the supported result
Choose the disposition and add a useful summary. Include the Trellus transcript link when one exists.
Confirm the exact task update
Trellus sets that task to COMPLETED with the note and waits for an accepted Unify response before reporting success.
Unify Dialer beta or Trellus?
Start with Unify Dialer beta
Use the native option when its current numbers, region, controls, usage model, and task result already meet the team's needs. Fewer tools is a real advantage when the workflow is already solved.
Review the Trellus path
Use Trellus when the team specifically wants its supported calling mode while preserving the current Unify Tasks boundary and an acknowledged task-completion note.
Unify's pricing matrix and newer support article describe Dialer beta access differently. Confirm the buyer's actual workspace and contract before comparing plans or cost.
One exact task, one acknowledged update
For the supported task path, the result is a task status plus task note. It is not presented as a new activity type or an arbitrary Person note.
A one-off Person call gets no task write. SKIPPED does not prove Sequence unenrollment. No Trellus-created Unify callback or contact-level DNC update is claimed.
A pricing signal stays a pricing task
Priya's team has a Play that turns repeated pricing-page visits into a Sequence. Step three is a manual phone task. Her dashboard is filtered to her name, PHONE_CALL, high priority, READY, and the “Pricing revisit” Sequence.
The live answer retains the Person, company, Sequence, Step 3, and valid primary mobile. Priya chooses Interested and adds “Send security overview before Friday.” The exact task is accepted as COMPLETED with disposition, summary, and transcript link.
If Priya later calls a Person with no task, this page does not promise the same Unify note. She should use the team's native one-off Task process when a scheduled follow-up is required.
Unify and Trellus
Does Unify have its own dialer?
Yes. Unify lists Dialer beta. Its public pricing matrix and newer support article describe plan access differently, so current eligibility should be confirmed in the buyer's own workspace.
Where does Trellus work in Unify?
The reviewed workflow starts from the current Unify Tasks dashboard and supported task or Person detail context in the web app.
Which Unify tasks can Trellus call?
The reviewed adapter marks non-completed PHONE_CALL tasks as callable, preserves assignment, and requests richer phone records for eligible tasks owned by the current user.
What does Trellus write back to Unify?
For the supported task path, Trellus can set the exact task to COMPLETED with a note containing disposition, summary, and an available transcript link after Unify accepts the update.
Does a one-off Person call complete a task?
No. The reviewed one-off call path does not receive the same Unify task completion and note.
Can Trellus create a callback task in Unify?
No Trellus-created Unify callback is part of this claim set. Use Unify's native one-off Task workflow when a scheduled follow-up is required.
Does “skip” remove the Person from the Sequence?
No such promise is made. The reviewed action sets the selected task to SKIPPED; it does not prove full Sequence unenrollment.
Does Trellus update Salesforce or HubSpot from Unify?
Not by this page's evidence. Linked record context can be retained, but the remote CRM activity, fields, permissions, and acknowledgements need a separate end-to-end test.
Bring one real Unify task view to the review
We will separate what Unify already owns, what Trellus can preserve, and which downstream results still need a sandbox call.
