PandaDoc Manual Contracting
About PandaDoc
PandaDoc Login: https://app.pandadoc.com/
As of June 2026:
- Sales & GA: Use support@clarivoy.com login
- Ops: Use datateam@clarivoy.com login
Service Order Templates
- Original copies are found in Dropbox here: https://www.dropbox.com/scl/fo/81nhuf4jddxloruypo686/AEXp9Gv5nE5eNQj3CpHXxWE?rlkey=xo26mwyq02tteaxpy8lcu0o5y&st=ewakipy8&dl=0
- PandaDoc versions are found here:
https://app.pandadoc.com/a/#/templates-next - All new Service Orders must be mapped in order for data to flow correctly between Pandadoc and Monday. To request a Pandadoc Template to be mapped, open an Ops Request.
Mapping Service Order Templates
Service Order Templates can both:
- Receive information from a Monday Board (typically Sales Pipeline) via Monday's Pandadoc integration
- Send information back to a Monday Board (Sales Pipeline via the Make.com Scenario PandaDoc - Document state changed)
Mapping a Template to Receive Information from a Monday board
- Open the updates of any item on the Monday board.
- Go to the Pandadoc Items tab (if it is missing, click the + sign at the end of the tabs list to add it).
- In the top right corner, click the gear icon (NOT the one next to the word Settings).
- Click Variables.
- The Variables list shows all fields on the Monday board and sample data for the item you have selected.
- Hover over a variable name. On the right side, click the
icon to copy the variable name to the clipboard. - Paste that variable in the Pandadoc template where you want the information to populate.
- Now, when a user uses the Pandadoc Items tab and selects your template, the variables you pasted into the document will be replaced with the actual item data from the Monday board.
Mapping a Template to Send Information back to Sales Pipeline
- In a Pandadoc Template, insert a text field.
- Click on the text field.
- Click on the Properties icon
. The “Text Field” properties box opens on the right side of the page. - Change the Field ID to one of the following:
| Pandadoc Field ID | Mapped to Monday board column | Mapped to 2nd Monday Board column |
|---|---|---|
| POC Name | Primary Contact First Name | Signer First Name* |
| Primary Contact Last Name | Signer Last Name* | |
| POC Title | Primary Contact Title | |
| POC Phone | Primary Contact Phone | |
| POC Email | Primary Contact Email Address | Signer Email* |
| OC Name | Onboarding Name | |
| OC Title | Onboarding Title | |
| OC Phone | Onboarding Phone | |
| OC Email | Onboarding Email | |
| BC Name | AP Contact Name | |
| BC Title | AP Contact Title | |
| BC Phone | AP Contact Phone | |
| BC Email | AP Email Address |
*Signer fields are only populated if they are blank
To request mapping to another Monday board other than Sales Pipeline, open an Ops Request.
Sending PandaDocs
New Sales Process via Hubspot
As of August 2026, all PandaDoc contracts are sent by the Sales team from within Hubspot. See Sales: New Business Processes
OLD Sales Pipeline PandaDoc process
These processes are no longer used as of August 2026. All PandaDoc contracts should be sent by the Sales team from within HubSpot.
Ready for Contract
- On the Sales Pipeline board, find the item
- Fill in the following required columns:
- Company Name *This is the auto group name (if a standalone store not part of an auto group, use the store name)
- Signer First Name *This is the person you are sending the contract to.
- Signer Last Name
- Signer Email
- Signer Job Title
- Subscription
- Referral Source
- Rooftop Count
- Set the Status to Ready for Contract
- Click into the conversation updates
- Click on the PandaDoc Items tab
- Click Create New Document
- Select the appropriate service order template
- Click the Add 1 item button at the bottom
- Fill out Client contact info at the top (under “Role: Client”)
- The rest of the contacts are already pre-filled
- Click the Continue button
- The contract is created and opened in a new window
- Rename the contract by changing the name in the top left - add Service Order to the end of the name
- Click the Send button (top right)
- Click Send via email
- 🚦 A Make.com scenario will change the Status to Contract Sent when the PandaDoc is sent
Contract Sent - Sales Handoff Survey
- When Status changes to Contract Sent,
- 🚨 Automation will fill in the Link column = a link to this item
- 🚨 When Link is filled in, if signup type=PandaDoc, an Email notification is sent to the Lead Assignee (Sales) with a link to the SuperForm Sales Handoff Form
- Lead Assignee (Sales) is to fill out the Sales Handoff SuperForm using the link they were emailed.
- 🚨 SuperForm will update specific fields on the item using the survey answers:
- Signer Type
- Onboarding Type
- Signer Persona
- Onboarding Persona
- Enterprise
- Expansion
- TBD - ✴️ When any of these fields are updated, a Zapier Zap will update the corresponding Rocketlane Project Fields.
- 🚨 SuperForm will update specific fields on the item using the survey answers:
Signed by all Parties
- Once the contract has been signed by both parties, PandaDoc sends notifications to:
- VP of Sales
- VP of Customer Success
- Director of Customer Success
- Controller
- Data Team
- 🚦 A Make.com scenario will:
- 🚦 Fill in all applicable fields on the Sales Pipeline board item, including:
- Primary Contact First Name
- Primary Contact Last Name
- Primary Contact Title
- Primary Contact Phone
- Primary Contact Email Address
- Onboarding Contact Name
- Onboarding Contact Title
- Onboarding Contact Phone
- Onboarding Contact Email
- AP Contact Name
- AP Contact Title
- AP Contact Phone
- AP Contact Email
- 🚦 Change the Status of the Sales Pipeline board item according to the below rules. Certain fields are required for items to go into Rocketlane:
• Property ID
• Domain
• Primary Contact Email- If all required fields are filled in, status is set to Rocketlane and the Rocketlane project is created.
- If all required fields are NOT filled in, status is set to Contract Signed - Needs CS Review and the item moves up to the top group on the page (for visibility by CS and Ops)
- 🚦 Fill in all applicable fields on the Sales Pipeline board item, including:
Customer Does Not Sign In Pandadoc (Manual Process)
If a customer prints and signs a Pandadoc and returns a PDF to you instead of signing it in Pandadoc, here is the process to follow. These are the automated steps that Make.com would normally perform, but cannot if the dealer signed a hard copy.
-
Check the contract for Contact Information provided by the dealer. Update these fields on the Sales Pipeline board item:
- Signer First Name *If not filled in, or the signer was someone different than you sent it to
- Signer Last Name
- Signer Email
- Signer Job Title
- Primary Contact First Name
- Primary Contact Last Name
- Primary Contact Email Address
- Primary Contact Phone
- AP Contact Name *REQUIRED
- AP Contact Title
- AP Contact Phone
- AP Contact Email Address *REQUIRED
- Onboarding Name *This would be a Technical Contact who can help with Onboarding data access
- Onboarding Title
- Onboarding Email
- Onboarding Phone
- Create an item update and upload the signed contract. Tag the Controller in the update so they have a copy of the contract.
- Set the Status to Rocketlane
Client and VP of Sales sign the contract
- Client receives an email that they need to sign the contract
- Client clicks the link (“Open the Document”) in their email to sign the contract
- Client fills in Primary Contact, Tech Contact, Billing Contact and signs at the bottom
- VP of Sales gets an email that the contract has been signed
- VP of Sales receives an email that they need to sign the contract
- VP of Sales clicks the link (“Open the Document”) in their email to sign the contract
- VP of Sales reviews the contract and signs at the bottom
Resending a Pandadoc
Correcting a Dealer's Email Address
See Correcting a Dealer's Email Address in PandaDoc
Changing a Signer
See Changing a Signer In PandaDoc
Sales Pipeline: Sending to Rocketlane or Properties Board
Sending to Rocketlane or Properties Board
-
SENDING TO ROCKETLANE OR PROPERTIES BOARD: The process varies for single stores or groups:
-
For single stores OR the 1st rooftop in a Group signup: set the status to Rocketlane
- When status is set to Rocketlane, this triggers a Zapier integration to:
- ✴️ Create the Rocketlane account and project and fills in the project id column on the Sale Pipeline board with the Rocketlane Project ID
- 🚨 When project id is filled in, if status=Rocketlane, Monday automations will:
Set the Status to Send to Properties Board.
- 🚨 When project id is filled in, if status=Rocketlane, Monday automations will:
- ✴️ Create the Rocketlane account and project and fills in the project id column on the Sale Pipeline board with the Rocketlane Project ID
- When status is set to Rocketlane, this triggers a Zapier integration to:
-
For subsequent stores in a Group signup: set the status to Send to Properties Board.
- See automations below based on the subscription.
-
For single stores OR the 1st rooftop in a Group signup: set the status to Rocketlane
At this point, the automations differ based on the Subscription:
MTSA Paid Subscriptions
- 🚨 When Status is set to Rocketlane, if Subscription is MTSA Pro or MTSA Pro+, a SuperMail automation will send a welcome email addressed to the Primary Contact, with CCs to Onboarding Contact and Signer Contact (if they are different).
-
When Status is set to Send to Properties board,
- 🚨 A Monday Workflow will search for an existing Client and if one does not exist, created it. The client will be linked in the DON'T MODIFY - Clarivoy Clients (Auto Group/Company) column. For the full process, see Creating New Clients Board Items: Automatic Creation.
- 🚨 A Monday Workflow will create an item on the Clarivoy Properties board then set the status to Won.
- 🚨 CS Specialist receives a notification when a new item is created on the Clarivoy Properties (Rooftops) board
Source Reports
- When Status is set to Send to Properties board
- 🚨 A Monday Workflow will search for an existing Client and if one does not exist, created it. The client will be linked in the DON'T MODIFY - Clarivoy Clients (Auto Group/Company) column. For the full process, see Creating New Clients Board Items: Automatic Creation.
- 🚨 A Monday Workflow will create an item on the MTSA Source Reports Properties board then set the status to Won.
- 🚦 When Status is set to Won, if Third Party Data Sharing Approval=Yes, Make.com scenario will create a linked item on the Third Party Data Sharing board with the appropriate approvals filled in based on the sources selected.
- If there is an issue creating the TPDS board item (such as blank Property ID or no sources), Make will email cusotmersuccess and datateam.
CDP Lite or TV
- Set the Status to Send to Properties Board.
- 🚨 When Status is set to Send to Properties Board, if TV Rate or CDP Rate are filled in:
- 🚨 A Monday Workflow will search for an existing Client and if one does not exist, created it. The client will be linked in the DON'T MODIFY - Clarivoy Clients (Auto Group/Company) column. For the full process, see Creating New Clients Board Items: Automatic Creation.
-
🚨 Monday automations will create an item on the Clarivoy Properties board then set the status to Won.
- 🚨 CS Specialist receives a notification when a new item is created on the Clarivoy Properties (Rooftops) board