Native Functionality & Tools | Entry 56
HubSpot playbooks are interactive conversation guides that appear on eligible CRM records. They help nonprofit staff and volunteers follow a repeatable structure, ask required questions, capture useful answers, update eligible CRM data, log the conversation, and complete the right follow-up without turning a personal exchange into a rigid script.
A playbook can remind the user what to ask, what information to provide, which warning signs to notice, and what should happen next. It can also store standardized notes, collect structured answers, update eligible CRM properties, log the engagement, create a task, schedule a meeting, create or associate another record, and support reporting or workflow automation.
HubSpot currently offers playbooks through eligible Sales Hub and Service Hub Professional and Enterprise subscriptions. An assigned Sales or Service seat is required, and creation and publishing depend on the user's playbook permissions.
A playbook can contain instructions, talking points, questions, open-text fields, structured answer options, required questions, CRM property questions, personalization tokens, links, media, embedded content, knowledge base articles, snippets, meeting scheduling, record creation, follow-up tasks, and logging settings.
It can tell the user what to explain, provide the right resource, ask the next qualification question, and store the result without forcing the user to move among several documents.
| Static script | HubSpot playbook |
|---|---|
| Stored in a document | Available from eligible CRM records |
| Tells the user what to say | Provides guidance and collects responses |
| Notes may be stored elsewhere | Answers can be logged to the CRM timeline |
| Does not update CRM fields | Eligible questions can update CRM properties |
| Has little associated record context | Used alongside the constituent's CRM record |
| Difficult to measure adoption | Includes usage and adoption analytics |
| Follow-up depends on memory | Can create a follow-up task |
Playbooks can be used from eligible Contact, Company, Deal, Ticket, and custom-object records. Published playbooks appear in the Playbooks section of the record's right-side panel, while recommended playbooks can also appear through a configurable CRM card in the middle column.
Staff can review previous emails, calls, meetings, donations or opportunities, volunteer activity, membership information, support requests, associated organizations, and open tasks while following the conversation guide.
Open-text questions capture nuance: what inspired someone to support the mission, which program matters most, what would make a partnership successful, what concern is blocking renewal, or what follow-up the organization promised.
Structured answer options create cleaner information when a known set of outcomes applies. An auction-item response might be Confirmed donation, Needs more information, Considering the request, Declined, Requested a callback, Wrong contact, or Item already collected.
Use open text when the story matters. Use structured information when the answer must support filtering, automation, routing, or reporting. HubSpot currently identifies list-of-answer-options questions as a Sales Hub Enterprise capability.
| Playbook question | Possible CRM property |
|---|---|
| What type of volunteering interests you? | Volunteer interest |
| Which program matters most to the donor? | Primary program interest |
| What sponsorship level is being considered? | Sponsorship level |
| Is the auction item confirmed? | Auction-item status |
| When should we follow up? | Next follow-up date |
| What is the preferred contact method? | Preferred communication method |
| What is the membership concern? | Membership renewal barrier |
Property-linked questions require eligible Enterprise functionality and playbook permissions. Once logged, the answers can support segmentation, saved views, workflows, reporting, personalization, record display, future conversations, assignment, and routing.
Create or update a property when the answer has repeated value for filtering, reporting, automation, routing, personalization, record views, or long-term relationship management. Use a note when the detail belongs to one conversation, changes frequently, is highly contextual, does not need reporting, or includes sensitive information.
Poorly planned playbooks can create unnecessary properties and clutter the CRM.
If a sponsor is interested, staff may explore benefits, stakeholders, decision-making, a meeting, the opportunity record, and the next task. If the sponsor needs information, staff can identify the missing details, share the approved package, confirm the decision deadline, and schedule follow-up. If the sponsor declines, staff can record the barrier respectfully and decide whether future outreach is appropriate.
Do not assume that every question creates a fully branching decision tree. Test the behavior available in the account and provide clear guidance where human judgment is still required.
The goal is a thoughtful, consistent conversation, not an interrogation.
A playbook can guide staff or volunteers through the introduction, prior request or donation history, item details, fair market value, restrictions, availability, collection logistics, recognition, response status, follow-up date, pickup task, event-team notification, and acknowledgment.
A trained volunteer can follow the same approved structure as staff without memorizing the entire process.
Sensitive screening, safeguarding, health, identity, and background-check information requires careful access and data-governance planning. Collect only information the nonprofit needs and is authorized to store.
Playbook submissions can be saved as eligible Call, Meeting, Email, or Note activities. HubSpot can preserve the questions, answers, notes, engagement type, applicable call outcome or type, follow-up task, and eligible property updates on the CRM timeline.
By default, an engagement may attach only to the record where the playbook was used. A property question that targets an associated record type can affect cross-object logging. Test which records receive the activity, which record each question updates, whether users must select a related record, and where other teams expect to find the result.
If a call or meeting was already logged, HubSpot documents the ability to attach a completed playbook to a recent eligible engagement logged within the previous six hours, helping avoid duplicate activities.
From the playbook experience, staff can create a task, schedule a meeting, create or associate a CRM record, select a call outcome, update eligible properties, or trigger an eligible workflow after logging.
| Record condition | Recommended playbook |
|---|---|
| Contact type is Major Donor Prospect | Major-Donor Discovery |
| Deal type is Corporate Sponsorship | Sponsorship Qualification |
| Volunteer status is Applicant | Volunteer Interview |
| Ticket category is Membership Renewal | Member-Retention Conversation |
| Auction-item status is Outreach Needed | Auction-Item Call |
| Deal stage is Stewardship Meeting | Donor Stewardship |
Recommendation rules can use eligible Contact, Company, Deal, and Ticket properties. Super Admins can also place the Recommended Enablement CRM card on default or team-specific record layouts.
Share donor and stewardship playbooks with development, recruitment playbooks with volunteer staff, renewal playbooks with membership teams, intake guides with program teams, partnership guides with sponsorship staff, and only the approved auction process with event volunteers.
Eligible users may be able to view and use playbooks without permission to create or publish them. Limit writing and publishing to people responsible for approved processes, and align access with job responsibilities and information sensitivity.
Built-in playbook analytics may include total playbooks, views, active users, views and submissions by user, usage over time, individual playbook use, related activities, and team adoption. This can reveal whether staff use the donor discovery guide, whether volunteers log their calls, where training is needed, and which playbooks should be revised or retired.
For outcome reporting, map a carefully chosen set of answers to CRM properties such as donor interest, sponsorship level, volunteer-interest category, renewal barrier, auction-item status, preferred contact method, partnership priority, or follow-up date.
A logged playbook submission can be an eligible workflow enrollment event for notifications, tasks, opportunity updates, internal alerts, support routing, review processes, qualified segments, or stewardship reminders.
Opening a playbook does not mean the conversation was completed. Base workflow logic on the logged submission or resulting structured property value.
Avoid long scripts, excessive introductions, dozens of required questions, asking for information already visible on the record, forcing every conversation down one path, collecting data with no purpose, or requiring duplicate entry.
A strong playbook provides enough structure for consistency while leaving space for listening, judgment, empathy, and natural conversation.
HubSpot includes version history, cloning, publishing, unpublishing, folders, and sharing controls. Without governance, teams may accumulate duplicate guides, conflicting questions, inconsistent properties, outdated language, broken links, and former staff practices.
Playbooks can make important conversations easier for new and experienced staff, volunteers, temporary event teams, managers, and distributed teams.
The value is not simply giving everyone a script. It is helping each person ask the right questions, capture the right information, connect it to the right CRM record, and complete the right follow-up.