Call steps become a campaign
Pharo pulls the call tasks due today out of Outreach sequences and dials them in one sitting instead of one at a time.
Pharo + OutreachIn build
This is a pairing, not a migration. Outreach keeps the cadence, the email and the reporting your team already runs on; Pharo takes the call step, dials it across several lines at once, and hands the task back completed with its disposition, recording and summary. Nothing about the sequence changes.
Pharo pulls the call tasks due today out of Outreach sequences and dials them in one sitting instead of one at a time.
Dispositions, recordings and call summaries return to the Outreach task and the prospect record, so the sequence advances on its own.
Asked about ramp time for new SDRs. Wants to see it on their own list.
Set from the call disposition.
Outreach stays the system your reporting points at. Pharo reads and writes the fields you already have rather than asking for new ones.
That is what this connector is for, and it is in build rather than shipped. The design is a pairing rather than a migration: Outreach keeps the cadence, the email and the reporting, and Pharo takes the call step and returns the task completed with its disposition, recording and summary.
No, and the page would be a different page if you did. Outreach stays the system your reporting points at. Nothing about the sequence changes except that the call step is dialed across several lines instead of one at a time.
A parallel dialer opens several outbound lines at once for a single rep and connects that rep to whichever one a person picks up, so the unanswered numbers and voicemails are cleared without anyone sitting through them. There is a longer explanation, including where it goes wrong, in what is a parallel dialer.
Up to 2 on Starter, 4 on Pro and 8 + on Enterprise — the count is on the pricing page. It is a plan setting rather than a dial to turn up freely, because abandonment exposure rises with lines: more lines open per rep means more calls answered with nobody to hand them to.
The orchestration layer runs on Nango, so most of the long tail is configuration rather than engineering. If the one you need is not here, tell us which and it moves up the queue.
Get started
Ready to eliminate dead dials and marked-up credits?
Seven days, 1,000 credits, no credit card. Or thirty minutes with the two people who would do the work.