Trellus for Vanillasoft

Keep Vanillasoft routing in charge of the call list

Choose the Project, Team, and routed contacts your callers are meant to work. Trellus keeps that context attached and submits the selected Result Code and comments to the same contact after the attempt.

Vanillasoft already has Progressive and Preview Auto Dialing. Trellus is worth evaluating only when a different call block removes a real bottleneck.

Where Trellus works in Vanillasoft

Starts in: the supported caller or contact surface
Queue: Vanillasoft Project, Team, and routing
Phone choice: mapped label and exact phone record
After the call: selected Result Code and comments
Current limit: no direct Vanillasoft callback or Lead Status change
Start with the right question

Vanillasoft already owns the routing decision

Stay with Vanillasoft Auto Dialing

Use its Progressive or Preview path when the native next-contact pace, configured phone system, Result Code workflow, and Vanillasoft reporting already fit the team.

Review the Trellus path

Use Trellus when callers should keep the same Project, Team, contact, exact phone record, and Result Code workflow but need a different supported call block.

Do not blend the feature sets
Monitoring, Whisper, Break-in, Voicemail Drop, SmartCaller ID, Project-based Caller ID, and the native HUD are not Trellus claims on this page.
Where it works

The Vanillasoft queue context Trellus preserves

A routed Project is not an exported generic list. Its selection and result rules remain operationally important.

The supported caller or contact surface

Trellus works in supported Vanillasoft .net and .org caller environments. Vanillasoft admin pages are not calling surfaces.

One Project and Team

The selected Project refreshes its Team options. Trellus keeps routed-today mode and the current Project/Team boundary instead of mixing the whole account.

Routed contacts and filter priority

Last Result, Lead Status, reached-before, Last Called, and available FilterPriority controls narrow the contacts. Trellus loads the queue in pages of up to 200.

Mapped phone labels and exact identity

Mobile, work, home, and other labels vary by Project. Trellus retains the exact Vanillasoft PhoneNumberID used for the attempt and result.

Mapping is Project-specific
A Team that switches Projects with different labels or Result Codes should recheck the working setup before the next call block.
Rep workflow

Six steps, with Vanillasoft still in charge

01

Open the caller environment

Start in the Project the caller is meant to work rather than an admin page or an untested host.

02

Choose Project, Team, and routing boundary

Use routed-today mode and available priority controls when those rules matter to the team's operation.

03

Confirm phone mappings

Review mobile, work, home, and other fields for that Project and preserve the exact phone-record identity.

04

Load the supported contacts

Trellus keeps contact, Project, Team, status, result history, and exact phone context with each row.

05

Work the supported call block

Current mode, line allowance, caller number, and region remain live-account checks rather than promises on this page.

06

Submit the exact Result Code

Select the real Quick or Full Result Code and add useful comments. Vanillasoft decides what that code does next.

What returns

One acknowledged Vanillasoft result

The public contract is the selected Result Code and comments on the same contact, with Project, phone, call-time, and available Team/user context.

Exact contact
Project and Team
Exact PhoneNumberID
Selected Result Code
Useful comments
Optional transcript field
Vanillasoft owns the consequence
A Result Code may route, schedule, reassign, or change status according to Project configuration. Trellus does not claim a second callback, Lead Status, or task write.
Quick versus Full Result

A shortcut should not hide another prompt

Vanillasoft limits Quick Results to 20 codes and excludes codes that require a callback, date, reassignment, or data-collection prompt. Those more complex outcomes belong in the Full Result path.

Synthetic example
Maya works “Renewals — East,” enables routed-today mode, and confirms Mobile and Direct. One person answers. She selects the exact “Interested” Result Code and adds “Send security overview before the next call.” Vanillasoft accepts that result on the same contact.
Optional transcript field
If the Project has a Public Transcript Link field, Trellus can add the available link separately. If the field is missing, the successful Result Code stays successful and is not submitted again.
FAQ

Vanillasoft and Trellus

Does Vanillasoft already have an auto dialer?

Yes. Vanillasoft documents Progressive and Preview Auto Dialing. Trellus is a separate supported calling path around the routed contact context.

Can Trellus use a Project and Team as the queue boundary?

Yes. Trellus supports Project and Team selection, routed-today mode, filters, and pages of up to 200 contacts. Confirm the live order and available FilterPriority options in the Project before a call block.

What does Trellus save to Vanillasoft?

It submits the selected Result Code and comments with the exact contact, Project, phone, and call-time context. Full Results can also carry available current-user and Team context.

Does Trellus schedule a Vanillasoft callback?

No separate Trellus callback is created. A Result Code may trigger scheduling configured by a Vanillasoft admin, but that is Vanillasoft behavior.

Does Trellus change Lead Status?

Trellus does not select a separate Lead Status. A Project's Result Code configuration may change status, but that is not an additional Trellus update.

Can Trellus use Quick Results?

Yes, for eligible codes. Vanillasoft excludes codes requiring callbacks, dates, reassignment, or data prompts and limits the Quick Result list to 20.

Does Trellus include Monitoring, Whisper, or Voicemail Drop?

No. Vanillasoft provides those and related controls as part of its own phone offering.

Does Trellus write to a connected CRM?

No. This workflow submits the supported result to Vanillasoft; it does not create a separate result in a connected CRM.

Bring the real Vanillasoft Project to the review

Show us the Team, routing rule, phone labels, Result Codes, and required post-call state. We will separate Trellus behavior from Vanillasoft configuration.