In short
Source: Sales Surge, build order from this guideAs of: 16 November 2026
In this article
- What does a connected quote-to-close flow look like?
- How do you log CloudTalk calls in Pipedrive?
- What should you not log?
- How do you send a PandaDoc proposal from a Pipedrive deal?
- Which PandaDoc status moves a Pipedrive stage?
- When is Pipedrive Smart Docs enough?
- Which KPIs do you check every week?
- What our cases show about quote to close
- In what order do you set it up?
- Common mistakes and how to fix them
- Frequently asked questions
Between the first call and the signature, most teams lose time in the gaps. The call happened but the notes are in someone's head. The proposal was sent from a Word file with last year's prices. Nobody saw that the client opened it three times on Friday. This guide shows how we connect CloudTalk, PandaDoc and Pipedrive so those gaps close, which fields travel along at every step, what you should not log, and which numbers tell you where deals stall.
What does a connected quote-to-close flow look like?
A connected flow has six steps, and each step writes something into Pipedrive that the next step uses. This is the timeline we build.
| Step | Tool | What happens | Fields in Pipedrive |
|---|---|---|---|
| 1. Call | CloudTalk | The rep calls from the deal or the person | Activity type call, direction, duration, recording link |
| 2. Outcome | CloudTalk | The rep picks an outcome and writes two or three lines | Call outcome, note, next step |
| 3. Activity | Pipedrive | The outcome creates the next activity automatically | Due date, owner, activity type |
| 4. Proposal from template | PandaDoc | The rep creates the proposal from the deal | Product lines, deal value, contact person, organization |
| 5. Status sync | PandaDoc and Make.com | Sent, viewed, completed or declined comes back | Proposal status, date viewed, date signed |
| 6. Stage | Pipedrive | Sent and signed move the stage; viewed creates a call task | Stage, won or lost, lost reason |
The point of the timeline is that a manager can open any deal and see in one screen what was said, what was offered and what the client did with it. If that takes three tools and a phone call, the flow is not connected yet.
How do you log CloudTalk calls in Pipedrive?
Install the CloudTalk integration from the Pipedrive marketplace, map every CloudTalk agent to a Pipedrive user, and let CloudTalk create the activity. The rep then adds only what no integration can: a short note and the next step.
Connect and map users
Every agent in CloudTalk is linked to the matching Pipedrive user, so the call lands under the right owner.Keep the outcome list short
Five to eight outcomes, such as connected, voicemail, no answer, wrong number, call back and meeting booked. Long lists get ignored.Link the call to the deal
Calls attach to the person and to the open deal, so the deal history shows every conversation.Turn outcomes into activities
Call back creates a call for the agreed day; meeting booked creates the meeting and moves the deal to the next stage if that is your rule.
Recordings and AI summaries are useful for coaching and for picking up a deal from a colleague. Check your recording consent before you switch them on, and tell callers when calls are recorded. More on the platform side is on our CloudTalk page.
What should you not log?
Log what helps the next person act, not everything that happened. Too much logging makes the deal history unreadable and the activity numbers meaningless.
- The same call twice. Pick one route, the integration or a Make.com flow, and switch the other off.
- Unanswered calls as separate notes. The outcome no answer on the activity is enough.
- Full transcripts in the note field. Link to the recording or summary instead; the note is for the decision and the next step.
- Internal calls between colleagues. Exclude internal numbers, or they show up as client contact.
- Personal details that have nothing to do with the deal. They do not belong in a CRM and they make a GDPR request harder.
How do you send a PandaDoc proposal from a Pipedrive deal?
With the PandaDoc integration the rep opens the deal, picks a template and PandaDoc fills it from Pipedrive. The connection takes an afternoon. The templates take the real time.
Put prices in Pipedrive product lines
Products, quantities and discounts live on the deal. The proposal reads them, so the deal value and the proposal always match.Build a few templates, not twenty
One per type of offer is usually enough: a standard proposal, a renewal and an extension. Fields fill from the deal, person and organization.Check and send from the deal
The rep reviews the generated proposal, adds a personal line and sends it from PandaDoc. The deal shows the document.Let the status come back
PandaDoc reports sent, viewed, completed and declined. The integration or a Make.com flow writes it into fields on the deal.
Give templates one owner. When every rep edits a private copy, old prices end up in signed contracts. Our PandaDoc page covers what we set up on the PandaDoc side.
Which PandaDoc status moves a Pipedrive stage?
Only sent and completed should move a stage automatically. The other statuses create a task for a human, because they need a judgement.
| PandaDoc status | Moves the stage? | What happens in Pipedrive |
|---|---|---|
| Sent | Yes | Deal moves to Proposal sent, the sent date is stored |
| Viewed | No | The rep gets a task to call within one working day |
| Viewed, not signed after three to five days | No | Follow-up task with the proposal link and the last call note |
| Completed (signed) | Yes | Deal moves to Won or to the handover stage, onboarding tasks are created |
| Declined | No | The rep decides: new version, or lost with a required lost reason |
The flows for the follow-up tasks run in Make.com. The wider picture, with enrichment and outbound around it, is in the Pipedrive RevOps stack.
When is Pipedrive Smart Docs enough?
Smart Docs is often enough when you send roughly 10 to 40 proposals a month from a few fixed templates and you want everything inside Pipedrive. It fills templates with deal data, tracks views and handles e-signatures, and Premium already includes basic contracts and e-signatures.
PandaDoc earns its place when proposals are long and in your own house style, when you need pricing tables with options, a content library, internal approval steps before sending, or more advanced signing. That is a matter of document volume and complexity, not of team size. The costs of Smart Docs and the plans are in our Pipedrive pricing guide. If you are unsure, start with Smart Docs; moving later means rebuilding templates, not the whole flow.
Which KPIs do you check every week?
Five numbers show where deals stall between the first call and the signature. Look at them per rep and per stage, and look at the trend over several weeks.
| KPI | How you calculate it | What it tells you |
|---|---|---|
| Connect rate | Calls with outcome connected ÷ all outbound calls | Whether you reach people; low means wrong numbers or wrong call times |
| Call to proposal | Deals with a proposal ÷ deals with a first call | Whether calls qualify; low means proposals go to the wrong people or too late |
| Proposal view rate | Proposals viewed ÷ proposals sent | Whether the proposal lands; low means it arrives without context |
| Time to sign | Days from sent to completed, median | How long decisions take; rising means more people are involved |
| Stale proposals | Proposals open after 14 days ÷ all open proposals | How much pipeline is waiting without a next step |
We build these as a dashboard in Pipedrive or in a reporting layer next to it. The definitions behind them are in our RevOps KPI glossary.
What our cases show about quote to close
At BOOH Media, deals sat in email, Excel and WhatsApp, and every quote was built again from scratch in Word. We set up one pipeline with seven stages. The customer now signs the quote through a link, and the deal moves to Signed on its own. Pipedrive was live in 5 days, where 4 weeks were planned. BOOH does not use PandaDoc. The principle is the same as in this guide, one source for the data and a status that moves the deal. The full story is on the BOOH Media case page.
Looking for a CloudTalk case study: BOOH Media is about the proposal side, not about calling. We do not publish a case with call numbers yet. What we can show from our wider work is in our results: for example 18% higher conversion through fast follow-up at Ontslagrecht Juristen NL, and 20%+ more margin through automation at Evans Watson.
In what order do you set it up?
Weeks 1 and 2: Pipedrive
Stages that match buyer decisions, required fields, product lines with prices and a lost reason list.Week 3: CloudTalk
Users, outcomes, automatic logging, follow-up rules and a check after a week that each call appears exactly once.Weeks 4 and 5: PandaDoc
Templates, field mapping, status sync and a test run with a real deal on every template.Week 6: flows and training
Make.com flows for follow-up tasks, the KPI dashboard and training on the team's own deals, not on a demo account.
If your stages or product data are not in order, the first two weeks matter most. Proposals built on wrong product lines are wrong faster, and that is not progress.
Common mistakes and how to fix them
- Prices in the template. Move them to Pipedrive product lines, so there is one source.
- Every status moves a stage. Limit automatic moves to sent and signed; the rest becomes a task.
- No follow-up after viewed. A viewed proposal is the moment to call. Create the task automatically.
- Lost without a reason. Make the lost reason required, with a short list, so you can learn from it.
- Calls logged twice. One route only, and check it after a week.
- Training on demo data. Train on the team's own deals, in its own account.
Frequently asked questions
How do you log CloudTalk calls in Pipedrive automatically?
Install the CloudTalk integration from the Pipedrive marketplace and map each CloudTalk agent to a Pipedrive user. From then on every call is logged as an activity on the person and the open deal, with direction, duration, the outcome the rep picks and a link to the recording. The rep only adds a short note and the next step. Make sure nobody also logs calls by hand, or you count them twice.
Can you send a PandaDoc proposal straight from a Pipedrive deal?
Yes. With the PandaDoc integration a rep opens the deal, picks a template and PandaDoc fills it with the deal, person, organization and product lines from Pipedrive. The rep checks the proposal, sends it, and the status comes back to the deal. Keep prices in Pipedrive product lines rather than in the template, so the proposal and the deal value always match.
Which PandaDoc status should move a Pipedrive stage?
Only two statuses should move a stage automatically: sent moves the deal to proposal sent, and completed, meaning signed, moves it to won or to your handover stage. Viewed and declined should not move the stage on their own. Viewed creates a call task for the rep, and declined asks the rep to mark the deal lost with a reason, because a decline is sometimes a request for a new version.
Is Pipedrive Smart Docs enough, or do I need PandaDoc?
Smart Docs is often enough when you send roughly 10 to 40 proposals a month from a few fixed templates and you want everything inside Pipedrive. PandaDoc earns its place when proposals are long and branded, need pricing tables with options, content libraries, approval steps or more advanced signing flows. Start with Smart Docs if you are unsure; moving to PandaDoc later is a template job, not a rebuild.
Which quote-to-close KPIs should you check every week?
Check five numbers weekly: connect rate on calls, the share of first calls that lead to a proposal, proposal view rate, time from proposal sent to signature, and the share of proposals still open after fourteen days. Together they show where deals stall. Look at the trend per rep and per stage rather than at one week in isolation, because small teams have noisy weekly numbers.
How long does it take to connect CloudTalk, PandaDoc and Pipedrive?
Plan four to six weeks for the full flow. The first one or two weeks go to Pipedrive stages, fields and product lines. Calling with CloudTalk takes about a week including call outcomes and follow-up rules. PandaDoc takes a week or two, mostly for building and testing templates. The last week is for the Make.com flows in between and for training the team on its own deals.




