Pipedrive email templates are useful when your team repeatedly asks for the same information. The challenge is keeping the reusable wording separate from details that need a fresh decision: which customer, which job and what you are actually promising.
This guide uses an illustrative UK equipment supplier requesting information before a site survey. The workflow is an editorial example, not a report of hands-on testing.
Table of Contents
Check access and choose one message to standardise
Pipedrive currently includes email sync on Growth and higher plans. If your mailbox is not connected, start with our Pipedrive email sync guide.
Choose a message with one clear purpose. For the equipment supplier, that might be collecting access instructions before arranging a survey. Avoid combining an introduction, a quotation, a booking confirmation and a payment request in one sprawling template.
Write a short brief before building anything:
- Use when: the customer has agreed to discuss a survey, but practical details are missing.
- Ask for: the site contact, access restrictions and suitable visiting windows.
- Do not promise: a fixed appointment, price or engineer until someone has checked availability.
This gives colleagues a useful boundary. They can judge whether the message fits the conversation rather than selecting it because its name sounds vaguely relevant.
Create the first version privately
Connect email sync before creating templates. In the composer, write your message, then use Choose template > Save draft as template. Add an internal name and select private or shared visibility, following Pipedrive’s template instructions.
Use a name such as “Survey enquiry: request access details”. Keep it private while checking the wording. A descriptive name is more useful than “Follow-up 4”, particularly when a new colleague joins the team.
For the illustrative supplier, the reusable body could be:
Thank you for discussing a site survey with us. Could you confirm who should meet our engineer, any access restrictions, and two suitable visiting windows? We will check availability and come back to confirm the arrangement.
This is original sample wording. Adapt it to your service and the actual conversation. It deliberately leaves out an address, price and appointment date; copying those details from a previous customer would create unnecessary risk.
Give shared wording a clear owner
Regular users can edit only templates they created. Adapting someone else’s shared template requires saving a new version, according to the editing guidance.
Agree who maintains the team’s main version before sharing it. Otherwise, three colleagues may create three slightly different copies and nobody will know which one reflects the current service.
Keep a short team note recording the approved name, its purpose and the person responsible for changes. Ask colleagues to flag confusing wording or an outdated promise. A customer’s unusual request belongs in that customer’s message, rather than becoming a permanent sentence everyone else sends.
Check the record behind every merge field
Merge fields require the relevant linked record and populated values; empty fields produce a warning. When someone has multiple deals, compose from the intended deal or link it in Sales Inbox. See Pipedrive’s merge-field requirements.
For example, the same facilities manager could be discussing equipment for a Leeds office and a Bristol warehouse. A familiar contact name alone does not tell the sender which premises the message concerns. Open the opportunity you intend to discuss and compare the finished message with that job’s notes.
Before adopting the template across the team, review these three situations using suitable test records or an unsent draft:
- Complete details: read the subject and body as a customer would, including spelling and the salutation.
- Missing information: decide whether to correct the CRM record, ask the customer or remove an unnecessary phrase.
- Several opportunities: verify the site, proposed work and next step against the intended deal.
Do not fill a blank with a guess just to make a message look finished. Where information is uncertain, an honest question is more useful than polished but incorrect personalisation.
Inspect attachments and the finished signature
Templates can include attachments. Prefer a general service document over a file containing another customer’s details. Before each send, open the actual attachment and check its contents, version and suitability for that recipient.
The composer inserts your configured default signature; edits made there affect only that email. Pipedrive explains this in its signature documentation.
Read the whole message once, including the footer. Check the sender’s name, telephone number, working hours and any duplicated sign-off. If the recipient replies to a colleague who is away, decide who will pick up the conversation.
Separate shared copy from conversation access
A reusable team message and a customer conversation have different access considerations. Pipedrive’s email visibility rules depend on account type, conversation settings and access to linked items.
For a handover, ask the receiving colleague to confirm they can find the relevant conversation through their normal account. Agree the next action and owner; use Pipedrive activities to organise that follow-up.
Templates do not remove sending restrictions. Company-wide and email-provider limits still apply. This individual-message workflow should not be treated as a bulk outreach plan.
Revisit the wording whenever your service, booking process or contact details change. Keep the small library understandable, and make the final customer-specific check part of every send.
Sources reviewed 1 November 2026. Product details are based on Pipedrive’s official documentation; the scenario and practical recommendations are editorial examples.
