How to Send Handwritten Notes Automatically from Redtail CRM

A paraplanner closes the last step of the new-client workflow in Redtail on a Tuesday morning. The household funded on Friday; the custodian paperwork cleared over the weekend. Redtail does what it was configured to do: the workflow marks complete, a review activity gets scheduled for next spring, and the contact's status flips from Prospect to Client. Everything is recorded. Nothing has been said to the people who just moved their life savings.

The thing that would have made the first week memorable is sitting two tabs over, in the note the advisor typed after the discovery meeting — that they came in because their previous advisor retired and nobody at the old firm called. A card that uses that detail, mailed the day the workflow closes, is the piece of onboarding the client repeats to their brother-in-law. Redtail has held every signal needed to send it since Friday. The gap is that those signals currently produce activities and status changes, and closing it takes one Zap.

The Redtail moments worth a stamp

Redtail is built around contacts, activities, opportunities, and workflows, and a well-run advisory office touches one of them dozens of times a day. That is exactly why the first instinct — card on every event — is the wrong one. A card after every logged phone call stops being a gesture and becomes a mailer, and advisory clients are the demographic most practised at recognizing a mailer. Four triggers carry nearly all of the return.

A workflow completes

The strongest trigger in Redtail, and the one that distinguishes it from CRMs that only know about deal stages. Most offices run onboarding, account transfer, annual review, and beneficiary updates as Redtail workflows, and a completed workflow — or a specific completed step inside one — marks something that actually happened to the client rather than something an advisor remembered to update. The funding step of onboarding is the single best card in the business: the client has just made a decision they deliberated over for weeks and is still deciding whether it was right. The wider case for which advisory moments deserve a note is in handwritten notes for financial advisors.

An opportunity is won

Offices that track pipeline in Redtail Opportunities get a clean trigger when the stage changes to a won or closed value. Pull from the record: the opportunity source, the amount if your templates reference the scale of the relationship (most should not), and the notes the advisor left along the way. If your office treats the opportunity close and the onboarding workflow as the same moment, pick one or the client gets two cards in a week.

An important date comes around

Redtail keeps birthdays, anniversaries, retirement dates, and client-since dates on the contact, plus whatever custom dates your office has added. A five-year client-since card written from what those five years actually covered — the first review, the college funding, the year they retired — outperforms every birthday card in the stack, because almost nobody else sends one. Automated birthday cards for customers covers how to keep date-triggered cards from reading like a calendar alert.

A review activity closes

The annual review is the moment most likely to be the only conversation of the year, and the card that follows it is the cheapest way to make it feel like something more than a compliance obligation. Trigger it from the review activity being marked complete, written from the activity note — the goal they mentioned, the concern they raised, the thing they are looking forward to. Keep a human in the loop on the subset tagged with a life event; a note after a review that discussed a spouse's diagnosis should be read before it mails, and sympathy card messages for clients covers why that category never runs on automatic.

Setting it up

Redtail does not offer outbound webhooks, so the route is Zapier, which Redtail supports directly. Enable the Zapier integration from inside Redtail, generate a Zapier token, and connect the account. The available triggers cover contacts created and updated, opportunities created and updated, activities created and updated, and — the ones that matter most here — Workflow Step Completed and Workflow Step Task Completed. That reaches every moment above without a single new field being built.

• ✓Connect Redtail to Zapier with a Zapier token from Redtail's integrations settings, then connect Scribble on the action side.
• ✓Pick the trigger. Workflow Step Completed, filtered to the funding step of your onboarding workflow, is the most precise. Opportunity Updated with a filter on stage equals Won is the most common starting point. Activity Updated with a filter on type equals Review and status equals Completed handles the post-review card.
• ✓Set a tone or template per trigger so the welcome card does not read like the anniversary card and the post-review note does not sound like onboarding.
• ✓Map the mailing address deliberately. Redtail contacts commonly carry a home address, a mailing address, and a business address, and nearly every misdelivered card traces back to picking the wrong one. For a household, send one card to the primary contact's mailing address, not one per spouse.
• ✓Choose a control mode: fully automatic, notify-only, a review window that auto-approves after a set number of hours, or approve-each. Offices with a compliance review step usually start on approve-each and relax it once the drafts stop needing edits.
• ✓Send a test card to your own desk and read it out loud before the Zap goes live for clients.

Turning Redtail fields into copy that doesn't sound like a merge

This is where most automated client mail gives itself away. A merge template produces 'Welcome to the firm, {{first_name}}' at any scale you like, and a client who has just signed a transfer form notices the seam in the first sentence. For a channel whose entire value is that it does not read as automated, that is an odd way to fail.

The fix is letting the record write the sentences. Scribble drafts each card from what the Redtail contact actually holds — the opportunity source, the discovery-meeting note, the workflow that just closed, the client-since year — so two households onboarded the same week get genuinely different cards. The advisor's own notes are the richest input, which is the best argument anyone has made for logging them: a sentence typed after a meeting becomes the sentence on the card.

The point of connecting Redtail is not to send more cards. It is to send cards that could only have been written to that one household.

Compliance deserves its own paragraph for an RIA or a broker-dealer office. Nothing in a welcome, thank-you, or anniversary card should reference performance, returns, or a recommendation, and a template per trigger is the simplest way to guarantee it. Offices that archive client correspondence can log each card's text back to the contact — the next section — so it sits with the rest of the record and the books-and-records question is answered before it is asked.

Writing results back to Redtail

An integration that only sends is half an integration. Use a second step in the same Zap to create a note or a completed activity on the Redtail contact when the card mails — the text, the trigger, the date — so the next person who opens the record sees a card already went out and does not send another. Route response signals back the same way: a QR code on the card can log an activity, apply a tag, or create a task for the advisor on scan, which turns a physical card into something Redtail can actually see.

That write-back is what answers the question when a partner asks what the handwritten-mail line item is doing. The answer becomes logged activities and tagged referrals sitting inside Redtail next to the opportunities they produced, rather than a shipment count in a separate tool.

A sensible rollout

Start with one Zap, not five. The funding step of onboarding — or Opportunity Won, if that is how your office marks a new relationship — is almost always the right first trigger. Run it in review-window mode for a few weeks so every card gets a look before it mails but nothing stalls during a busy stretch. Once the drafts stop needing edits, move it to fully automatic and add the second trigger; the client-since anniversary is usually the best follow-up, because the volume is steady and every recipient is already a client. If the trigger you want lives partly in another system, such as a custodian feed or a planning tool, the Zapier route combines them the same way. Firms on Wealthbox get the same build, mapped to its opportunities and workflow steps, in the Wealthbox guide; firms on Salesforce Financial Services Cloud have a direct path.